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.

Windows randomly locks up goes to BSOD, restarts with error codes.

Discussion in 'Windows XP' started by JeffWolf, 2008/05/05.

  1. 2008/05/05
    JeffWolf

    JeffWolf Inactive Thread Starter

    Joined:
    2008/05/05
    Messages:
    7
    Likes Received:
    0
    Computer:
    Intel Wasp Motherboard
    Intel Pentium 4 Prescott @ 3.4
    Sapphire ATI x1950 GT
    2 Gigs of Ram 2x512 1x1024 Running at same clock speed
    250 Gb HD w/ 500 Gb HD
    NAV 2008


    Windows randomly locks up and would go right to a black screen and then restarts. I changed the setting to go to BSOD and got this error code.

    0x0000007f (0x0000000D, 0x00000000, 0x00000000, 0x00000000)

    I restart the computer and am given:
    Your system has recovered from a serious error:
    I view the technical data:
    C:\DOCUME~1\Jeff\LOCALS~1\Temp\WERabd0.dir00\Mini050408-01.dmp
    C:\DOCUME~1\Jeff\LOCALS~1\Temp\WERabd0.dir00\sysdata.xml

    Minidump info:
    <SNIP>

    I installed a new motherboard and processor but it did work fine for a period of time. This started happening about 2 weeks ago.
    Over heating is not the cause as I have an Antec 900 case and the processor is between 130-140 (Fine for a prescott) and the case temp is about 100 degrees.

    Could someone please point me in the right direction?
    Thanks.
     
    Last edited: 2008/05/05
  2. 2008/05/05
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    JeffWolf - Welcome to the Board :)

    High probability it is a hardware problem ....

    General causes of "STOP 0x0000007F" errors
    You have replaced the mobo and CPU - this leaves the memory - I suggest you check it out, noting
    So the best way - having checked that the RAM is compatible with your motherboard and in the recommended slots is to remove the 1 gig stick - test, switch the 2 512 sticks to another pair of slots, test until all combinations are covered. Remove the 2 512 sticks and replace with the i gig stick, test, switch around the slots, test and see what comes up.
     

  3. to hide this advert.

  4. 2008/05/05
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    You edited while I posted - that in itself is not much use. Run the dump through our dump data collection tool and post the log here noting ....
    Normally that would be my first suggestion followed by the memory check, but my hunch is that you have a memory problem.
     
  5. 2008/05/05
    JeffWolf

    JeffWolf Inactive Thread Starter

    Joined:
    2008/05/05
    Messages:
    7
    Likes Received:
    0
    Thank you Pete for the speedy reply. I will try taking out the memory and seeing if a certain combination works.

    Question: Should the two 512 sticks be in slots A0 and A1 or slots A0 and B0?
    Right now I have the two 512s next to each other in A0 and A1 and the 1024 Dimm in B0. Is that correct?
     
  6. 2008/05/06
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    I cannot tell - you need to refer to the motherboard manual for memory configuration. My experience is entirely with Asus boards and I have not set eyes on an Intel board :)
     
  7. 2008/05/06
    Rockster2U

    Rockster2U Geek Member

    Joined:
    2002/04/01
    Messages:
    3,181
    Likes Received:
    9
    Jeff:

    Pete's got you on the right path. I too think memory is your most likely problem. In your current setup, although you added a 1 gig stick to your two original 512's, you have now circumvented your previous dual channel memory configuration. If you return to the two 512's, your problem probably goes away. If you want more memory, I would suggest you purchase matched pairs of high end memory. Two sticks can run T1 timings but 4 sticks of anything will drop you back to T2 timings. And, 3 sticks forces single channel performance.

    ;)

    edit: Aside from what I said above, in an effort to clarify the current problem, I suspect your 1 gig memory module is not quite up to snuff. Not all memory is created equal - one gets what they pay for.
     
    Last edited: 2008/05/06
  8. 2008/05/06
    JeffWolf

    JeffWolf Inactive Thread Starter

    Joined:
    2008/05/05
    Messages:
    7
    Likes Received:
    0
    Alright then, will try to run 2x512 Dimms first. The 1 Gig stick is a simpletech memory module. It was a certified Gateway upgrade at the time and is guaranteed for life. Yes I had a gateway and as time went on I swapped out guts until I now have a home built PC.

    One interesting little tidbit though, After posting yesterday afternoon I started a Norton Anti-Virus scan that ran throughout the whole night. NO BSOD. I thought cool and after returning from school I jiggled the mouse to take the computer out of sleep mode. I examined the findings of Norton and then left for work. Only after I took the computer out of sleep mode and the scan was not running did it go to a BSOD. Does this help you diagnose the issue? Are stop codes being misinterpreted by the memory?

    The 2 x 512's just went to Blue Screen in Dual Channel Mode.
    Checking the 1 x 1024 now.

    Lo and behold the 1x1024 module in the slot A0 seems to be working fine. Is stable and although I am missing a gig of memory. It is working and has not shown a blue screen. I will let this go to the morning before I give a final assessment as to whether it is fixed or not.
     
    Last edited: 2008/05/06
  9. 2008/05/07
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Jeff

    Better to make a new post rather than edit an older one - we get no email notification for edits. I saw your edit by chance.

    I'll leave Rockster to comment on the dual mode situation - he has a far greater depth of knowledge on the ins and outs of memory :)
     
  10. 2008/05/07
    JeffWolf

    JeffWolf Inactive Thread Starter

    Joined:
    2008/05/05
    Messages:
    7
    Likes Received:
    0
    I have tried all memory combinations. Nothing works. The one that lasted the longest was the 1 Gb stick in Dimm A0 in single channel dynamic paging mode.

    I still get blue screens with everything.

    So whats next?
     
  11. 2008/05/08
    JeffWolf

    JeffWolf Inactive Thread Starter

    Joined:
    2008/05/05
    Messages:
    7
    Likes Received:
    0
    Have had the computer sitting here in safe mode since my last post. Has not gone to a BSOD. Does this help at all for diagnosis?
     
  12. 2008/05/08
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    If it appears to be OK in Safe Mode may well be a driver issue - post a couple of dump data logs as I suggested earlier in the thread.
     
  13. 2008/05/12
    JeffWolf

    JeffWolf Inactive Thread Starter

    Joined:
    2008/05/05
    Messages:
    7
    Likes Received:
    0
    Memory Dump Log
    Hope this helps.



    Opened log file 'c:\debuglog.txt'

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini050808-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 2) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    Debug session time: Thu May 8 18:50:51.796 2008 (GMT-4)
    System Uptime: 0 days 0:21:08.514
    Loading Kernel Symbols
    ....................................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {d, 0, 0, 0}

    *** ERROR: Module load completed but symbols could not be loaded for ati2mtag.sys
    Probably caused by : ati2mtag.sys ( ati2mtag+102550 )

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

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

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault). The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
    use .trap on that value
    Else
    .trap on the appropriate frame will show where the trap was taken
    (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000d, EXCEPTION_GP_FAULT
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000

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


    BUGCHECK_STR: 0x7f_d

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    LAST_CONTROL_TRANSFER: from f6640550 to 804e122c

    STACK_TEXT:
    a76acd24 f6640550 badb0d00 a289051e 804e2ed8 nt!KiSystemFatalException+0xf
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a76acd94 f66b534c 8003f400 f66b5585 10012fb6 ati2mtag+0x102550
    a76acd9c f66b5585 10012fb6 10012fba 10010000 ati2mtag+0x17734c
    a76acddc 804ec781 f73a3b85 84bfc3c8 00000000 ati2mtag+0x177585
    a76acde0 f73a3b84 84bfc3c8 00000000 0000027f nt!KiThreadStartup+0x16
    a76acde4 84bfc3c8 00000000 0000027f 07ff0000 NDIS!___PchSym_+0xc
    a76acde8 00000000 0000027f 07ff0000 00000000 0x84bfc3c8


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    ati2mtag+102550
    f6640550 640fb60551000000 movzx eax,byte ptr fs:[51h]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: ati2mtag+102550

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: ati2mtag

    IMAGE_NAME: ati2mtag.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47561512

    FAILURE_BUCKET_ID: 0x7f_d_ati2mtag+102550

    BUCKET_ID: 0x7f_d_ati2mtag+102550

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

    eax=ffdff13c ebx=00000000 ecx=00000000 edx=10010030 esi=10012fba edi=f6640550
    eip=804e122c esp=a76acd0c ebp=a76acd24 iopl=0 nv up di ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000086
    nt!KiSystemFatalException+0xf:
    804e122c c3 ret
    ChildEBP RetAddr Args to Child
    a76acd24 f6640550 badb0d00 a289051e 804e2ed8 nt!KiSystemFatalException+0xf (FPO: [0,0] TrapFrame @ a76acd24)
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a76acd94 f66b534c 8003f400 f66b5585 10012fb6 ati2mtag+0x102550
    a76acd9c f66b5585 10012fb6 10012fba 10010000 ati2mtag+0x17734c
    a76acddc 804ec781 f73a3b85 84bfc3c8 00000000 ati2mtag+0x177585
    a76acde0 f73a3b84 84bfc3c8 00000000 0000027f nt!KiThreadStartup+0x16
    a76acde4 84bfc3c8 00000000 0000027f 07ff0000 NDIS!___PchSym_+0xc
    a76acde8 00000000 0000027f 07ff0000 00000000 0x84bfc3c8
    start end module name
    804d7000 806fd000 nt ntkrnlmp.exe Wed Feb 28 04:08:32 2007 (45E54690)
    806fd000 8071dd00 hal halmacpi.dll Wed Aug 04 01:59:09 2004 (41107B2D)
    a647c000 a64bc280 HTTP HTTP.sys Thu Mar 16 20:33:09 2006 (441A03C5)
    a64bd000 a64cf720 NAVENG NAVENG.SYS Thu Feb 28 20:21:51 2008 (47C75E2F)
    a64f8000 a65d0f80 NAVEX15 NAVEX15.SYS Thu Feb 28 20:20:50 2008 (47C75DF2)
    a65d1000 a661a000 SRTSP SRTSP.SYS Mon Jan 21 23:58:54 2008 (4795780E)
    a68e2000 a68ec000 secdrv secdrv.sys Wed Sep 13 09:18:32 2006 (45080528)
    a6b1a000 a6b1d800 asyncmac asyncmac.sys Wed Aug 04 02:05:02 2004 (41107C8E)
    a6d9a000 a6deb480 srv srv.sys Mon Aug 14 06:34:39 2006 (44E051BF)
    a6edc000 a6f07d80 mrxdav mrxdav.sys Tue Dec 18 04:51:33 2007 (47679825)
    a70ee000 a712c000 SymIDSCo SymIDSCo.sys Thu Feb 07 19:26:34 2008 (47ABA1BA)
    a712c000 a7142000 SYMFW SYMFW.SYS unavailable (00000000)
    a7142000 a7156400 wdmaud wdmaud.sys Wed Jun 14 05:00:44 2006 (448FD03C)
    a723b000 a723de80 MaVc2K MaVc2K.sys Mon Jan 15 22:44:45 2007 (45AC4A2D)
    a72af000 a72bdd80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
    a7317000 a731b000 SYMREDRV SYMREDRV.SYS unavailable (00000000)
    a757f000 a758ca80 nwlnkspx nwlnkspx.sys Fri Aug 17 16:54:16 2001 (3B7D8478)
    a762f000 a7644980 nwlnkipx nwlnkipx.sys Wed Aug 04 02:03:29 2004 (41107C31)
    a7761000 a7764280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
    a77dd000 a77ec700 nwlnknb nwlnknb.sys Fri Aug 17 16:54:16 2001 (3B7D8478)
    a784d000 a7870000 Fastfat Fastfat.SYS Wed Aug 04 02:14:15 2004 (41107EB7)
    a9a98000 a9aaf480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
    a9ab0000 a9ac1000 LMouKE LMouKE.sys unavailable (00000000)
    a9af9000 a9b01000 SYMIDS SYMIDS.SYS unavailable (00000000)
    a9b01000 a9b09000 SYMNDIS SYMNDIS.SYS unavailable (00000000)
    a9b39000 a9b57000 EraserUtilRebootDrv EraserUtilRebootDrv.sys Thu Jan 17 21:44:27 2008 (4790128B)
    a9b57000 a9bb7000 eeCtrl eeCtrl.sys Thu Jan 17 21:44:27 2008 (4790128B)
    a9bb7000 a9c25a00 mrxsmb mrxsmb.sys Fri May 05 05:41:42 2006 (445B1DD6)
    a9c26000 a9c50a00 rdbss rdbss.sys Fri May 05 05:47:55 2006 (445B1F4B)
    a9c51000 a9cc1000 SPBBCDrv SPBBCDrv.sys Wed Jan 16 22:24:17 2008 (478ECA61)
    a9d61000 a9d82d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
    a9d83000 a9daac00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
    a9dab000 a9dd0000 SYMEVENT SYMEVENT.SYS Mon Jan 14 18:29:24 2008 (478BF054)
    a9dd0000 a9df0f00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
    a9df1000 a9e1e000 SYMTDI SYMTDI.SYS unavailable (00000000)
    a9e1e000 a9e75e80 tcpip tcpip.sys Tue Oct 30 13:20:52 2007 (472767F4)
    a9e76000 a9e88400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
    a9ecd000 a9ecf900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
    aa5ba000 aa656000 ctac32k ctac32k.sys Fri Aug 11 02:45:14 2006 (44DC277A)
    aa656000 aa67d000 ctsfm2k ctsfm2k.sys Fri Aug 11 02:45:18 2006 (44DC277E)
    aa67d000 aa6aa000 emupia2k emupia2k.sys Fri Aug 11 02:45:17 2006 (44DC277D)
    aa6aa000 aa7ae000 ha10kx2k ha10kx2k.sys Fri Aug 11 02:45:24 2006 (44DC2784)
    aa7ae000 aa7e0000 hap17v2k hap17v2k.sys Fri Aug 11 02:45:26 2006 (44DC2786)
    bf000000 bf011580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
    bf012000 bf058000 ati2dvag ati2dvag.dll Tue Dec 04 22:04:08 2007 (47561528)
    bf058000 bf0d2000 ati2cqag ati2cqag.dll Tue Dec 04 21:11:17 2007 (475608C5)
    bf0d2000 bf140000 atikvmag atikvmag.dll Tue Dec 04 21:19:14 2007 (47560AA2)
    bf140000 bf170000 atiok3x2 atiok3x2.dll Tue Dec 04 21:14:59 2007 (475609A3)
    bf170000 bf4774a0 ati3duag ati3duag.dll Tue Dec 04 21:44:52 2007 (475610A4)
    bf478000 bf608700 ativvaxx ativvaxx.dll Tue Dec 04 21:33:46 2007 (47560E0A)
    bf800000 bf9c2800 win32k win32k.sys Wed Mar 19 05:46:46 2008 (47E0E106)
    f622e000 f6286e80 update update.sys Mon Apr 23 06:32:54 2007 (462C8B56)
    f6287000 f6297e00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
    f6298000 f62ae680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
    f62f9000 f635f000 ab3wsbj6 ab3wsbj6.SYS unavailable (00000000)
    f635f000 f6372900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
    f6373000 f6391ec0 Mtlmnt5 Mtlmnt5.sys Wed Jan 28 07:54:43 2004 (4017B113)
    f6392000 f63f4de0 slntamr slntamr.sys Wed Jan 28 08:15:32 2004 (4017B5F4)
    f63f5000 f6428000 ctoss2k ctoss2k.sys Fri Aug 11 02:45:23 2006 (44DC2783)
    f6428000 f644a680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
    f644b000 f646e980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
    f646f000 f64e9000 ctaud2k ctaud2k.sys unavailable (00000000)
    f64e9000 f650be80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
    f650c000 f6529a00 e1000325 e1000325.sys Tue Mar 11 09:21:36 2003 (3E6DE2E0)
    f652a000 f653d780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
    f653e000 f6829000 ati2mtag ati2mtag.sys Tue Dec 04 22:03:46 2007 (47561512)
    f6839000 f6841880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
    f6849000 f6851d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
    f6859000 f6863000 SRTSPX SRTSPX.SYS unavailable (00000000)
    f6899000 f68a1700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
    f68a9000 f68b1700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
    f71f5000 f71f7580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
    f7201000 f7204c80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
    f7205000 f7208360 SlWdmSup SlWdmSup.sys Wed Jan 28 07:20:42 2004 (4017A91A)
    f7209000 f720c040 ntiowp ntiowp.SYS Fri Oct 20 06:57:19 2006 (4538AB8F)
    f7219000 f721b280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
    f7229000 f722cf00 MODEMCSA MODEMCSA.sys Fri Aug 17 16:57:37 2001 (3B7D8541)
    f7275000 f728f580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
    f7290000 f731c400 Ntfs Ntfs.sys Fri Feb 09 06:10:31 2007 (45CC56A7)
    f731d000 f7333780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
    f7334000 f7345f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
    f7346000 f7365780 fltmgr fltmgr.sys Mon Aug 21 05:14:57 2006 (44E97991)
    f7366000 f737d480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
    f737e000 f739c880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
    f739d000 f73c9a80 NDIS NDIS.SYS Wed Aug 04 02:14:27 2004 (41107EC3)
    f73ca000 f73f5000 SSIDRV SSIDRV.SYS Fri Jun 15 15:19:06 2007 (4672E62A)
    f73f5000 f7405a80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
    f7406000 f7433d80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
    f7434000 f744b800 SCSIPORT SCSIPORT.SYS Wed Aug 04 01:59:39 2004 (41107B4B)
    f744c000 f7536000 sptd sptd.sys unavailable (00000000)
    f7557000 f755fc00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
    f7567000 f7570000 SSHRMD SSHRMD.SYS Fri Jun 15 15:19:13 2007 (4672E631)
    f7577000 f7580000 SSFS0BB8 SSFS0BB8.SYS Fri Jun 15 15:19:09 2007 (4672E62D)
    f7587000 f7591500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
    f7597000 f75a3c80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
    f75a7000 f75afe00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
    f75b7000 f75c3200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
    f75c7000 f75d1580 agp440 agp440.sys Wed Aug 04 02:07:40 2004 (41107D2C)
    f7607000 f7616900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
    f7617000 f7624000 sskbfd sskbfd.sys Fri Jun 15 15:19:11 2007 (4672E62F)
    f76c7000 f76d3000 ATITool ATITool.sys Thu Dec 29 18:04:24 2005 (43B46B78)
    f76d7000 f76dfd00 intelppm intelppm.sys Wed Aug 04 01:59:19 2004 (41107B37)
    f76e7000 f76f5b80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
    f76f7000 f7706d80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
    f7707000 f7711380 imapi imapi.sys Wed Aug 04 02:00:12 2004 (41107B6C)
    f7717000 f7723180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
    f7727000 f7735080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
    f7737000 f7743880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
    f7747000 f7751200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
    f7757000 f7762d00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
    f7767000 f776f900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
    f7777000 f7780f00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
    f7787000 f7790480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
    f77c7000 f77d5100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
    f77d7000 f77db880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
    f77df000 f77e5200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
    f77e7000 f77eb900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
    f7877000 f787b580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
    f787f000 f7883080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
    f7887000 f788c020 wanatw4 wanatw4.sys Tue Jul 16 11:23:14 2002 (3D343A62)
    f788f000 f7895000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
    f7897000 f789ca00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
    f789f000 f78a6000 SymIM SymIM.sys unavailable (00000000)
    f78af000 f78b4000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
    f78bf000 f78c5180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
    f78c7000 f78cc200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
    f78cf000 f78d3a80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
    f78d7000 f78de880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
    f78df000 f78e7000 ntiopnp ntiopnp.SYS Mon Feb 12 14:26:28 2007 (45D0BF64)
    f78ef000 f78f6b80 usbccgp usbccgp.sys Wed Aug 04 02:08:45 2004 (41107D6D)
    f78f7000 f78fd780 USBSTOR USBSTOR.SYS Wed Aug 04 02:08:44 2004 (41107D6C)
    f790f000 f7917000 CO_Mon CO_Mon.sys unavailable (00000000)
    f791f000 f7923b00 HidBatt HidBatt.sys Fri Aug 17 16:57:58 2001 (3B7D8556)
    f7927000 f792e000 LHidKE LHidKE.Sys unavailable (00000000)
    f792f000 f7933500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
    f793f000 f7944000 usbuhci usbuhci.sys Wed Aug 04 02:08:34 2004 (41107D62)
    f7947000 f794d800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
    f794f000 f7957000 ctprxy2k ctprxy2k.sys Fri Aug 11 02:45:39 2006 (44DC2793)
    f7957000 f795e580 Modem Modem.SYS Wed Aug 04 02:08:04 2004 (41107D44)
    f795f000 f7965b00 fdc fdc.sys Wed Aug 04 01:59:25 2004 (41107B3D)
    f7967000 f796a000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
    f796b000 f796d480 compbatt compbatt.sys Fri Aug 17 16:57:58 2001 (3B7D8556)
    f796f000 f7972700 BATTC BATTC.SYS Fri Aug 17 16:57:52 2001 (3B7D8550)
    f7973000 f7976580 RecAgent RecAgent.sys Tue Jan 13 08:03:28 2004 (4003ECA0)
    f7a37000 f7a39f80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
    f7a3b000 f7a3ea00 kbdhid kbdhid.sys Wed Aug 04 01:58:33 2004 (41107B09)
    f7a47000 f7a49580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
    f7a4f000 f7a52c80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
    f7a57000 f7a58b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
    f7a59000 f7a5a100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
    f7a5b000 f7a5d000 speedfan speedfan.sys unavailable (00000000)
    f7a6d000 f7a6f000 SYMDNS SYMDNS.SYS unavailable (00000000)
    f7a95000 f7a96a80 ParVdm ParVdm.SYS Fri Aug 17 16:49:49 2001 (3B7D836D)
    f7aa9000 f7aaa100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
    f7aab000 f7aac280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
    f7aaf000 f7ab0f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
    f7ab1000 f7ab2080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
    f7ab5000 f7ab6080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
    f7ab7000 f7ab8080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
    f7ac1000 f7ac2100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
    f7b1f000 f7b1fd00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
    f7b20000 f7b20680 giveio giveio.sys Wed Apr 03 22:33:25 1996 (316334F5)
    f7b74000 f7b74c00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
    f7b82000 f7b82d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
    f7c00000 f7c00b80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)

    Unloaded modules:
    a60b9000 a60e4000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a70a0000 a70cb000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7c99000 f7c9a000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a70cb000 a70ee000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a727f000 a728c000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    a728f000 a729d000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7a73000 f7a75000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f6889000 f6892000 processr.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f721d000 f7221000 kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f68b9000 f68c6000 i8042prt.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f78b7000 f78bc000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7221000 f7224000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
     
  14. 2008/05/13
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Although I have to say .....
    it would appear that the cause of that crash was the ATI drivers ....
    I suggest you uninstall and reinstall - look for updates and see what happens.

    A single dump log is not necessarily conclusive and it would be helpful to see more.
     
  15. 2008/05/13
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    That's your display driver, nearly 4 years old. Check if there's an update for it!
     
  16. 2008/05/17
    JeffWolf

    JeffWolf Inactive Thread Starter

    Joined:
    2008/05/05
    Messages:
    7
    Likes Received:
    0

    I am running a Sapphire ATI x1950 GT. The latest set of drivers does not work with the card so I am using the set of drivers that came on the CD. It's not 4 years old though. Is there still something left behind from my older cards installations. (X850 and before that 9600 pro) ?
     
  17. 2008/05/17
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    See if you can find an 'intermediate' set of drivers - newer than those on the CD, but not the latest.

    If you have any further dump data logs to post - let's see them.
     
  18. 2008/05/18
    Rockster2U

    Rockster2U Geek Member

    Joined:
    2002/04/01
    Messages:
    3,181
    Likes Received:
    9
    Another thought here - you may want to uninstall anything you can that is ATI related - drivers, Catalyst Control & etc. and then run Driver Cleaner Pro to get at all the ATI remnants. Then try your newest drivers or as Pete suggested, something almost new.

    Be careful with Driver Cleaner Pro but I think it will very helpful to you.

    ;)

    edit: Here's the link
     
    Last edited: 2008/05/18
  19. 2008/05/19
    bdesmond

    bdesmond Inactive

    Joined:
    2008/05/19
    Messages:
    36
    Likes Received:
    0
    Given the specifics of this crash, I'm inclined to believe you need to figure out a way to update the drivers. It's unlikely this is hardware related.
     

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.