BSOD while gaming

[dleslie]

Hi!

I'm new to the forums so I just wanted to say thanks for checking out my post here.

I've been experiencing some blue screens while playing SC2 and Mass Effect 2. I'm kind of confused about it since I've done all I know how to when it comes to stability checking; memtest, chkdsk, occt etc. all come up golden. So, I was hoping to crowdsource a little expertise.

This is a partly new build I had to throw together in a hurry when my old system bit the big one.

MSI P55A-G55
i3-550
8gig Mushkin 1333
2x 250gig WD hdd (carryover from old rig, 4 years old)
8800gt (also 4 year old carryover)
Antec Truepower 750 psu

Thanks for your time,
Dave

 

[JMH]

Hi!

I'm new to the forums so I just wanted to say thanks for checking out my post here.

I've been experiencing some blue screens while playing SC2 and Mass Effect 2. I'm kind of confused about it since I've done all I know how to when it comes to stability checking; memtest, chkdsk, occt etc. all come up golden. So, I was hoping to crowdsource a little expertise.

This is a partly new build I had to throw together in a hurry when my old system bit the big one.

MSI P55A-G55
i3-550
8gig Mushkin 1333
2x 250gig WD hdd (carryover from old rig, 4 years old)
8800gt (also 4 year old carryover)
Antec Truepower 750 psu

Thanks for your time,
Dave

Hello Dave,
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kb) in the drop down box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.
Until a .dmp file is generated, the Minidump folder may not exist.

 

[dleslie]

Hi,

Apologies... I thought I had them all attached.

Take two...

 

[zigzag3143]

Hi,

Apologies... I thought I had them all attached.

Take two...

Hi Dleslie and welcome to seven forums

The crash was probably caused by your afd.sys which is part of the operating system. To correct this problem I would run something called system file check to verify and repair your system files.

There is a report at the end and we need the results

To run SFC go to start>cmd>right click and run as admin>sfc /scannow.

Dont forget to tell us the results.


Ken

 

[dleslie]

Hi!

Thanks for your help.

The results: Windows Resource Protection did not find any integrity violations.

I also have these files I whipped up according to the forum's format thread. Maybe they will help.

Dave

 

[dleslie]

bump

 

[dleslie]

Latest and greatest BSOD action...

 

[DeanP]

Hello Dave,

I would first remove AVG including Identity Protection. AVG is a known issue of causing BSOD on some Windows 7 System. Use this removal tool to delete all the left overs when AVG is uninstalled: AVG - Download tools
You may use Microsoft Security Essentials (MSE) or Avast Anti-Virus in it's place,

MSE: http://www.microsoft.com/security_essentials/
Avast: avast! - Download Free Antivirus Software or Internet Security
These two AV do not intend to cause BSOD.
Also, the dump blames AVG.

Also, look at this driver.

