Windows 7: BSOD new and old

James7679 · 21 Aug 2011

Hello, I just slapped togather my new baby and I got a BSOD. It has ocurred three times, I know exactly how to replicate. After first boot, optical drive failed. I loaded the MoBos driver disk onto a flash drive. After attempting to run the disk off the flash, it BSODd. Manually retrieved Network drivers from flash drive and loaded them, went online, fixed my optical drive and as soon as I try to load the disk I get a BSOD. ONLY with that disk, but not just that program, some other innitiators are, EVGA Precision, and Riva tuner, and the funny thing about this is, even running the Uninstaller for the two previous mentioned, I get a BSOD. Thank you.

Windows 7 x64
Intel i5 2500k
Gigabyte GA-Z68A-D3-B3
8gigs Patriot Vengence
Corsair vx550
EVGA GTX550TI
lots of fans

Jonathan_King · 22 Aug 2011

Hello,

First off, uninstall Gigabyte Easy Tune, as it was blamed by one crash. You may need to go into Safe Mode to do that.

Second, run Memtest86 and the three Prime95 tests. See here:

http://www.sevenforums.com/tutorials...t-prime95.html

RAM - Test with Memtest86+

Finally, would you mind clarifying the CD drive issue for me? What is the connection between the BSODs and use of the CD drive?

If the hardware tests do not show any errors, post back with a jcgriff2 report. See here: http://www.sevenforums.com/crashes-d...tructions.html

...Summary of the dumps:

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Aug 22 05:52:31.918 2011 (UTC - 4:00)
System Uptime: 0 days 0:40:52.182
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  JBrowser.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
BiosReleaseDate = 05/02/2011
SystemProductName = Z68A-D3-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 14:53:00.852 2011 (UTC - 4:00)
System Uptime: 1 days 1:50:17.540
Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  ehexthost32.ex
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_VRF_nt!MiRemoveAnyPage+13e
BiosReleaseDate = 02/04/2009
SystemProductName = MB-750I-72P9
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 17 20:16:03.457 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:55.160
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : MpFilter.sys ( MpFilter+84d8 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x76
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x76_System_VRF_MpFilter+84d8
BiosReleaseDate = 02/04/2009
SystemProductName = MB-750I-72P9
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for Unknown_Module_fdfdfdfd`fdfdfdfd
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fdfdfdfd`fdfdfdfd
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul 15 19:15:37.897 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:48.553
*** WARNING: Unable to verify timestamp for Unknown_Module_fdfdfdfd`fdfdfdfd
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fdfdfdfd`fdfdfdfd
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xE6
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

James7679 · 23 Aug 2011

Jonathan, thank you for your replay. To answer your question about the relevance of the Optical drive issue, after reviewing what I posted, I guess there is none. Also, the MoBo, Processor, Memory, and GPU are all brand new and the referenced memory BSOD was from my old memory. What I am mostly concerned with is that I get BSOD's when I try to open ANY tuning software, whether it's Easy Tune, Riva Tuner, Precision, etc. Even upon trying to run the uninstaller for said programs I get a BSOD. More to the point, the software disk that came with the MOBO has all the necessary software and add ins for its components. When I insert the disk into the optical drive, upon loading the disk, is when I get the current BSOD. ?????

Jonathan_King · 23 Aug 2011

Do try running Memtest86 and Prime95 tests as suggested, as there may be a hardware problem involved.

Have you tried removing the tuner programs in Safe Mode?

James7679 · 23 Aug 2011

No, I will tonight. Do you have a suggestion for working around the BSOD refferencing gdrv.sys which occurs when I try to load the MoBo app disk? GDRV.SYS loads off the disk.

Jonathan_King · 23 Aug 2011

What are you attempting to do with the mobo application disc? Depending on the nature of the issue, could you adjust the autoplay settings such that the program does not automatically run when you insert the disc?

AutoPlay - Turn On or Off

James7679 · 23 Aug 2011

The disk has all of the add ins and software for running the newer processors, THX, Tuning software, USB charge, USB 3.0, ETC. Here's something else for you. I downloaded Passmark's Performance Test x64 and hen I ran it I got a BSOD. I can run all of my games(Black Ops, BFBC2, Medal of Honor) all maxed out with no problems AT ALL. So my theory is, the BSOD's are somehow linked to any kind of tuning or OCing software. Any ideas?

Jonathan_King · 24 Aug 2011

The Verifier_Enabled dump blames DirectIo.sys, which appears to be a component of Burn-in Test. We can only assume that the driver is incompatible with your firmware or software, and all that can be done is removing the program or somehow updating to a version that does not crash. I would recommend the former.

The driver is trying to load from F:\Program Files\PerformanceTest; without access to a jcgriff2 report to find the answer myself, I must ask: what is the F drive? Is that an external drive you have installed programs to, or is that the letter of your CD drive?

If the latter, all I can say is stop trying to use that disc, as it is only causing problems. If that program is installed on your system, we'll do everything in our power to delete it. If necessary, go into Safe Mode, log into the Administrator account, and delete the folder F:\Program Files\Performance Test.

Again, a jcgriff2 report would be most helpful. See here: http://www.sevenforums.com/crashes-d...tructions.html

...Summary of the dumps:

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Aug 23 08:01:25.567 2011 (UTC - 4:00)
System Uptime: 1 days 1:57:39.832
*** WARNING: Unable to verify timestamp for DirectIo.sys
*** ERROR: Module load completed but symbols could not be loaded for DirectIo.sys
Probably caused by : DirectIo.sys ( DirectIo+21e0 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  pt.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_DirectIo+21e0
BiosReleaseDate = 05/02/2011
SystemProductName = Z68A-D3-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

James7679 · 04 Sep 2011

I have been very busy at work. I have uploaded files as requested. I managed to get precision to run. I went though and deleted all versions and files on pc referencing Precision. Then I ran regedit and searched for all entries referencing Precision and deleted them. Then downloaded the file again and reinstalled. Works good now. Still having problems with the mobo app disk. As you can see, from the system health report, not all of my hardware is functioning properly due to not being able to load this disk. As far as drive F, this is my main hard drive, "f" was the letter assigned whe I reformattted to install Windows 7. On another subject, I was going to attemp a repair install, but when doing so, I got a message stating that the version I am trying to use is older than the version I have installed. The disk I have is an OEM disk for Windows 7 64bit Home Premium that I purchased when I built this PC originally. The system has since updated to SP1 for Windows 7 64bit. Is there any way to work around this(as I know I will need to do a clean install again)?

James7679 · 04 Sep 2011

Also, Memtest cleared memory 5x, and Prime95 ran for days without fault.

Windows 7: BSOD new and old

BSOD new and old problems?