New
#71
hey
did you have a look at the rest of the posts? this minidump file was uploaded after using the driver verifier...
hey
did you have a look at the rest of the posts? this minidump file was uploaded after using the driver verifier...
This is not a good thing, a STOP 0x101 revolves around your CPU - and this is an error saying that it's timing out. What settings did you use when you were running Driver Verifier
If it was the settings that I suggested, then let's try a couple more settings:
- First, run the Driver Verifier against all non-Microsoft drivers. Leave it run for 36 hours (or the first Driver Verifier dump file that you get.
- Then, run it against all Microsoft drivers - letting it run 36 hours or until you get a crash dump
- Finally, run it against all drivers (it will get very slow!). Let it run 36 hours and we'll see what you get.
Info from this post: https://www.sevenforums.com/crashes-d...tml#post356791
Good luck!...What you're looking for will be in one of the following categories:
a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
thanks. i'm gonna keep you updated.
merry christmas.
Merry Christmas to you too.
Good luck
hey guys
well, i'm attaching minidump crashes files from the last two days. i've sadly lost track of which files relate to what kind of driver verifier setting. i've tried all three of them though.
please have a look at them to see if you see something that might finally help me solve this problem, or just bring me to the conclusion that I have to send this computer back and get another one instead of it (after all, it's new and haden't had more than two problemless days with it).
thanks a lot.
It's either an issue with your video sub-system or with your storage sub-system (I suspect the video - but have no hard evidence for this).
Presuming that the BIOS is current, and that the drivers are all updated (only old one is Spyder3.sys), and that the inside the case conditions are OK (not overheating, adequate airflow, fans working, etc) - then I'd have to assume that this is a hardware issue.
Additionally the stringent testing with Driver Verfier doesn't reveal any pattern (other than the STOP 0x101 errors) - and that's usually symptomatic of a hardware failure. Send it back and let the manufacturer figure it out.
Here's the summary of the last 6 BSOD's:
Code:Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Debug session time: Sat Dec 19 06:44:08.546 2009 (GMT-5) System Uptime: 0 days 0:01:36.062 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Debug session time: Sat Dec 19 06:45:35.546 2009 (GMT-5) System Uptime: 0 days 0:00:42.062 *** WARNING: Unable to verify timestamp for nvstor32.sys *** ERROR: Module load completed but symbols could not be loaded for nvstor32.sys DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Debug session time: Sat Dec 19 06:39:36.390 2009 (GMT-5) System Uptime: 0 days 0:20:31.625 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Debug session time: Sun Dec 20 08:54:04.100 2009 (GMT-5) System Uptime: 0 days 18:46:35.350 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Debug session time: Sun Dec 20 09:27:29.546 2009 (GMT-5) System Uptime: 0 days 0:04:42.062 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Debug session time: Sun Dec 20 10:13:37.968 2009 (GMT-5) System Uptime: 0 days 0:01:10.218 *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System