1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

IRQ conflict and random re-booting

Discussion in 'Windows XP' started by velectro, 2009/01/22.

Page 1 of 3
  1. 2009/01/22
    velectro

    velectro Inactive Thread Starter

    Joined:
    2009/01/22
    Messages:
    35
    Likes Received:
    0
    Hi all,

    My computer is suffering from random re-starts, with the message:

    driver_irql_not_less_or_equal
    stop: 0x000000d1 (0x00485404, 0x000000ff, 0x0000001, 0xBA6CD062)

    Here is the info from system information:

    I/O Port 0x00000000-0x00000CF7 PCI bus
    I/O Port 0x00000000-0x00000CF7 Direct memory access controller

    I/O Port 0x000003C0-0x000003DF PCI standard PCI-to-PCI bridge
    I/O Port 0x000003C0-0x000003DF NVIDIA GeForce 8400 GS

    IRQ 21 Microsoft UAA Bus Driver for High Definition Audio
    IRQ 21 NVIDIA MCP61 Serial ATA Controller

    I/O Port 0x0000B000-0x0000BFFF PCI standard PCI-to-PCI bridge
    I/O Port 0x0000B000-0x0000BFFF NVIDIA GeForce 8400 GS

    Memory Address 0xE0000000-0xEFFFFFFF PCI standard PCI-to-PCI bridge
    Memory Address 0xE0000000-0xEFFFFFFF NVIDIA GeForce 8400 GS

    Memory Address 0xA0000-0xBFFFF PCI bus
    Memory Address 0xA0000-0xBFFFF PCI standard PCI-to-PCI bridge
    Memory Address 0xA0000-0xBFFFF NVIDIA GeForce 8400 GS

    I/O Port 0x000003B0-0x000003BB PCI standard PCI-to-PCI bridge
    I/O Port 0x000003B0-0x000003BB NVIDIA GeForce 8400 GS

    Memory Address 0xF8000000-0xFBFFFFFF PCI standard PCI-to-PCI bridge
    Memory Address 0xF8000000-0xFBFFFFFF NVIDIA GeForce 8400 GS




    I have already done a re-format and fresh XP install, but it hasnt solved it. I tried to manually change IRQ but of course found it was greyed out and i couldn't!

    I have reached the end of my tether and PC knowledge,so I'm hoping someone on here can help!

    Thanks.
     
    velectro,
    #1
  2. 2009/01/22
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    4,076
    Likes Received:
    178
    Its most probably a driver related issue.

    Update all your drivers specially video drivers. [nVidia]
     
    rsinfo,
    #2


  3. to hide this advert.

  4. 2009/01/22
    velectro

    velectro Inactive Thread Starter

    Joined:
    2009/01/22
    Messages:
    35
    Likes Received:
    0
    Thanks for replying, last time i re-installed everything i made sure i had the most up-to-date drivers for everything
     
    velectro,
    #3
  5. 2009/01/22
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    As a matter of interest did you install the motherboard chipset drivers after the format and install?
     
    PeteC,
    #4
  6. 2009/01/22
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    I would check out your RAM, noting .....
    The only satisfactory way of testing RAM is to test the installed RAM in various configurations. If you have a single module swap it around the slots. If you have a pair of modules run each one singly, swapping between slots; then run them in pairs swapping between pairs of slots. If you have 2 sets of matched modules do not get them mixed up.
     
    PeteC,
    #5
  7. 2009/01/22
    velectro

    velectro Inactive Thread Starter

    Joined:
    2009/01/22
    Messages:
    35
    Likes Received:
    0
    Thanks for the tip, I have one 2gb module installed. When i move it to the 2nd slot it wont boot the computer, i get 2 beeps close together, move it back to original slot and all is well...not sure what that means?

    Is this the cause of the other part of the problem, or a seperate issue?
     
    velectro,
    #6
  8. 2009/01/22
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    What is the make of your BIOS - AMI, Award, Phoenix ....?
     
    PeteC,
    #7
  9. 2009/01/22
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Follow these instructions to post a Dump Data Log.

    If you do not have a dump, ensure that your machine is configured to write out a dump by following the directions from microsoft

    Please note:
     
    Arie,
    #8
  10. 2009/01/22
    velectro

    velectro Inactive Thread Starter

    Joined:
    2009/01/22
    Messages:
    35
    Likes Received:
    0
    Thanks for your replies. Motherboard info:

    Gigabyte M61PME-S2
    Chipset: Nvidia MCP61

    Bios:

    Award, Version F1, Date 01/08/2008


    I'll post dump data log shortly
     
    velectro,
    #9
  11. 2009/01/23
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    I have been unable to decode the BIOS beeps you noted - they do not appear in ....

    Award BIOS Beep Codes , but the fact that changing the memory slot eliminates the problem suggests a slot problem on the mobo. There is nothing in the manual to suggest that a single module must be installed in a specific slot.

    BTW you never responded to ....
     
    PeteC,
    #10
  12. 2009/01/24
    velectro

    velectro Inactive Thread Starter

    Joined:
    2009/01/22
    Messages:
    35
    Likes Received:
    0
    Hi, sorry i must have missed that question - yes i have tried both the most up-to-date chipset drivers from the web site and my old ones from CD - on various installs and both versions result in the same issue.

    I tried using the debugging tool for windows with debugwiz and it said after the DOS window went it would write a txt file to my C drive, it hasn't and as much as i look and search I can't find it. But i did get this just from the debugging tool:

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 004854c4, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: ba7d5092, address which referenced memory
    Debugging Details:
    ------------------

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************

    MODULE_NAME: kmixer

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    004854c4

    CURRENT_IRQL: ff

    FAULTING_IP:
    +ffffffffba7d5092
    ba7d5092 f0360fba2900 lock bts dword ptr ss:[ecx],0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from 00000000 to ba7d5092

    SYMBOL_ON_RAW_STACK: 1

    STACK_ADDR_RAW_STACK_SYMBOL: ffffffffb450ad60

    STACK_COMMAND: dds B450AD60-0x20 ; kb

    STACK_TEXT:
    b450ad40 0012fb08
    b450ad44 006c529d
    b450ad48 0012fa10
    b450ad4c 7c90118a
    b450ad50 006c0000
    b450ad54 00000001
    b450ad58 ffffffff
    b450ad5c b43e2b9b <Unloaded_kmixer.sys>+0xab9b
    b450ad60 01660000
    b450ad64 0012f9bc
    b450ad68 7c90e4f4
    b450ad6c badb0d00
    b450ad70 0012f964
    b450ad74 b57aad98
    b450ad78 b57aadcc
    b450ad7c 80539ac0 nt+0x62ac0
    b450ad80 804da930 nt+0x3930
    b450ad84 ffffffff
    b450ad88 b57aada8
    b450ad8c 805d28d4 nt+0xfb8d4
    b450ad90 00000000
    b450ad94 00000000
    b450ad98 00000023
    b450ad9c 00000023
    b450ada0 000004f9
    b450ada4 0000000c
    b450ada8 4f909b31
    b450adac 00000001
    b450adb0 ffffffff
    b450adb4 0000003b
    b450adb8 01660000
    b450adbc 00000000


    FOLLOWUP_IP:
    kmixer+ab9b
    b43e2b9b ?? ???

    SYMBOL_NAME: kmixer+ab9b

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: kmixer.sys

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
     
    velectro,
    #11
  13. 2009/01/24
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    This is the second occasion in recent weeks when the dump log has not been written to C:\. I have no idea of the cause - possibly a result of the problem with the computer ?? The problem has been passed on, but I doubt if we will have access to a solution - the member who wrote the Debug wizard - an MS 'code monkey' is no longer with us on the BBS.

    The log you produced has a symbol problem - were you connected to the internet while debugging?
     
    PeteC,
    #12
  14. 2009/01/24
    velectro

    velectro Inactive Thread Starter

    Joined:
    2009/01/22
    Messages:
    35
    Likes Received:
    0
    Yes i was connected to the internet whilst de-bugging, should i re-do it whilst disconnected?
     
    velectro,
    #13
  15. 2009/01/25
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    No - you need to be connected for the appropriate symbol set to be downloaded if not available on the computer.

    As you have reformatted and reinstalled XP and the problem still remains I tend to lean towards a hardware problem.

    The log referenced kmixer.sys which is Windows kernel mode audio mixer.

    A few suggestions ...

    Run System File Checker .....

    Start > Run > type in sfc /scannow > Enter and have your XP CD handy - it may be asked for. SFC will run and exit with no closing dialogue. To determine if any files were changed look in Event Viewer - any changes will be noted between the entries shown in the screenshot below.

    Disable all Audio Devices in Device Manager - if the restarts cease this points towards a faulty audio chip/card. (If you have a plug in audio card try removing it - and disabling the onboard audio if present)

    On the off chance it is a faulty pagefile which is causing the problem - unlikely as you have reformatted, etc - set the pagefile to a max/min of zero and reboot. Then set a fixed size pagefile (preferred) with a max/min of 1.5x the installed RAM and reboot. This creates a new pagefile.

    As noted above the possibility of a hardware problem cannot be ruled out - you already seem to have a problem with a memory slot.
     

    Attached Files:

    PeteC,
    #14
  16. 2009/01/25
    velectro

    velectro Inactive Thread Starter

    Joined:
    2009/01/22
    Messages:
    35
    Likes Received:
    0
    PeteC, thank you for your suggestions, here are my results...

    system file checker thre up events 7035 and 7036 in the event viewer.
    After one of its random re-starts, event 1003 also appeared.

    I disabled the audio in device manager, and this made no difference. I then disabled it in the Bios with no result.

    I also followed your instructions about the Pagefile, and again no result.

    I too am now seriously thinking this could be a hardware problem, i really hope not i'd rather not have to shell out for more components!
     
    velectro,
    #15
  17. 2009/01/26
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    We have found that the path for the log file in the revised version of the Debug Wizard is incorrect. This explains why I have no trouble using an earlier version and you were unable to find the dump log.

    Please run the Debug Wizard again .....

    Browse to the location of your dump file and select it.

    Tick the Advanced button and edit the first part of the 'Command string to pass to debugger' (Screenshots) .....

    Replace -logo c:temp\debuglog.txt with -logo c:\debuglog.txt

    i.e. remove temp
     

    Attached Files:

    PeteC,
    #16
    velectro likes this.
  18. 2009/01/26
    velectro

    velectro Inactive Thread Starter

    Joined:
    2009/01/22
    Messages:
    35
    Likes Received:
    0
    Hi PeteC, thanks again for posting....here is the results...I can see this was created after i had tried to start the game "Obscure" and it caused a reboot, but the rest makes no sense to me so hopefully someone here can understand it:

    Opened log file 'c:\debuglog.txt'

    Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini012409-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 2600.xpsp_sp3_gdr.080814-1236
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Sat Jan 24 15:22:37.125 2009 (GMT+0)
    System Uptime: 0 days 4:02:06.852
    Loading Kernel Symbols
    ...............................................................
    ............................................................
    Loading User Symbols
    Loading unloaded module list
    ..............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {4854c4, ff, 1, ba7d5092}

    Probably caused by : kmixer.sys ( kmixer+ab9b )

    Followup: MachineOwner
    ---------

    1: kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 004854c4, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: ba7d5092, address which referenced memory

    Debugging Details:
    ------------------


    WRITE_ADDRESS: 004854c4

    CURRENT_IRQL: ff

    FAULTING_IP:
    +ffffffffba7d5092
    ba7d5092 f0360fba2900 lock bts dword ptr ss:[ecx],0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: Obscure.exe

    LAST_CONTROL_TRANSFER: from 00000000 to ba7d5092

    SYMBOL_ON_RAW_STACK: 1

    STACK_ADDR_RAW_STACK_SYMBOL: ffffffffb450ad60

    STACK_COMMAND: dds B450AD60-0x20 ; kb

    STACK_TEXT:
    b450ad40 0012fb08
    b450ad44 006c529d
    b450ad48 0012fa10
    b450ad4c 7c90118a
    b450ad50 006c0000
    b450ad54 00000001
    b450ad58 ffffffff
    b450ad5c b43e2b9b <Unloaded_kmixer.sys>+0xab9b
    b450ad60 01660000
    b450ad64 0012f9bc
    b450ad68 7c90e4f4
    b450ad6c badb0d00
    b450ad70 0012f964
    b450ad74 b57aad98
    b450ad78 b57aadcc
    b450ad7c 80539ac0 nt!_except_handler3
    b450ad80 804da930 nt!ObWatchHandles+0x6cc
    b450ad84 ffffffff
    b450ad88 b57aada8
    b450ad8c 805d28d4 nt!PspTerminateThreadByPointer+0x52
    b450ad90 00000000
    b450ad94 00000000
    b450ad98 00000023
    b450ad9c 00000023
    b450ada0 000004f9
    b450ada4 0000000c
    b450ada8 4f909b31
    b450adac 00000001
    b450adb0 ffffffff
    b450adb4 0000003b
    b450adb8 01660000
    b450adbc 00000000


    FOLLOWUP_IP:
    kmixer+ab9b
    b43e2b9b ?? ???

    SYMBOL_NAME: kmixer+ab9b

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: kmixer

    IMAGE_NAME: kmixer.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: 0xD1_kmixer+ab9b

    BUCKET_ID: 0xD1_kmixer+ab9b

    Followup: MachineOwner
    ---------

    eax=01660000 ebx=0000005f ecx=004854c4 edx=01807b7b esi=006d0d88 edi=01660000
    eip=ba7d5092 esp=b450ad30 ebp=00000000 iopl=0 nv up di pl nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010002
    ba7d5092 f0360fba2900 lock bts dword ptr ss:[ecx],0 ss:0010:004854c4=????????
    ChildEBP RetAddr Args to Child
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00000000 00000000 00000000 00000000 00000000 0xba7d5092
    start end module name
    804d7000 806e4000 nt ntkrpamp.exe Thu Aug 14 10:33:13 2008 (48A3FBD9)
    806e4000 80704d00 hal halmacpi.dll Sun Apr 13 19:31:27 2008 (4802517F)
    b566a000 b56aaa80 HTTP HTTP.sys Sun Apr 13 19:53:48 2008 (480256BC)
    b58ab000 b58aee00 GTNDIS5 GTNDIS5.SYS Thu Sep 25 15:15:31 2003 (3F72F883)
    b5d63000 b5db4880 srv srv.sys Thu Dec 11 10:57:07 2008 (4940F203)
    b5e2b000 b5e3f480 wdmaud wdmaud.sys Sun Apr 13 20:17:18 2008 (48025C3E)
    b5f30000 b5f5c180 mrxdav mrxdav.sys Sun Apr 13 19:32:42 2008 (480251CA)
    b6189000 b618c900 ndisuio ndisuio.sys Sun Apr 13 19:55:57 2008 (4802573D)
    b621d000 b622bd80 sysaudio sysaudio.sys Sun Apr 13 20:15:55 2008 (48025BEB)
    b671d000 b6734900 dump_atapi dump_atapi.sys Sun Apr 13 19:40:29 2008 (4802539D)
    b675d000 b67cc280 mrxsmb mrxsmb.sys Fri Oct 24 12:21:07 2008 (4901AFA3)
    b67cd000 b67e0680 prodrv06 prodrv06.sys Thu May 13 12:19:35 2004 (40A359C7)
    b67e1000 b680be80 rdbss rdbss.sys Sun Apr 13 20:28:38 2008 (48025EE6)
    b680c000 b682dd00 afd afd.sys Thu Aug 14 11:04:35 2008 (48A40333)
    b6856000 b687dc00 netbt netbt.sys Sun Apr 13 20:20:59 2008 (48025D1B)
    b687e000 b68a3500 ipnat ipnat.sys Sun Apr 13 19:57:10 2008 (48025786)
    b68a4000 b68fc480 tcpip tcpip.sys Fri Jun 20 12:51:09 2008 (485B99AD)
    b68fd000 b690f600 ipsec ipsec.sys Sun Apr 13 20:19:42 2008 (48025CCE)
    b6930000 b696c000 klif klif.sys Mon Oct 27 19:33:06 2008 (49061772)
    b69dd000 b69e0900 kbdhid kbdhid.sys Sun Apr 13 19:39:47 2008 (48025373)
    b69e1000 b69e3f80 mouhid mouhid.sys Fri Aug 17 21:47:57 2001 (3B7D82FD)
    b69e9000 b69eb880 hidusb hidusb.sys Sun Apr 13 19:45:27 2008 (480254C7)
    b6a01000 b6a24a80 portcls portcls.sys Sun Apr 13 20:19:40 2008 (48025CCC)
    b6a25000 b6f0d000 RtkHDAud RtkHDAud.sys Tue Jan 06 11:00:02 2009 (496339B2)
    b6f9d000 b6fa8c00 fssfltr_tdi fssfltr_tdi.sys Tue Dec 09 00:59:19 2008 (493DC2E7)
    b90d5000 b9132f00 update update.sys Sun Apr 13 19:39:46 2008 (48025372)
    b9133000 b9143e00 psched psched.sys Sun Apr 13 19:56:36 2008 (48025764)
    b9144000 b915a580 ndiswan ndiswan.sys Sun Apr 13 20:20:41 2008 (48025D09)
    b915b000 b916ef00 VIDEOPRT VIDEOPRT.SYS Sun Apr 13 19:44:39 2008 (48025497)
    b916f000 b9748360 nv4_mini nv4_mini.sys Wed Sep 17 18:44:45 2008 (48D1420D)
    b9749000 b976b700 ks ks.sys Sun Apr 13 20:16:34 2008 (48025C12)
    b976c000 b9794000 HDAudBus HDAudBus.sys Thu May 26 16:46:29 2005 (4295EF55)
    b9794000 b97eaf00 RT61 RT61.sys Thu Oct 27 08:06:27 2005 (43607C73)
    b97eb000 b980e200 USBPORT USBPORT.SYS Sun Apr 13 19:45:34 2008 (480254CE)
    b980f000 b9822900 parport parport.sys Sun Apr 13 19:40:09 2008 (48025389)
    b9842000 b9845c80 mssmbios mssmbios.sys Sun Apr 13 19:36:45 2008 (480252BD)
    b9846000 b9848780 ndistapi ndistapi.sys Sun Apr 13 19:57:27 2008 (48025797)
    b9852000 b9854280 rasacd rasacd.sys Fri Aug 17 21:55:39 2001 (3B7D84CB)
    b985a000 b985d1c0 cdrbsdrv cdrbsdrv.SYS Mon Mar 08 03:55:49 2004 (404BEEC5)
    b9882000 b9da1000 kl1 kl1.sys Mon Jul 21 15:33:37 2008 (48849E41)
    b9da1000 b9dbab80 Mup Mup.sys Sun Apr 13 20:17:05 2008 (48025C31)
    b9dbb000 b9dd64c0 prohlp02 prohlp02.sys Thu May 13 14:00:03 2004 (40A37153)
    b9dd7000 b9e03980 NDIS NDIS.sys Sun Apr 13 20:20:35 2008 (48025D03)
    b9e04000 b9e90600 Ntfs Ntfs.sys Sun Apr 13 20:15:49 2008 (48025BE5)
    b9e91000 b9ea7880 KSecDD KSecDD.sys Sun Apr 13 19:31:40 2008 (4802518C)
    b9ea8000 b9eb9f00 sr sr.sys Sun Apr 13 19:36:50 2008 (480252C2)
    b9eba000 b9ed9b00 fltmgr fltmgr.sys Sun Apr 13 19:32:58 2008 (480251DA)
    b9eda000 b9ef1880 SCSIPORT SCSIPORT.SYS Sun Apr 13 19:40:29 2008 (4802539D)
    b9ef2000 b9f17000 nvgts nvgts.sys Tue Aug 19 02:53:21 2008 (48AA2791)
    b9f17000 b9f30c00 nvata nvata.sys Thu Oct 19 01:31:35 2006 (4536C767)
    b9f31000 b9f48900 atapi atapi.sys Sun Apr 13 19:40:29 2008 (4802539D)
    b9f49000 b9f67880 ftdisk ftdisk.sys Fri Aug 17 21:52:41 2001 (3B7D8419)
    b9f68000 b9f78a80 pci pci.sys Sun Apr 13 19:36:43 2008 (480252BB)
    b9f79000 b9fa6d80 ACPI ACPI.sys Sun Apr 13 19:36:33 2008 (480252B1)
    ba0a8000 ba0b1180 isapnp isapnp.sys Sun Apr 13 19:36:40 2008 (480252B8)
    ba0b8000 ba0c2580 MountMgr MountMgr.sys Sun Apr 13 19:39:45 2008 (48025371)
    ba0c8000 ba0d4c80 VolSnap VolSnap.sys Sun Apr 13 19:41:00 2008 (480253BC)
    ba0d8000 ba0e0e00 disk disk.sys Sun Apr 13 19:40:46 2008 (480253AE)
    ba0e8000 ba0f4180 CLASSPNP CLASSPNP.SYS Sun Apr 13 20:16:21 2008 (48025C05)
    ba0f8000 ba103000 klbg klbg.sys Tue Jan 29 14:29:18 2008 (479F383E)
    ba158000 ba167900 Cdfs Cdfs.SYS Sun Apr 13 20:14:21 2008 (48025B8D)
    ba168000 ba171000 HIDCLASS HIDCLASS.SYS Sun Apr 13 19:45:25 2008 (480254C5)
    ba188000 ba196000 AmdK8 AmdK8.sys Mon Jun 19 07:37:31 2006 (4496462B)
    ba198000 ba1a7c00 serial serial.sys Sun Apr 13 20:15:44 2008 (48025BE0)
    ba1a8000 ba1b1000 klfltdev klfltdev.sys Thu Mar 13 15:02:27 2008 (47D94203)
    ba1b8000 ba1c2480 imapi imapi.sys Sun Apr 13 19:40:57 2008 (480253B9)
    ba1c8000 ba1d7600 cdrom cdrom.sys Sun Apr 13 19:40:45 2008 (480253AD)
    ba1d8000 ba1e6100 redbook redbook.sys Sun Apr 13 19:40:27 2008 (4802539B)
    ba1f8000 ba204880 rasl2tp rasl2tp.sys Sun Apr 13 20:19:43 2008 (48025CCF)
    ba208000 ba212200 raspppoe raspppoe.sys Sun Apr 13 19:57:31 2008 (4802579B)
    ba218000 ba223d00 raspptp raspptp.sys Sun Apr 13 20:19:47 2008 (48025CD3)
    ba228000 ba230900 msgpc msgpc.sys Sun Apr 13 19:56:32 2008 (48025760)
    ba238000 ba241f00 termdd termdd.sys Sun Apr 13 19:38:36 2008 (4802532C)
    ba288000 ba291e80 NDProxy NDProxy.SYS Sun Apr 13 19:57:28 2008 (48025798)
    ba2a8000 ba2b6b00 drmk drmk.sys Sun Apr 13 19:45:12 2008 (480254B8)
    ba2b8000 ba2c6880 usbhub usbhub.sys Sun Apr 13 19:45:36 2008 (480254D0)
    ba2d8000 ba2e0700 wanarp wanarp.sys Sun Apr 13 19:57:20 2008 (48025790)
    ba2e8000 ba2f0780 netbios netbios.sys Sun Apr 13 19:56:01 2008 (48025741)
    ba308000 ba312e00 Fips Fips.SYS Sun Apr 13 19:33:27 2008 (480251F7)
    ba328000 ba32e180 PCIIDEX PCIIDEX.SYS Sun Apr 13 19:40:29 2008 (4802539D)
    ba330000 ba334d00 PartMgr PartMgr.sys Sun Apr 13 19:40:48 2008 (480253B0)
    ba338000 ba33ca80 TDI TDI.SYS Sun Apr 13 20:00:04 2008 (48025834)
    ba348000 ba34e180 HIDPARSE HIDPARSE.SYS Sun Apr 13 19:45:22 2008 (480254C2)
    ba370000 ba375200 vga vga.sys Sun Apr 13 19:44:40 2008 (48025498)
    ba378000 ba37ca80 Msfs Msfs.SYS Sun Apr 13 19:32:38 2008 (480251C6)
    ba380000 ba387880 Npfs Npfs.SYS Sun Apr 13 19:32:38 2008 (480251C6)
    ba388000 ba38e000 StarOpen StarOpen.SYS Tue Jun 27 20:15:56 2006 (44A183EC)
    ba3a0000 ba3a7d80 usbccgp usbccgp.sys Sun Apr 13 19:45:38 2008 (480254D2)
    ba3a8000 ba3ad900 dadder dadder.sys Thu Aug 02 10:32:24 2007 (46B1A4A8)
    ba3c8000 ba3cc500 watchdog watchdog.sys Sun Apr 13 19:44:59 2008 (480254AB)
    ba418000 ba41c0a0 MRENDIS5 MRENDIS5.SYS Mon Nov 22 23:36:39 2004 (41A27807)
    ba428000 ba42c920 AegisP AegisP.sys Tue May 17 21:22:56 2005 (428A52A0)
    ba440000 ba441000 fdc fdc.sys unavailable (00000000)
    ba448000 ba44c300 usbohci usbohci.sys Sun Apr 13 19:45:34 2008 (480254CE)
    ba450000 ba457600 usbehci usbehci.sys Sun Apr 13 19:45:34 2008 (480254CE)
    ba468000 ba470000 klim5 klim5.sys Wed Apr 30 15:06:33 2008 (48187CE9)
    ba470000 ba474580 ptilink ptilink.sys Fri Aug 17 21:49:53 2001 (3B7D8371)
    ba478000 ba47c080 raspti raspti.sys Fri Aug 17 21:55:32 2001 (3B7D84C4)
    ba480000 ba486000 kbdclass kbdclass.sys Sun Apr 13 19:39:46 2008 (48025372)
    ba488000 ba48da00 mouclass mouclass.sys Sun Apr 13 19:39:47 2008 (48025373)
    ba490000 ba495000 flpydisk flpydisk.sys Sun Apr 13 19:40:24 2008 (48025398)
    ba4b8000 ba4bb000 BOOTVID BOOTVID.dll Fri Aug 17 21:49:09 2001 (3B7D8345)
    ba588000 ba58a900 Dxapi Dxapi.sys Fri Aug 17 21:53:19 2001 (3B7D843F)
    ba5a4000 ba5a7d80 serenum serenum.sys Sun Apr 13 19:40:12 2008 (4802538C)
    ba5a8000 ba5a9b80 kdcom kdcom.dll Fri Aug 17 21:49:10 2001 (3B7D8346)
    ba5aa000 ba5ab100 WMILIB WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
    ba5ac000 ba5ad2e0 sfhlp01 sfhlp01.sys Mon Dec 01 15:20:51 2003 (3FCB5C53)
    ba5ae000 ba5afb20 prosync1 prosync1.sys Sat Sep 06 13:22:06 2003 (3F59D16E)
    ba5f0000 ba5f1100 swenum swenum.sys Sun Apr 13 19:39:52 2008 (48025378)
    ba600000 ba601280 USBD USBD.SYS Fri Aug 17 22:02:58 2001 (3B7D8682)
    ba60c000 ba60da80 ParVdm ParVdm.SYS Fri Aug 17 21:49:49 2001 (3B7D836D)
    ba612000 ba613f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 21:49:37 2001 (3B7D8361)
    ba614000 ba615080 Beep Beep.SYS Fri Aug 17 21:47:33 2001 (3B7D82E5)
    ba616000 ba617080 mnmdd mnmdd.SYS Fri Aug 17 21:57:28 2001 (3B7D8538)
    ba618000 ba619080 RDPCDD RDPCDD.sys Fri Aug 17 21:46:56 2001 (3B7D82C0)
    ba62a000 ba62b100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
    ba670000 ba670d00 pciide pciide.sys Fri Aug 17 21:51:49 2001 (3B7D83E5)
    ba68f000 ba68fc00 audstub audstub.sys Fri Aug 17 21:59:40 2001 (3B7D85BC)
    ba6b8000 ba6b8d00 dxgthk dxgthk.sys Fri Aug 17 21:53:12 2001 (3B7D8438)
    ba751000 ba751b80 Null Null.SYS Fri Aug 17 21:47:39 2001 (3B7D82EB)
    bf000000 bf011600 dxg dxg.sys Sun Apr 13 19:38:27 2008 (48025323)
    bf012000 bf5d8e00 nv4_disp nv4_disp.dll Wed Sep 17 18:38:33 2008 (48D14099)
    bf800000 bf9c2c80 win32k win32k.sys Mon Sep 15 13:12:42 2008 (48CE513A)
    bffa0000 bffe5c00 ATMFD ATMFD.DLL Mon Apr 14 01:09:55 2008 (4802A0D3)

    Unloaded modules:
    b43d8000 b4403000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b43d8000 b4403000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b45e0000 b460b000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b5487000 b54b2000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba781000 ba782000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b5db5000 b5de0000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba178000 ba185000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b61dd000 b61eb000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b5de0000 b5e03000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba620000 ba622000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba2f8000 ba301000 processr.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b985e000 b9862000 kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba4b0000 ba4b5000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba59c000 ba59f000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
     
    velectro,
    #17
  19. 2009/01/26
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Well, I'm glad that we were at least able to resolve the case of the missing log file :) Our apologies for the inconvenience caused.

    However, although we now have the full detail, I am no closer to resolving the problem as I am no expert in deciphering the nitty gritty of these logs - as was posted earlier ....
    I've researched kmixer.sys exhaustively on Google - plenty of problems, but no definitive answers in terms of fixing it that I could find.

    Are the restarts associated with any particular activity on the computer or are they completely random?

    A hardware problem remains a possibility - there is the problem of the computer failing to boot with the memory module in a specific slot, but I'm not going to stick my neck out and say - 'It's hardware'
     
    PeteC,
    #18
  20. 2009/01/26
    velectro

    velectro Inactive Thread Starter

    Joined:
    2009/01/22
    Messages:
    35
    Likes Received:
    0
    Hi PeteC, thank you for all you hard work, i do appreciate it :)

    The restarts definately happen when i start the game "obscure" and at other times to, but less definitively connected with any one activity - eg i could just be surfing. Next time there is a non-game restart I'll post that minidump too...and hopefully someone who has expert knowledge with analyzing them comes on here soon.
     
    velectro,
    #19
  21. 2009/01/26
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Yes, do that - it may shed some further light on the problem.
    For testing purposes I would uninstall the game and see if the restarts continue. There's very little on Google re 'ObsCure'.
     
    PeteC,
    #20
Page 1 of 3

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...