Microsoft drivers are assumed to be stable, so there is no point in stressing them. It will just slow down your computer.
The way Verifier works, it stresses all drivers checked, in hopes of causing them to BSOD. When it happens, we can look at the dump and hopefully find the cause.
Just use your computer normally while Verifier is running, but don't start anything that you can't afford to lose in a BSOD.
"After a reboot, driver verifier should be enabled."
Ok, so what I did last time was what the topic said, and rebooting went fine(is that the clear sign, or am I supposed to use my computer during the time the verifier is on?
What I also did was during the driver selection, I clicked on "show not loaded drivers" and selected them all except the windows and the 2 named.
Then I couldn't reboot. During signing out it gave a BSOD(c1).
My guess is that I wasn't supposed to check the not loaded drivers, so what I'll do NOW is reboot again with only the loaded drivers selected. brb
EDIT:
back after a reboot. No problems so far. What I'll do NOW is play a game with driver verification on until my system crashes.
Or is there something else I should test?
Thanks
Just use your system just as you normally would. Play whatever games you normally play, go to the sites you normally do, and pretend Verifier is not running.
So the next BSOD is the Data Jackpot :P ?
If it's a driver issue you're having, then hopefully yes.
If the dump still doesn't point to a specific cause, we can then assume it is either a hardware problem, or low-level driver.
Ok, I got my BSOD. Not really at a nice time though:
I was getting ready for bed and wanted to shut my computer down. So I Clicked Shutdown.
And it was shutting down and BOOF, BSOD.
So I can't seem to shutdown xD Because the system will reboot after the BSOD xD
Here are the Files:
Thanks for looking into this again
I've experienced the same BSOD's as you and struggled for a couple months until I found the problem. I suspect the culprit in your case, as it was in mine, is the Gigabyte GA-770TA-UD3 M/B itself!
After 3 weeks of random BSOD's with a new system last Spring, I ended up RMA'ing the RAM, which didn't help. Finally received Gigabyte RMA authorization and returned the board. Week and half later, got it back with no explanantion. After calling, I was told they couldn't find anything wrong with it. Spoke with the manager and convinced them to allow a board replacement. When the new one arrived, it worked fine for a day and half but guess what, starting spitting out BSOD's and random restarts.
Long story short, I just ended up replacing the M/B with a MSI 790X-G45 and have run two weeks of torture tests without a single hiccup... it's been perfect!
Check out the Newegg customer satisfaction reviews and you'll see many reports of the same issue. Some have "fixed" their boards by raising the Northbridge voltage by 0.1 volts (directly from Gigabyte technician), while others have raised their PCIx and Vcor by .15 -.25 volts. But in my particular case, it didn't help.
Always liked their products but will never buy another one of these boards. If you got the resources, run, don't walk and replace the board. You'll hopefully save yourself a lot of headaches down the road.
@BWpotter, that sounds very scary! I don't want my mobo to be, well broken
@jonathan_king
I Decided to stress my system a little by running a benchmark(performance test by passmark.com). And it gave me another 3B crash.
Here are the files
Looks like Gigabyte's Dynamic Energy Saver Advanced program is the cause here, not the first time by any means.
Please remove it, and see what happens.
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\Desktop\Downloads\Documents\Windows7_BSOD_jcgriff2\082510-21528-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e0a000 PsLoadedModuleList = 0xfffff800`03047e50 Debug session time: Tue Aug 24 18:23:45.054 2010 (UTC - 4:00) System Uptime: 0 days 3:24:45.083 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C1, {fffff9802f1c8ff0, fffff9802f1c8ffc, 2d000c, 24} Unable to load image \??\C:\Windows\gdrv.sys, Win32 error 0n2 *** 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+30c7 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) Special pool has detected memory corruption. Typically the current thread's stack backtrace will reveal the guilty party. Arguments: Arg1: fffff9802f1c8ff0, address trying to free Arg2: fffff9802f1c8ffc, address where bits are corrupted Arg3: 00000000002d000c, (reserved) Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten Debugging Details: ------------------ BUGCHECK_STR: 0xC1_24 SPECIAL_POOL_CORRUPTION_TYPE: 24 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: essvr.exe CURRENT_IRQL: 1 IRP_ADDRESS: fffff9802c380f3b LAST_CONTROL_TRANSFER: from fffff80002f81843 to fffff80002e7a740 STACK_TEXT: fffff880`06d0d4f8 fffff800`02f81843 : 00000000`000000c1 fffff980`2f1c8ff0 fffff980`2f1c8ffc 00000000`002d000c : nt!KeBugCheckEx fffff880`06d0d500 fffff800`02fad356 : fffff800`02e0a000 00000000`20206f49 ffffffff`ffef7148 fffffa80`04e24200 : nt!MmFreeSpecialPool+0x383 fffff880`06d0d630 fffff800`02e99d9e : 00000000`00000000 fffff980`2c380fb0 fffff980`2c380ee0 fffff980`2c380fb0 : nt!ExDeferredFreePool+0xf13 fffff880`06d0d6e0 fffff800`02e7d0dd : fffff980`2c380fb3 fffff800`00000001 00000000`00000001 fffff880`00000005 : nt!IopCompleteRequest+0x5ce fffff880`06d0d7b0 fffff800`0331a19f : fffff980`2c380ee0 fffffa80`07556400 fffff980`2c380f00 00000000`00000000 : nt!IopfCompleteRequest+0x75d fffff880`06d0d890 fffff880`07d710c7 : fffff880`07d71a50 00000000`00000008 00000000`00000000 fffff980`2c380fb0 : nt!IovCompleteRequest+0x19f fffff880`06d0d960 fffff880`07d71a50 : 00000000`00000008 00000000`00000000 fffff980`2c380fb0 00000000`00000001 : gdrv+0x30c7 fffff880`06d0d968 00000000`00000008 : 00000000`00000000 fffff980`2c380fb0 00000000`00000001 00000000`00000000 : gdrv+0x3a50 fffff880`06d0d970 00000000`00000000 : fffff980`2c380fb0 00000000`00000001 00000000`00000000 00000000`00000001 : 0x8 STACK_COMMAND: kb FOLLOWUP_IP: gdrv+30c7 fffff880`07d710c7 ?? ??? SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: gdrv+30c7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: gdrv IMAGE_NAME: gdrv.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49b9d175 FAILURE_BUCKET_ID: X64_0xC1_24_VRF_gdrv+30c7 BUCKET_ID: X64_0xC1_24_VRF_gdrv+30c7 Followup: MachineOwner ---------
Just deinstalled it, didn't need it anyway.
The question is, I have to Reboot now. My guess is I'll get the crash on shutdown again(the C1 one)
I'll let you know in a sec
Quote