RTCore64.sys Wed May 25 18:39:12 2005 - RivaTuner/EVGA Precision/MSI Afterburner
Uninstall it - known cause of BSOD because they use old driver and causing conflicts

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002dfc9e7, fffff8800a153868, fffff8800a1530d0}
Probably caused by : ntkrnlmp.exe ( nt!PfTLocateEntryInfo+87 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002dfc9e7, The address that the exception occurred at
Arg3: fffff8800a153868, Exception Record Address
Arg4: fffff8800a1530d0, Context Record Address
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!PfTLocateEntryInfo+87
fffff800`02dfc9e7 c3              ret
EXCEPTION_RECORD:  fffff8800a153868 -- (.exr 0xfffff8800a153868)
ExceptionAddress: fffff80002dfc9e7 (nt!PfTLocateEntryInfo+0x0000000000000087)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: ffffffffffffffff
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
CONTEXT:  fffff8800a1530d0 -- (.cxr 0xfffff8800a1530d0)
rax=fffff8a0080e8010 rbx=fffff8800a153b88 rcx=00000000000017fc
rdx=0000000000009000 rsi=fffff8800a153b00 rdi=0000000000000001
rip=fffff80002dfc9e7 rsp=fffff8800a153aa8 rbp=000000000000ffff
 r8=0000000000009800  r9=fffff8a0080dc000 r10=00000000000094cc
r11=fffff8800a153b00 r12=fffff8a00adc0020 r13=0000000000000378
r14=fffff8a008097000 r15=0000000000002371
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!PfTLocateEntryInfo+0x87:
fffff800`02dfc9e7 c3              ret
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  ffffffffffffffff
EXCEPTION_PARAMETER2:  0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc30e0
 0000000000000000 
FOLLOWUP_IP: 
nt!PfTLocateEntryInfo+87
fffff800`02dfc9e7 c3              ret
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from fffff80002e09349 to fffff80002dfc9e7
STACK_TEXT:  
fffff880`0a153aa8 fffff800`02e09349 : 00000000`00000010 00000000`00010202 fffff880`0a153ad8 00000000`00000018 : nt!PfTLocateEntryInfo+0x87
fffff880`0a153ab0 fffff800`02eaa6ad : fffff8a0`0809a798 00000000`00000001 fffff8a0`0ade3738 fffff800`02e19735 : nt!PfTGetLogEntryInfo+0x79
fffff880`0a153ae0 fffff800`02ef8a60 : fffff880`0a153c10 fffff8a0`08097018 fffff8a0`0adc0000 fffff8a0`0ab63000 : nt!PfTCreateTraceDump+0x31d
fffff880`0a153be0 fffff800`02efe653 : fffffa80`0a7f1b01 00000000`00000080 fffffa80`06d0b840 fffff800`02c19568 : nt!PfTGenerateTrace+0x10
fffff880`0a153c10 fffff800`02d2e7c6 : ffffffff`ff676980 fffffa80`0a7f1b60 fffff880`0a153db0 fffffa80`0a7f1b60 : nt!PfTLoggingWorker+0x113
fffff880`0a153d40 fffff800`02a69c26 : fffff880`03164180 fffffa80`0a7f1b60 fffffa80`0a482060 fffff880`01265534 : nt!PspSystemThreadStartup+0x5a
fffff880`0a153d80 00000000`00000000 : fffff880`0a154000 fffff880`0a14e000 fffff880`0a153790 00000000`00000000 : nt!KxStartSystemThread+0x16

SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!PfTLocateEntryInfo+87
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd
STACK_COMMAND:  .cxr 0xfffff8800a1530d0 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_nt!PfTLocateEntryInfo+87
BUCKET_ID:  X64_0x7E_nt!PfTLocateEntryInfo+87
Followup: MachineOwner
---------
3: kd> lmtsmn
start             end                 module name
fffff880`00f74000 fffff880`00fcb000   ACPI     ACPI.sys     Tue Jul 14 11:19:34 2009 (4A5BC106)
fffff880`02ed3000 fffff880`02f5d000   afd      afd.sys      Tue Jul 14 11:21:40 2009 (4A5BC184)
fffff880`043b1000 fffff880`043c7000   AgileVpn AgileVpn.sys Tue Jul 14 12:10:24 2009 (4A5BCCF0)
fffff880`011de000 fffff880`011e9000   amdxata  amdxata.sys  Wed May 20 05:56:59 2009 (4A12F2EB)
fffff880`0797c000 fffff880`07987000   asyncmac asyncmac.sys Tue Jul 14 12:10:13 2009 (4A5BCCE5)
fffff880`00ea5000 fffff880`00eae000   atapi    atapi.sys    Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`010f1000 fffff880`0111b000   ataport  ataport.SYS  Tue Jul 14 11:19:52 2009 (4A5BC118)
fffff880`0723f000 fffff880`07273000   AVGIDSDriver AVGIDSDriver.Sys Wed Aug 04 10:24:45 2010 (4C58972D)
fffff880`016df000 fffff880`016e9000   AVGIDSEH AVGIDSEH.Sys Tue Sep 14 10:46:38 2010 (4C8EA9CE)
fffff880`07313000 fffff880`0731f000   AVGIDSFilter AVGIDSFilter.Sys Wed Aug 04 10:23:21 2010 (4C5896D9)
fffff880`040f0000 fffff880`04140000   avgldx64 avgldx64.sys Wed Dec 08 15:01:55 2010 (4CFEE713)
fffff880`0142a000 fffff880`01439000   avgmfx64 avgmfx64.sys Tue Sep 07 12:49:14 2010 (4C858C0A)
fffff880`016d5000 fffff880`016df000   avgrkx64 avgrkx64.sys Tue Sep 07 12:49:37 2010 (4C858C21)
fffff880`02e2d000 fffff880`02e8e000   avgtdia  avgtdia.sys  Sat Nov 13 00:08:42 2010 (4CDD203A)
fffff880`01bf8000 fffff880`01bff000   Beep     Beep.SYS     Tue Jul 14 12:00:13 2009 (4A5BCA8D)
fffff880`040df000 fffff880`040f0000   blbdrive blbdrive.sys Tue Jul 14 11:35:59 2009 (4A5BC4DF)
fffff880`05dca000 fffff880`05de8000   bowser   bowser.sys   Tue Jul 14 11:23:50 2009 (4A5BC206)
fffff960`00700000 fffff960`00727000   cdd      cdd.dll      unavailable (00000000)
fffff880`10000000 fffff880`1001d000   cdfs     cdfs.sys     Tue Jul 14 11:19:46 2009 (4A5BC112)
fffff880`01400000 fffff880`0142a000   cdrom    cdrom.sys    Tue Jul 14 11:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Tue Jul 14 13:32:13 2009 (4A5BE01D)
fffff880`0159d000 fffff880`015cd000   CLASSPNP CLASSPNP.SYS Tue Jul 14 11:19:58 2009 (4A5BC11E)
fffff880`00d39000 fffff880`00d97000   CLFS     CLFS.SYS     Tue Jul 14 11:19:57 2009 (4A5BC11D)
fffff880`014d5000 fffff880`01548000   cng      cng.sys      Tue Jul 14 11:49:40 2009 (4A5BC814)
fffff880`043a1000 fffff880`043b1000   CompositeBus CompositeBus.sys Tue Jul 14 12:00:33 2009 (4A5BCAA1)
fffff880`0731f000 fffff880`07328000   cpuz135_x64 cpuz135_x64.sys Wed Nov 10 02:33:36 2010 (4CD94DB0)
fffff880`02fe7000 fffff880`02ff5000   crashdmp crashdmp.sys Tue Jul 14 12:01:01 2009 (4A5BCABD)
fffff880`040c1000 fffff880`040df000   dfsc     dfsc.sys     Tue Jul 14 11:23:44 2009 (4A5BC200)
fffff880`040b2000 fffff880`040c1000   discache discache.sys Tue Jul 14 11:37:18 2009 (4A5BC52E)
fffff880`01a1b000 fffff880`01a31000   disk     disk.sys     Tue Jul 14 11:19:57 2009 (4A5BC11D)
fffff880`047c0000 fffff880`047e2000   drmk     drmk.sys     Tue Jul 14 13:01:25 2009 (4A5BD8E5)
fffff880`1001d000 fffff880`10026000   dump_atapi dump_atapi.sys Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`017dd000 fffff880`017e9000   dump_dumpata dump_dumpata.sys Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`017e9000 fffff880`017fc000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 11:21:51 2009 (4A5BC18F)
fffff880`05c77000 fffff880`05c83000   Dxapi    Dxapi.sys    Tue Jul 14 11:38:28 2009 (4A5BC574)
fffff880`10c85000 fffff880`10d79000   dxgkrnl  dxgkrnl.sys  Wed Jan 26 17:22:56 2011 (4D3FA1A0)
fffff880`10d79000 fffff880`10dbf000   dxgmms1  dxgmms1.sys  Wed Jan 26 17:22:12 2011 (4D3FA174)
fffff880`05c41000 fffff880`05c77000   fastfat  fastfat.SYS  Tue Jul 14 11:23:28 2009 (4A5BC1F0)
fffff880`0104c000 fffff880`01060000   fileinfo fileinfo.sys Tue Jul 14 11:34:25 2009 (4A5BC481)
fffff880`01000000 fffff880`0104c000   fltmgr   fltmgr.sys   Tue Jul 14 11:19:59 2009 (4A5BC11F)
fffff880`01559000 fffff880`01563000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 11:19:45 2009 (4A5BC111)
fffff880`01563000 fffff880`0159d000   fvevol   fvevol.sys   Sat Sep 26 14:34:26 2009 (4ABD7DB2)
fffff880`0168b000 fffff880`016d5000   fwpkclnt fwpkclnt.sys Tue Jul 14 11:21:08 2009 (4A5BC164)
fffff880`0438b000 fffff880`04398000   GEARAspiWDM GEARAspiWDM.sys Tue May 19 00:17:04 2009 (4A1151C0)
fffff800`02ff8000 fffff800`03041000   hal      hal.dll      Tue Jul 14 13:27:36 2009 (4A5BDF08)
fffff880`10dd0000 fffff880`10df4000   HDAudBus HDAudBus.sys Tue Jul 14 12:06:13 2009 (4A5BCBF5)
fffff880`04727000 fffff880`04783000   HdAudio  HdAudio.sys  Tue Jul 14 12:06:59 2009 (4A5BCC23)
fffff880`04030000 fffff880`04049000   HIDCLASS HIDCLASS.SYS Tue Jul 14 12:06:21 2009 (4A5BCBFD)
fffff880`043f7000 fffff880`043ff080   HIDPARSE HIDPARSE.SYS Tue Jul 14 12:06:17 2009 (4A5BCBF9)
fffff880`041ef000 fffff880`041fd000   hidusb   hidusb.sys   Tue Jul 14 12:06:22 2009 (4A5BCBFE)
fffff880`05d02000 fffff880`05dca000   HTTP     HTTP.sys     Tue Jul 14 11:22:16 2009 (4A5BC1A8)
fffff880`01a12000 fffff880`01a1b000   hwpolicy hwpolicy.sys Tue Jul 14 11:19:22 2009 (4A5BC0FA)
fffff880`0435e000 fffff880`0437c000   i8042prt i8042prt.sys Tue Jul 14 11:19:57 2009 (4A5BC11D)
fffff880`04166000 fffff880`0417c000   intelppm intelppm.sys Tue Jul 14 11:19:25 2009 (4A5BC0FD)
fffff880`0437c000 fffff880`0438b000   kbdclass kbdclass.sys Tue Jul 14 11:19:50 2009 (4A5BC116)
fffff800`00bc5000 fffff800`00bcf000   kdcom    kdcom.dll    Tue Jul 14 13:31:07 2009 (4A5BDFDB)
fffff880`04296000 fffff880`042d9000   ks       ks.sys       Thu Mar 04 17:32:25 2010 (4B8F37D9)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Tue Jul 14 11:20:54 2009 (4A5BC156)
fffff880`01660000 fffff880`0168b000   ksecpkg  ksecpkg.sys  Fri Dec 11 19:03:32 2009 (4B21E0B4)
fffff880`047e2000 fffff880`047e7200   ksthunk  ksthunk.sys  Tue Jul 14 12:00:19 2009 (4A5BCA93)
fffff880`05cd5000 fffff880`05cea000   lltdio   lltdio.sys   Tue Jul 14 12:08:50 2009 (4A5BCC92)
fffff880`05c91000 fffff880`05cb4000   luafv    luafv.sys    Tue Jul 14 11:26:13 2009 (4A5BC295)
fffff880`00ce1000 fffff880`00d25000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 13:29:10 2009 (4A5BDF66)
fffff880`05c83000 fffff880`05c91000   monitor  monitor.sys  Tue Jul 14 11:38:52 2009 (4A5BC58C)
fffff880`04285000 fffff880`04294000   mouclass mouclass.sys Tue Jul 14 11:19:50 2009 (4A5BC116)
fffff880`02e1b000 fffff880`02e28000   mouhid   mouhid.sys   Tue Jul 14 12:00:20 2009 (4A5BCA94)
fffff880`00e8b000 fffff880`00ea5000   mountmgr mountmgr.sys Tue Jul 14 11:19:54 2009 (4A5BC11A)
fffff880`05de8000 fffff880`05e00000   mpsdrv   mpsdrv.sys   Tue Jul 14 12:08:25 2009 (4A5BCC79)
fffff880`05c00000 fffff880`05c2d000   mrxsmb   mrxsmb.sys   Sat Feb 27 20:52:19 2010 (4B88CF33)
fffff880`072a2000 fffff880`072f0000   mrxsmb10 mrxsmb10.sys Sat Feb 27 20:52:28 2010 (4B88CF3C)
fffff880`072f0000 fffff880`07313000   mrxsmb20 mrxsmb20.sys Sat Feb 27 20:52:26 2010 (4B88CF3A)
fffff880`014a0000 fffff880`014ab000   Msfs     Msfs.SYS     Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`00fd4000 fffff880`00fde000   msisadrv msisadrv.sys Tue Jul 14 11:19:26 2009 (4A5BC0FE)
fffff880`01060000 fffff880`010be000   msrpc    msrpc.sys    Tue Jul 14 11:21:32 2009 (4A5BC17C)
fffff880`040a7000 fffff880`040b2000   mssmbios mssmbios.sys Tue Jul 14 11:31:10 2009 (4A5BC3BE)
fffff880`01a00000 fffff880`01a12000   mup      mup.sys      Tue Jul 14 11:23:45 2009 (4A5BC201)
fffff880`00e81000 fffff880`00e8b000   mv91cons mv91cons.sys Wed Sep 23 09:36:37 2009 (4AB94365)
fffff880`0111b000 fffff880`011a7000   mv91xx   mv91xx.sys   Thu Jul 01 13:55:14 2010 (4C2BF582)
fffff880`011d6000 fffff880`011de000   mvxxmm   mvxxmm.sys   Thu Jul 01 13:54:57 2010 (4C2BF571)
fffff880`016eb000 fffff880`017dd000   ndis     ndis.sys     Tue Jul 14 11:21:40 2009 (4A5BC184)
fffff880`043eb000 fffff880`043f7000   ndistapi ndistapi.sys Tue Jul 14 12:10:00 2009 (4A5BCCD8)
fffff880`04200000 fffff880`0422f000   ndiswan  ndiswan.sys  Tue Jul 14 12:10:11 2009 (4A5BCCE3)
fffff880`04712000 fffff880`04727000   NDProxy  NDProxy.SYS  Tue Jul 14 12:10:05 2009 (4A5BCCDD)
fffff880`02f8c000 fffff880`02f9b000   netbios  netbios.sys  Tue Jul 14 12:09:26 2009 (4A5BCCB6)
fffff880`02e8e000 fffff880`02ed3000   netbt    netbt.sys    Tue Jul 14 11:21:28 2009 (4A5BC178)
fffff880`01600000 fffff880`01660000   NETIO    NETIO.SYS    Tue Jul 14 11:21:46 2009 (4A5BC18A)
fffff880`014ab000 fffff880`014bc000   Npfs     Npfs.SYS     Tue Jul 14 11:19:48 2009 (4A5BC114)
fffff880`0409b000 fffff880`040a7000   nsiproxy nsiproxy.sys Tue Jul 14 11:21:02 2009 (4A5BC15E)
fffff800`02a1b000 fffff800`02ff8000   nt       ntkrnlmp.exe Wed Oct 27 15:43:09 2010 (4CC791BD)
fffff880`01257000 fffff880`013fa000   Ntfs     Ntfs.sys     Tue Jul 14 11:20:47 2009 (4A5BC14F)
fffff880`01439000 fffff880`01442000   Null     Null.SYS     Tue Jul 14 11:19:37 2009 (4A5BC109)
fffff880`046fa000 fffff880`04712000   nusb3hub nusb3hub.sys Fri Apr 23 13:34:35 2010 (4BD0F92B)
fffff880`04000000 fffff880`04030000   nusb3xhc nusb3xhc.sys Fri Apr 23 13:34:36 2010 (4BD0F92C)
fffff880`10c83000 fffff880`10c84180   nvBridge nvBridge.kmd Sat Jan 08 14:57:22 2011 (4D27C482)
fffff880`10028000 fffff880`10c82d00   nvlddmkm nvlddmkm.sys Sat Jan 08 15:07:22 2011 (4D27C6DA)
fffff880`02f66000 fffff880`02f8c000   pacer    pacer.sys    Tue Jul 14 12:09:41 2009 (4A5BCCC5)
fffff880`00e40000 fffff880`00e55000   partmgr  partmgr.sys  Tue Jul 14 11:19:58 2009 (4A5BC11E)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Tue Jul 14 11:19:51 2009 (4A5BC117)
fffff880`00e6a000 fffff880`00e71000   pciide   pciide.sys   Tue Jul 14 11:19:49 2009 (4A5BC115)
fffff880`00e71000 fffff880`00e81000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 11:19:48 2009 (4A5BC114)
fffff880`01548000 fffff880`01559000   pcw      pcw.sys      Tue Jul 14 11:19:27 2009 (4A5BC0FF)
fffff880`07328000 fffff880`073ce000   peauth   peauth.sys   Tue Jul 14 13:01:19 2009 (4A5BD8DF)
fffff880`04783000 fffff880`047c0000   portcls  portcls.sys  Tue Jul 14 12:06:27 2009 (4A5BCC03)
fffff880`00d25000 fffff880`00d39000   PSHED    PSHED.dll    Tue Jul 14 13:32:23 2009 (4A5BE027)
fffff880`043c7000 fffff880`043eb000   rasl2tp  rasl2tp.sys  Tue Jul 14 12:10:11 2009 (4A5BCCE3)
fffff880`0422f000 fffff880`0424a000   raspppoe raspppoe.sys Tue Jul 14 12:10:17 2009 (4A5BCCE9)
fffff880`0424a000 fffff880`0426b000   raspptp  raspptp.sys  Tue Jul 14 12:10:18 2009 (4A5BCCEA)
fffff880`0426b000 fffff880`04285000   rassstp  rassstp.sys  Tue Jul 14 12:10:25 2009 (4A5BCCF1)
fffff880`0404a000 fffff880`0409b000   rdbss    rdbss.sys    Tue Jul 14 11:24:09 2009 (4A5BC219)
fffff880`01485000 fffff880`0148e000   RDPCDD   RDPCDD.sys   Tue Jul 14 12:16:34 2009 (4A5BCE62)
fffff880`0148e000 fffff880`01497000   rdpencdd rdpencdd.sys Tue Jul 14 12:16:34 2009 (4A5BCE62)
fffff880`01497000 fffff880`014a0000   rdprefmp rdprefmp.sys Tue Jul 14 12:16:35 2009 (4A5BCE63)
fffff880`01bbe000 fffff880`01bf8000   rdyboost rdyboost.sys Tue Jul 14 11:34:34 2009 (4A5BC48A)
fffff880`05cea000 fffff880`05d02000   rspndr   rspndr.sys   Tue Jul 14 12:08:50 2009 (4A5BCC92)
fffff880`042fc000 fffff880`04352000   Rt64win7 Rt64win7.sys Wed Jun 23 21:10:45 2010 (4C21CF95)
fffff880`07905000 fffff880`0790b000   RTCore64 RTCore64.sys Wed May 25 18:39:12 2005 (42941D90)
fffff880`011a7000 fffff880`011d6000   SCSIPORT SCSIPORT.SYS Tue Jul 14 12:01:04 2009 (4A5BCAC0)
fffff880`073ce000 fffff880`073d9000   secdrv   secdrv.SYS   Thu Sep 14 01:18:38 2006 (4508052E)
fffff880`04352000 fffff880`0435e000   serenum  serenum.sys  Tue Jul 14 12:00:33 2009 (4A5BCAA1)
fffff880`02f9b000 fffff880`02fb8000   serial   serial.sys   Tue Jul 14 12:00:40 2009 (4A5BCAA8)
fffff880`01b78000 fffff880`01bbe000   snapman  snapman.sys  Wed Apr 28 00:17:12 2010 (4BD6D5C8)
fffff880`01b70000 fffff880`01b78000   spldr    spldr.sys    Tue May 12 04:56:27 2009 (4A0858BB)
fffff880`0786f000 fffff880`07905000   srv      srv.sys      Fri Aug 27 15:38:00 2010 (4C773318)
fffff880`07808000 fffff880`0786f000   srv2     srv2.sys     Fri Aug 27 15:37:46 2010 (4C77330A)
fffff880`07200000 fffff880`0722d000   srvnet   srvnet.sys   Fri Aug 27 15:37:24 2010 (4C7732F4)
fffff880`04294000 fffff880`04295480   swenum   swenum.sys   Tue Jul 14 12:00:18 2009 (4A5BCA92)
fffff880`04600000 fffff880`0469f000   t3       t3.sys       Thu Jun 04 07:13:51 2009 (4A26CB6F)
fffff880`01802000 fffff880`019ff000   tcpip    tcpip.sys    Mon Jun 14 15:39:04 2010 (4C15A458)
fffff880`0722d000 fffff880`0723f000   tcpipreg tcpipreg.sys Tue Jul 14 12:09:49 2009 (4A5BCCCD)
fffff880`014bc000 fffff880`014c9000   TDI      TDI.SYS      Tue Jul 14 11:21:18 2009 (4A5BC16E)
fffff880`015e0000 fffff880`015fe000   tdx      tdx.sys      Tue Jul 14 11:21:15 2009 (4A5BC16B)
fffff880`02fd3000 fffff880`02fe7000   termdd   termdd.sys   Tue Jul 14 12:16:36 2009 (4A5BCE64)
fffff880`01a37000 fffff880`01b24000   timntr   timntr.sys   Thu Dec 17 07:04:06 2009 (4B292116)
fffff960`004e0000 fffff960`004ea000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`04140000 fffff880`04166000   tunnel   tunnel.sys   Tue Jul 14 12:09:37 2009 (4A5BCCC1)
fffff880`042d9000 fffff880`042eb000   umbus    umbus.sys    Tue Jul 14 12:06:56 2009 (4A5BCC20)
fffff880`07987000 fffff880`07998000   usbaapl64 usbaapl64.sys Fri Sep 17 14:19:05 2010 (4C92D019)
fffff880`02e00000 fffff880`02e1ac00   usbaudio usbaudio.sys Tue Jul 14 12:06:31 2009 (4A5BCC07)
fffff880`041d2000 fffff880`041ef000   usbccgp  usbccgp.sys  Tue Jul 14 12:06:45 2009 (4A5BCC15)
fffff880`10df4000 fffff880`10df5f00   USBD     USBD.SYS     Tue Jul 14 12:06:23 2009 (4A5BCBFF)
fffff880`10dbf000 fffff880`10dd0000   usbehci  usbehci.sys  Tue Jul 14 12:06:30 2009 (4A5BCC06)
fffff880`046a0000 fffff880`046fa000   usbhub   usbhub.sys   Tue Jul 14 12:07:09 2009 (4A5BCC2D)
fffff880`0417c000 fffff880`041d2000   USBPORT  USBPORT.SYS  Tue Jul 14 12:06:31 2009 (4A5BCC07)
fffff880`042eb000 fffff880`042f7000   usbprint usbprint.sys Tue Jul 14 12:38:18 2009 (4A5BD37A)
fffff880`047e8000 fffff880`047f9000   usbscan  usbscan.sys  Tue Jul 14 12:35:32 2009 (4A5BD2D4)
fffff880`0121a000 fffff880`01235000   USBSTOR  USBSTOR.SYS  Tue Jul 14 12:06:34 2009 (4A5BCC0A)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Tue Jul 14 12:01:31 2009 (4A5BCADB)
fffff880`01442000 fffff880`01450000   vga      vga.sys      Tue Jul 14 11:38:47 2009 (4A5BC587)
fffff880`01450000 fffff880`01475000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 11:38:51 2009 (4A5BC58B)
fffff880`00e55000 fffff880`00e6a000   volmgr   volmgr.sys   Tue Jul 14 11:19:57 2009 (4A5BC11D)
fffff880`00d97000 fffff880`00df3000   volmgrx  volmgrx.sys  Tue Jul 14 11:20:33 2009 (4A5BC141)
fffff880`01b24000 fffff880`01b70000   volsnap  volsnap.sys  Tue Jul 14 11:20:08 2009 (4A5BC128)
fffff880`02fb8000 fffff880`02fd3000   wanarp   wanarp.sys   Tue Jul 14 12:10:21 2009 (4A5BCCED)
fffff880`01475000 fffff880`01485000   watchdog watchdog.sys Tue Jul 14 11:37:35 2009 (4A5BC53F)
fffff880`00ec1000 fffff880`00f65000   Wdf01000 Wdf01000.sys Tue Jul 14 11:22:07 2009 (4A5BC19F)
fffff880`00f65000 fffff880`00f74000   WDFLDR   WDFLDR.SYS   Tue Jul 14 11:19:54 2009 (4A5BC11A)
fffff880`02f5d000 fffff880`02f66000   wfplwf   wfplwf.sys   Tue Jul 14 12:09:26 2009 (4A5BCCB6)
fffff960`00030000 fffff960`00340000   win32k   win32k.sys   unavailable (00000000)
fffff880`04398000 fffff880`043a1000   wmiacpi  wmiacpi.sys  Tue Jul 14 11:31:02 2009 (4A5BC3B6)
fffff880`00fcb000 fffff880`00fd4000   WMILIB   WMILIB.SYS   Tue Jul 14 11:19:51 2009 (4A5BC117)
fffff880`05cb4000 fffff880`05cd5000   WudfPf   WudfPf.sys   Tue Jul 14 12:05:37 2009 (4A5BCBD1)
Unloaded modules:
fffff880`0790b000 fffff880`0797c000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`017dd000 fffff880`017eb000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`017eb000 fffff880`017f7000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`017f7000 fffff880`01800000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`015cd000 fffff880`015e0000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000

 

[zigzag3143]

Latest and greatest BSOD action...

While this minidump has incorrect symbols (where did you download it from? did you install SP1?) we can still give you some generic things to narrow the focus.

You also have driver from as far back as 2005 that need updating and they could be the cause.

It is blaming a memory exception on an un named driver. I would:

1- Run memtest to verify your memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.



2-Run driver verifier to find the errant driver . WARNING BEFORE RUNNING VERIFIER MAKE SURE YOU HAVE A COMPLETE BACKUP AND RESTORE POINT.




Beyond that, please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

Let us know if you require further assistance with this



Ken J

 

[dleslie]

Thanks very much for the help. I'll get to work on this and post my results.

Dave

 

[dleslie]

Hi,

I have uninstalled AVG, using the uninstaller that was linked. I went with MSE instead. I ran memtest 86+ before posting here for three full passes, so I'm going to assume that things are alright in the memory department.

I set up the driver verifier according to the instructions in the post and, sure enough, the MSI afterburner driver caused a crash on the first reboot. I managed to get into windows normally after another crash with no driver info attached to it. I uninstalled Afterburner and then restarted and so far so good.

Will this driver verifier continue to run after every restart until I turn it off?

Thanks for the help again!!!!

Dave

 

[DeanP]

Hello Dave,

Run at least 7 passes for Memtest (you won't find any errors occurring around 3 or 4 passes).

As said, uninstall MSI Afterburner - because it is using an old driver, causing issues on some Windows 7 system and Driver Verifier is blaming it.

What to do when Driver Verifier is on?

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

 

[dleslie]

Hi,

After rebooting a crash occurred before Windows could boot up. Here is the dump file.

Thanks again!

Dave

 

[dleslie]

I should have mentioned that verifier was running at the time of the crash, but, there was no indication of a specific driver at fault at the blue screen.

Dave

 

[DeanP]

   Warning

Before you do anything - turn off Driver Verifier. (type in verifier.exe in Start Search Box and select Delete existing settings)

Dump blames the driver of your Zotac Graphics card, please do the following...

- Boot into safe mode with networking
- Uninstall the Display drivers
- Use driver sweeper to remove leftover ATI display driver files Guru3D - Driver Sweeper (This step is important)
- Reboot into safe mode with networking
- Install the latest drivers ZOTAC - It's time to play! - Downloads | Windows 7 and Vista 64-bit | Graphics Card Drivers
- Reboot into normal mode

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002a69634, fffff880033bc5b8, fffff880033bbe20}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+92ad0 )

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

 

[dleslie]

Hi,

Seven passes of memtest with no errors. The video drivers have been cleared and reinstalled in safe mode. Fingers crossed.

Thanks for the help,

Dave

 

[dleslie]

Hi,

After taking the above measures, I got another crash during startup while using driver verifier.

Here's the file. Thanks again!

Dave

 

[dleslie]

Hi,

Things seemed to be running smoothly for a while, until I was playing Starcraft 2 today. I got two bluescreens within 20 minute of each other. I have followed the advise given to me by the generous gentlemen who have responded to the thread. But, here I am, back again.

If anyone could take some time to peek at these dumps and see what could be causing my problems I would appreciate it. Thanks.

Dave

 

[DeanP]

[warn2]Turn off Driver Verifier. Go to verifier.exe and select "Delete existing settings"[/warn2]

Dump blames hardware. See this thread: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

If you are overclocking anything. Stop and return to default values, please.

Regards...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80087cc028, be000000, 800400}

Probably caused by : hardware

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80087cc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`02ff5903 : 00000000`00000124 00000000`00000000 fffffa80`087cc028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02b8c5a3 : 00000000`00000001 fffffa80`08016470 00000000`00000000 fffffa80`080164c0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`02ff55c8 : 00000000`00000728 fffffa80`08016470 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`02ff4f1a : fffffa80`08016470 fffff800`00ba8e70 fffffa80`08016470 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`02ff4dd5 : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`02fe8e88 : fffff800`02bf0e80 fffff800`02bf0e80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02a74fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02a74e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff800`02a83dbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9cca0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PoIdle+0xab


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80087cc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`02ff5903 : 00000000`00000124 00000000`00000000 fffffa80`087cc028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02b8c5a3 : 00000000`00000001 fffffa80`08016470 00000000`00000000 fffffa80`080164c0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`02ff55c8 : 00000000`00000728 fffffa80`08016470 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`02ff4f1a : fffffa80`08016470 fffff800`00ba8e70 fffffa80`08016470 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`02ff4dd5 : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`02fe8e88 : fffff800`02bf0e80 fffff800`02bf0e80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02a74fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02a74e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff800`02a83dbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9cca0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PoIdle+0xab


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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