Intermittent BSOD, no common activity.

**GoinDH** · 08-14-2012

Hardlock is gone, Installed latest windows update, then IRQL BSOD during idle around 20 min later, seems ndisuio.sys is the culprit according to BlueScreenView. With so many random BSOD could it be hardware? Would you recommend a fresh install? Not exactly what i want to do but it is what it is. I can pack up the latest dump if you would like.

Thanks again.

**usasma** · 08-15-2012

Please zip up and upload the latest memory dumps (they're located in C:\Windows\Minidump)
Then run Driver Verifier according to these instructions: Driver Verifier Settings

We'll see what those results are and then will move on from there.

When first released, BlueScreenView wasn't very helpful with BSOD's in 64 bit systems.
I haven't done any research on this in the recent past, so I'm unsure if this is still the case or not.
It does point to networking stuff - so we should focus our troubleshooting efforts there.

**GoinDH** · 08-15-2012

Will run driver verifier tonight but here is the latest dumps.

**usasma** · 08-15-2012

Hardlock.sys is still present. Please do the following:
- Set a System Restore point
- Create a System Repair Disc (Start...All Programs...Maintenance...Create a System Repair Disc)
- Download and install Autoruns (free from here: http://technet.microsoft.com/en-us/s.../bb963902.aspx )
- Search Autorun's entries for anything with hardlock.sys - disable it by removing the checkmark in the far left column
- Rename hardlock.sys to hardlock.BAK (located at C:\Windows\system32\drivers\hardlock.sys)
- Reboot the system
NOTE: Should the system fail to boot, use the System Repair Disc to rename hardlock.BAK to hardlock.sys (from the Command Prompt), then use System Restore to reset the system to the previously made System Restore point.

Should the BSOD's continue to happen after the hardlock.sys is successfully removed, then we have to suspect a hardware issue. Please run these free diagnostics in that case: http://www.carrona.org/hwdiag.html

Analysis:

The following is for information purposes only.

Code:

**************************Wed Aug 15 15:11:26.803 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081512-49187-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:05:29.301
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck Code: BugCheck 116, {fffffa800d8f4010, fffff88003f7e250, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by :atikmpag.sys ( atikmpag+9250 )
BugCheck Info: VIDEO_TDR_FAILURE (116)
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug 14 20:32:43.517 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081412-58874-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:04:22.000
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: BugCheck D1, {ffffffffffffff6b, 2, 1, fffff8800267bf6a}
*** WARNING: Unable to verify timestamp for ndisuio.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisuio.sys
Probably caused by :ndisuio.sys ( ndisuio+4f6a )
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug 14 15:11:21.891 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081412-49639-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:05:06.000
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: BugCheck D1, {fffffe32, 2, 1, fffff88002635f6a}
Probably caused by :ntoskrnl.exe ( nt+7f1c0 )
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug 14 01:37:58.503 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081312-49218-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:12:14.612
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: BugCheck D1, {7c, 2, 0, fffff880040f0463}
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
Probably caused by :USBPORT.SYS ( USBPORT+14463 )
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug 14 01:24:33.516 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081312-44678-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:01:38.014
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: BugCheck FC, {fffff88002497f6a, 80000003fadd9963, fffff80004c500d0, 0}
Probably caused by :ntoskrnl.exe ( nt+7f1c0 )
BugCheck Info: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFC
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:

The following is for information purposes only.

Code:

**************************Wed Aug 15 15:11:26.803 2012 (UTC - 4:00)**************************
hardlock.sys      Thu Nov 30 12:12:07 2006 (456F10E7)
AtiPcie.sys       Tue May  5 11:00:22 2009 (4A005486)
ASACPI.sys        Wed Jul 15 23:31:29 2009 (4A5E9F11)
EIO64.sys         Tue Jul 21 22:34:42 2009 (4A667AC2)
AsIO.sys          Mon Aug  3 03:03:16 2009 (4A768BB4)
PxHlpa64.sys      Tue Oct 20 14:08:42 2009 (4ADDFCAA)
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
cpuz134_x64.sys   Fri Jul  9 07:16:58 2010 (4C37052A)
speedfan.sys      Sat Dec 18 06:03:51 2010 (4D0C9517)
point64.sys       Fri Apr  8 18:58:14 2011 (4D9F9306)
Rt64win7.sys      Fri Jun 10 02:33:15 2011 (4DF1BAAB)
AtihdW76.sys      Tue Dec  6 04:14:25 2011 (4EDDDCF1)
MpFilter.sys      Fri Mar  9 06:05:26 2012 (4F59E3F6)
dc3d.sys          Sun May 27 10:20:12 2012 (4FC2381C)
atikmpag.sys      Mon Jun 11 12:26:14 2012 (4FD61C26)
atikmdag.sys      Mon Jun 11 12:59:31 2012 (4FD623F3)
RTKVHD64.sys      Tue Jun 19 04:50:56 2012 (4FE03D70)

**GoinDH** · 08-15-2012

I think i have got rid of Hardlock, will check for hardware faults next. 4 BSOD just in the past few hours,

. Thank you so much again for your help.

**usasma** · 08-16-2012

Of all the BSOD's, only the last one didn't have hardlock.sys
Please run these free diagnostics: Hardware Diagnostics
I suspect a video problem, but please complete all the tests and let us know the results

Some additional suggestions for troubleshooting video issues: http://www.sevenforums.com/crash-loc...eshooting.html

I was reviewing the thread and have 2 other concerns:

- Ensure that Driver Verifier is turned off. To do this, please open up Driver Verifier and select "Delete existing settings". Then click on "Finish" and reboot the system for the changes to take effect.

- You stated this in post #7: "I changed all my Mobo factory settings to default,..."
Asus M4 series mobo's may have some memory issues when set a default. Please consult OCZ for the recommended settings on your RAM, then enter those settings into the BIOS (in other words - DO NOT use the default memory settings on your motherboard).

Analysis:

The following is for information purposes only.

Code:

**************************Wed Aug 15 21:01:13.502 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081512-46753-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:10:19.000
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: BugCheck D1, {57ff1587258, 2, 0, fffff880029e1f6a}
Probably caused by :ntoskrnl.exe ( nt+7f1c0 )
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug 15 20:09:13.716 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081512-54834-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:03:33.840
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck Code: BugCheck 116, {fffffa800fc894e0, fffff88003f38250, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by :atikmpag.sys ( atikmpag+9250 )
BugCheck Info: VIDEO_TDR_FAILURE (116)
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug 15 19:50:44.502 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081512-52041-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:06:59.000
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: BugCheck D1, {fffff880025daf6a, 2, 8, fffff880025daf6a}
Probably caused by :ntoskrnl.exe ( nt+7f1c0 )
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:

The following is for information purposes only. Any drivers in red should be updated.

Code:

**************************Wed Aug 15 21:01:13.502 2012 (UTC - 4:00)**************************
AtiPcie.sys       Tue May  5 11:00:22 2009 (4A005486)
ASACPI.sys        Wed Jul 15 23:31:29 2009 (4A5E9F11)
EIO64.sys         Tue Jul 21 22:34:42 2009 (4A667AC2)
AsIO.sys          Mon Aug  3 03:03:16 2009 (4A768BB4)
PxHlpa64.sys      Tue Oct 20 14:08:42 2009 (4ADDFCAA)
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
cpuz134_x64.sys   Fri Jul  9 07:16:58 2010 (4C37052A)
speedfan.sys      Sat Dec 18 06:03:51 2010 (4D0C9517)
point64.sys       Fri Apr  8 18:58:14 2011 (4D9F9306)
Rt64win7.sys      Fri Jun 10 02:33:15 2011 (4DF1BAAB)
AtihdW76.sys      Tue Dec  6 04:14:25 2011 (4EDDDCF1)
MpFilter.sys      Fri Mar  9 06:05:26 2012 (4F59E3F6)
dc3d.sys          Sun May 27 10:20:12 2012 (4FC2381C)
atikmpag.sys      Mon Jun 11 12:26:14 2012 (4FD61C26)
atikmdag.sys      Mon Jun 11 12:59:31 2012 (4FD623F3)
RTKVHD64.sys      Tue Jun 19 04:50:56 2012 (4FE03D70)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Aug 15 20:09:13.716 2012 (UTC - 4:00)**************************
hardlock.sys      Thu Nov 30 12:12:07 2006 (456F10E7)

**GoinDH** · 08-16-2012

I turned Driver Verifier off after having to boot to safe mode to delete all settings in Verifier.

You are correct, hardlock was still there during 3 of that string of 4 BSOD because i was in the middle of reserching and trying differnt things to get rid of it.

At this point my current plan of action will be to reset my Motherboard back to what my RAM manufacturer recommends, run Driver Verifier again, then begin trouble shooting my video with the link you provided, will update as soon as i can.

**usasma** · 08-16-2012

Sounds like a good plan, I'll wait to hear back from you.
I get email notification when you reply :0)

**GoinDH** · 08-21-2012

Finally got some time to do some trouble shooting.

First i returned all the motherboard RAM settings to what my RAM manufacturer suggested. Then i started testing my video card and hard drive with the hardware test links you provided. Both hard drives passed the quick test, did not do a full test on either drive. Ran FurMark till both my GPUs hit peak temp of 59*C, this took a bit of trail and error to get both of the GPUs to work in FurMark. I have the MSI 5770 Hawk and i had to rename the Furmark.exe to SeriousSam.exe to utilize both GPUs during the burn in test.

Anyways now the part i find interesting. After testing the hard drives and GPUs i put my computer back into Driver Verifier mode and it has not had a BSOD since. I do have to admit having the computer in driver verifier mode makes gaming performance complete ****, but it is a stable system doing everything else. I did recently installed MSI afterburner software to help monitor GPU settings, found it to be better than GPU-Z. I believe i did this right before or after turning on Driver Verifier, so i dont know if it will show up in the BSOD i am uploading. I will also upload a drivers list to see if anything else stands out to you.

Again i cant thank you enough for spending your time helping me and other Windows users with our systems, you are a godsend for the moderately knowledgeable consumers we are.

*Edit: Might be useful information the computer has only been running in verifier mode for a total of around 8hrs. I will continue to run the computer in verifier mode for a total of 36hr as recommended on your website.

**usasma** · 08-21-2012

Run the long test on the hard drive(s) when you get time. I've seen the short test pass while the long test fails on many occasions at work.

MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's in some Win7 systems. Un-install it and leave it off while we're testing. Although yours is a newer version than the version that we commonly see causing BSOD's - it's still been seen to be involved in a few BSOD's.

The 36 hour estimate for Driver Verifier is just a guess on my part - I made it to ensure that you catch any recurring tasks that may occur on the system. It's not a hard and fast rule.

Verifier will slow down your system's performance as it's performing additional operations that stress the drivers (and, hopefully, cause them to crash and name the faulting driver).

It's looking more and more like a hardware error to me
Un-install all the Asus utilities (with the exception of the Asus ATK0110 ACPI utility) to see if that helps.

Lot's of cdrom.sys errors in the BSOD's. Try disconnecting your CD/DVD drive(s) and see if that helps. Disconnect both the power and the data cables.

Continue with the hardware testing - especially any stress tests (such as Prime95 and the OCCT tests) and the CPU stress tests.

Analysis:

The following is for information purposes only.

Code:

**************************Mon Aug 20 01:43:43.363 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081912-47954-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:11:35.862
BugCheck Code: BugCheck 50, {fffff9801129a400, 0, fffff800039da2d7, 0}
Probably caused by :ntkrnlmp.exe ( nt!CcMapData+117 )
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: itype.exe
FAILURE_BUCKET_ID: X64_0x50_nt!CcMapData+117
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 19 23:46:54.521 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081912-48953-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:00:56.004
BugCheck Code: BugCheck D1, {fffff880025bef6a, 2, 8, fffff880025bef6a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_cdrom!DeviceEvtIoInCallerContext+1ad
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 19 23:42:14.517 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081912-46098-01.dmp]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081912-54849-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:04:43.000
BugCheck Code: BugCheck D1, {fffff880025a4f6a, 2, 8, fffff880025a4f6a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_cdrom!DeviceEvtIoInCallerContext+1ad
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 19 23:36:09.609 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081912-49530-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:24:51.733
BugCheck Code: BugCheck D1, {4f444622, 2, 1, fffff8800425c58b}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xD1
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 19 23:09:56.502 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081912-51012-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:03:39.000
BugCheck Code: BugCheck FC, {fffff880025bdf6a, 80000003f3db5963, fffff80004c470d0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
BugCheck Info: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xFC_cdrom!DeviceEvtIoInCallerContext+1ad
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 18 15:31:30.892 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081812-47829-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:40:33.000
BugCheck Code: BugCheck D1, {fffffe32, 2, 1, fffff8800260dfa5}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xD1_cdrom!DeviceEvtIoInCallerContext+1ad
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug 17 15:07:29.513 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081712-30841-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:01:01.011
BugCheck Code: BugCheck FC, {fffff8800219cf6a, 80000003f7961963, fffff80004c550d0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+1ad )
BugCheck Info: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xFC_cdrom!DeviceEvtIoInCallerContext+1ad
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Aug 16 22:50:37.968 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081612-33212-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:36:16.467
BugCheck Code: BugCheck A, {ffffffffffffffff, 2, 1, fffff80003697160}
Probably caused by :ntkrnlmp.exe ( nt!KeSignalGateBoostPriority+60 )
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME: Rainmeter.exe
FAILURE_BUCKET_ID: X64_0xA_nt!KeSignalGateBoostPriority+60
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Aug 16 22:12:50.501 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081612-46457-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:35:23.000
BugCheck Code: BugCheck D1, {fffffe32, 2, 1, fffff88002629f6a}
*** WARNING: Unable to verify timestamp for cpuz134_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpuz134_x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :cpuz134_x64.sys ( cpuz134_x64+3f6a )
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xD1_cpuz134_x64+3f6a
  BIOS Version                  3503   
  BIOS Release Date             05/06/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:

The following is for information purposes only. Any drivers in red should be updated.

Code:

**************************Mon Aug 20 01:43:43.363 2012 (UTC - 4:00)**************************
AtiPcie.sys                 Tue May  5 11:00:22 2009 (4A005486)
ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)
EIO64.sys                   Tue Jul 21 22:34:42 2009 (4A667AC2)
AsIO.sys                    Mon Aug  3 03:03:16 2009 (4A768BB4)
PxHlpa64.sys                Tue Oct 20 14:08:42 2009 (4ADDFCAA)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
cpuz134_x64.sys             Fri Jul  9 07:16:58 2010 (4C37052A)
speedfan.sys                Sat Dec 18 06:03:51 2010 (4D0C9517)
point64.sys                 Fri Apr  8 18:58:14 2011 (4D9F9306)
Rt64win7.sys                Fri Jun 10 02:33:15 2011 (4DF1BAAB)
RTCore64.sys                Tue Sep  6 08:24:50 2011 (4E661112)
AtihdW76.sys                Tue Dec  6 04:14:25 2011 (4EDDDCF1)
MpFilter.sys                Fri Mar  9 06:05:26 2012 (4F59E3F6)
dc3d.sys                    Sun May 27 10:20:12 2012 (4FC2381C)
atikmpag.sys                Mon Jun 11 12:26:14 2012 (4FD61C26)
atikmdag.sys                Mon Jun 11 12:59:31 2012 (4FD623F3)
RTKVHD64.sys                Tue Jun 19 04:50:56 2012 (4FE03D70)

Intermittent BSOD, no common activity.

LinkBack

Thread Tools

Search Thread

Re: Intermittent BSOD, no common activity.

Re: Intermittent BSOD, no common activity.

Re: Intermittent BSOD, no common activity.

Re: Intermittent BSOD, no common activity.

Re: Intermittent BSOD, no common activity.

Re: Intermittent BSOD, no common activity.

Re: Intermittent BSOD, no common activity.

Re: Intermittent BSOD, no common activity.

Re: Intermittent BSOD, no common activity.

Re: Intermittent BSOD, no common activity.

Similar Threads

Intermittent BSOD

BSOD, Common Occurrence

Intermittent BSOD

[BSOD] Intermittent BSOD's

Intermittent BSOD 0x8000000002

Visitors found this page by searching for:

Virtual Usb Bus Enumerator windows 7

Tags for this Thread

Posting Permissions