Computer will just blue screen randomly. Only programs I've been using are firefox, itunes, and trillian
BSOD Windows 7 64 bit
I'm running Windows 7, 64 bit.
Recently just built the computer from parts. OS installation less than a week. Haven't tried reinstalling the OS.
Video Card: ATI Radeon HD 4200
MotherBoard: ASUS M4A785TD-V EVO
Power Supply: Apevia ATX-CW500WP4 500W ATX Power Supply
Using an AMD Phenom II processor.
Recently just built the computer from parts. OS installation less than a week. Haven't tried reinstalling the OS.
Video Card: ATI Radeon HD 4200
MotherBoard: ASUS M4A785TD-V EVO
Power Supply: Apevia ATX-CW500WP4 500W ATX Power Supply
Using an AMD Phenom II processor.
Attachments
-
639.5 KB Views: 43
- Status
- Not open for further replies.
1 - 15 of 15 Posts
No blue screen info in the attached files (but 3 are listed in the MSINFO32 report), please do the following:
Also, as the 3 listed dump files don't have much information with them, please run Driver Verifier according to these directions:Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.
If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.
If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service . I recommend Windows Live SkyDrive - http://skydrive.live.com or another free, file-hosting service. Then post the link to it in your topic so that we can download it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): http://www.carrona.org/setmini.html
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:
More info on this at this link: http://support.microsoft.com/?kbid=244617&sd=RMVPCode: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
here are my minidump files. I'm in the process of using the driver verifier but the computer hasn't blue screened yet
Attachments
-
544.5 KB Views: 40
22 memory dump files, from 29 May to 05 Jul 2010
5 different STOP error codes, blaming 5 different causes.
Still nothing firm from the memory dump files - I'd suggest waiting until you get some results from the Driver Verifier.
BSOD BUGCHECK SUMMARY
5 different STOP error codes, blaming 5 different causes.
Still nothing firm from the memory dump files - I'd suggest waiting until you get some results from the Driver Verifier.
BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 5 15:46:16.798 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:55.093
BugCheck 3B, {c0000005, fffff80002db30bf, fffff88008324da0, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 5 06:01:24.214 2010 (UTC - 4:00)
System Uptime: 0 days 2:47:53.884
BugCheck 3B, {c0000005, fffff80002e02f8c, fffff880083ceda0, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 5 03:12:19.615 2010 (UTC - 4:00)
System Uptime: 0 days 0:51:15.285
BugCheck 3B, {c0000005, fffff80002cc6805, fffff88003b7fc10, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: lsass.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul 4 17:18:56.495 2010 (UTC - 4:00)
System Uptime: 0 days 0:19:54.790
BugCheck 3B, {c0000005, fffff9600006945b, fffff880086a6e20, 0}
Probably caused by : win32k.sys ( win32k!MultiUserGreTrackRemoveEngResource+2b )
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 02:30:14.715 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:27.010
BugCheck 3B, {c0000005, fffff80002f8f41b, fffff88006560070, 0}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpReceiveMessagePort+27b )
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 02:14:12.152 2010 (UTC - 4:00)
System Uptime: 0 days 1:40:47.463
BugCheck 3B, {c0000005, fffff80002f7b41b, fffff880029e1070, 0}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpReceiveMessagePort+27b )
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 00:32:07.164 2010 (UTC - 4:00)
System Uptime: 0 days 0:57:11.834
BugCheck 3B, {c0000005, fffff80002c81805, fffff880082923b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: TrustedInstall
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 15 02:01:41.104 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:51.415
BugCheck 1000007E, {ffffffffc0000005, fffff80002f82726, fffff880031af968, fffff880031af1d0}
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
PROCESS_NAME: System
BUGCHECK_STR: 0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 15 01:58:01.268 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:47.938
BugCheck 3B, {c0000005, fffff80002c81497, fffff88008413060, 0}
Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+47 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 15:59:50.870 2010 (UTC - 4:00)
System Uptime: 0 days 0:09:16.165
BugCheck 3B, {c0000005, fffff9600010945b, fffff8800910fd00, 0}
Probably caused by : win32k.sys ( win32k!MultiUserGreTrackRemoveEngResource+2b )
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 15:49:47.977 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:39.647
BugCheck 24, {1904fb, fffff88002f858d8, fffff88002f85140, fffff880010f272f}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+26f )
PROCESS_NAME: System
BUGCHECK_STR: 0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 15:45:57.433 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:08.103
BugCheck 19, {3, fffffa8003661b00, fffffa8003661b00, 7ffffa8003661b00}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
BUGCHECK_STR: 0x19_3
PROCESS_NAME: svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 15:41:02.872 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:50.168
BugCheck 24, {1904fb, fffff880085160d8, fffff88008515940, fffff80002df4f8c}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
PROCESS_NAME: svchost.exe
BUGCHECK_STR: 0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 15:35:02.348 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:23.018
BugCheck 24, {1904fb, fffff88002f85728, fffff88002f84f90, fffff880012c10df}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+2ef )
PROCESS_NAME: System
BUGCHECK_STR: 0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 08:55:33.636 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:40.947
BugCheck 24, {1904fb, fffff88002f858d8, fffff88002f85140, fffff880010ba6a7}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+1e7 )
PROCESS_NAME: System
BUGCHECK_STR: 0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 12 08:48:02.791 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:10.461
BugCheck 3B, {c0000005, fffff80002f9c42e, fffff88006c25170, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3e )
BUGCHECK_STR: 0x3B
PROCESS_NAME: mscorsvw.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 19:59:22.020 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:35.721
BugCheck 1A, {41284, fffff6fb7da00001, 7, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR: 0x1a_41284
PROCESS_NAME: WMIC.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 19:42:48.205 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:04.875
BugCheck 24, {1904fb, fffff880082f75b8, fffff880082f6e20, fffff88001308daf}
Probably caused by : Ntfs.sys ( Ntfs!TxfAccessCheck+9f )
PROCESS_NAME: firefox.exe
BUGCHECK_STR: 0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 14:45:10.740 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:02.441
BugCheck 1000007E, {ffffffffc0000005, fffff80002fc157e, fffff880031bda48, fffff880031bd2b0}
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKCBWorker+d6 )
PROCESS_NAME: System
BUGCHECK_STR: 0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 14:29:22.765 2010 (UTC - 4:00)
System Uptime: 0 days 0:41:51.435
BugCheck 3B, {c0000005, fffff80002dc1000, fffff880065d6ef0, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+174 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: lsass.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun May 30 01:55:51.924 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:42.204
BugCheck 3B, {c0000005, fffff80002e0af8c, fffff88004431d90, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: trillian.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun May 30 01:36:32.803 2010 (UTC - 4:00)
System Uptime: 0 days 1:25:21.473
BugCheck 3B, {c0000005, fffff9600006bcb6, fffff880023bd990, 0}
Probably caused by : win32k.sys ( win32k+5bcb6 )
BUGCHECK_STR: 0x3B
PROCESS_NAME: iTunes.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]24 plus hours and still no blue screen yet.
Just let it run until you get one - if you do not get one within a week turn DV off and consider your problem solved.24 plus hours and still no blue screen yet.
hmm yea i've had the DV on the entire time and theres been no blue screen. doesn't give me the assurance that the problem is solved though but it will do for now. thanks guys
Ok. Post back if you get any more BSODs
Driver Verifier is a program that stresses drivers in order to force them into crashing - if there's a problem with them. No problem = no crash.
But, that's why we have to carefully select the 3rd party drivers and the tests to run on them. If you haven't tried "Low Resource Simulation" - try that. Then, try selecting only the Microsoft drivers (and none of the 3rd party drivers) to see if that will generate BSOD's.
Your last 2 errors were from Pool Corruption - so we'd need to turn that driver test on in Driver Verifier (which was done in the instructions). The others were memory access errors - and those can be several different things in the driver tests menu.
But the point here is that the results of the testing are starting to point at hardware problems. As such, I'd suggest running these free diagnostic/stress tests:
But, that's why we have to carefully select the 3rd party drivers and the tests to run on them. If you haven't tried "Low Resource Simulation" - try that. Then, try selecting only the Microsoft drivers (and none of the 3rd party drivers) to see if that will generate BSOD's.
Your last 2 errors were from Pool Corruption - so we'd need to turn that driver test on in Driver Verifier (which was done in the instructions). The others were memory access errors - and those can be several different things in the driver tests menu.
But the point here is that the results of the testing are starting to point at hardware problems. As such, I'd suggest running these free diagnostic/stress tests:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
http://www.carrona.org/memdiag.html (read the details at the link)
http://www.carrona.org/hddiag.html (read the details at the link)
Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: http://www.carrona.org/malware.html (read the details at the link)
Then, if the above tests pass, I'd try these free stress tests:
FurMark download site: http://www.ozone3d.net/benchmarks/fur/
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exitPrime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
okay so couple week laters. i get a blue screen again. I ran the driver verifier and it crashed. Where would i be able to find the mindmp files from the crash?
just kidding im retarded and didn't read. here are my minidump files and the BSOD info
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: c1
BCP1: FFFFF9801FF96EE0
BCP2: FFFFF9801FF96EC7
BCP3: 0000000000E70118
BCP4: 0000000000000032
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\071710-15818-01.dmp
C:\Users\Rich\AppData\Local\Temp\WER-26442-0.sysdata.xml
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: c1
BCP1: FFFFF9801FF96EE0
BCP2: FFFFF9801FF96EC7
BCP3: 0000000000E70118
BCP4: 0000000000000032
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\071710-15818-01.dmp
C:\Users\Rich\AppData\Local\Temp\WER-26442-0.sysdata.xml
Attachments
-
58.8 KB Views: 34
The Driver Verifier cites memory corruption as the cause of the error (a STOP 0xC1 error). More info on the error here: http://www.carrona.org/bsodindx.html#0x000000C1
Most often these errors can be caused by corrupted drivers - but (IMO) they can also be caused by problems with memory (CPU, mobo, RAM, Video RAM).
The general pattern of the errors suggests:
- hardware problems (most likely memory)
- compatibility issues
- Windows issues
It does not suggest (to me) a driver issue.
So, let's try some different tests:
- Although a Windows corruption is least likely, let's try this as it's an easy test to run:
To test the hardware, try these free diagnostic tests:
Most often these errors can be caused by corrupted drivers - but (IMO) they can also be caused by problems with memory (CPU, mobo, RAM, Video RAM).
The general pattern of the errors suggests:
- hardware problems (most likely memory)
- compatibility issues
- Windows issues
It does not suggest (to me) a driver issue.
So, let's try some different tests:
- Although a Windows corruption is least likely, let's try this as it's an easy test to run:
And, as for the possibility of compatibility issues, please look up your hardware and software at this link: http://www.microsoft.com/windows/compatibility/windows-7/en-us/default.aspxSFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.
To test the hardware, try these free diagnostic tests:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
http://www.carrona.org/memdiag.html (read the details at the link)
http://www.carrona.org/hddiag.html (read the details at the link)
Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: http://www.carrona.org/malware.html (read the details at the link)
Then, if the above tests pass, I'd try these free stress tests:
FurMark download site: http://www.ozone3d.net/benchmarks/fur/
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exitPrime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
It looks like SFC.EXE fixed something (I can't read these logs very well).
1 - 15 of 15 Posts
- Status
- Not open for further replies.
Tech Support Forum
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!
Full Forum Listing
Top Contributors this Month
View All
spunk.funk
145 Replies
SpywareDr
54 Replies
wolfen1086
42 Replies
Recommended Communities
