BSOD Bug Check Code 50

[cort64]

I built a new computer a couple of months back using all new parts from an online store. Ever since day one I have experienced the occasional BSOD. I have tried updating the video card drivers, reseating the RAM etc but to no avail. I have used Memtest x86 and Windows 7 memory disgnostic and found no faults.

Sometimes the computer will BSOD within minutes of being booted yet at other times it can run for days without a problem. Lately the BSODs have become much more frequent. Any ideas?

System Specs:
AMD Phenom II X6 1100T
8 GB DDR3 1333
Radeon HD 6970
Windows 7 Home Premium x64 OEM

 

[zigzag3143]

I built a new computer a couple of months back using all new parts from an online store. Ever since day one I have experienced the occasional BSOD. I have tried updating the video card drivers, reseating the RAM etc but to no avail. I have used Memtest x86 and Windows 7 memory disgnostic and found no faults.

Sometimes the computer will BSOD within minutes of being booted yet at other times it can run for days without a problem. Lately the BSODs have become much more frequent. Any ideas?

System Specs:
AMD Phenom II X6 1100T
8 GB DDR3 1333
Radeon HD 6970
Windows 7 Home Premium x64 OEM

These could not read the faulting driver. Please run driver verifier to find out which

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

 

[cort64]

Ok. I followed your instructions and got a blue screen before I got into windows. It mentioned a file called RTKVHD64.sys

I have restarted the computer and it is up and running for the moment. What should I do next?

Edit - Another BSOD happened. This time at the top of the screen it displayed the following:
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

When I rebooted I got another BSOD before I got into Windows (RTKVHD.SYS again). I am back up and running again but probably not for long at this rate.

 

[zigzag3143]

Ok. I followed your instructions and got a blue screen before I got into windows. It mentioned a file called RTKVHD64.sys

I have restarted the computer and it is up and running for the moment. What should I do next?

Edit - Another BSOD happened. This time at the top of the screen it displayed the following:
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

When I rebooted I got another BSOD before I got into Windows (RTKVHD.SYS again). I am back up and running again but probably not for long at this rate.

Obviously we need the DMP files to be sure but the RTKVHD.SYS is your realtek Audio driver. I would re-install it.

 

[cort64]

Sorry. Here's the new dump files. So we can confirm.

 

[cort64]

Update - I went back to the restore point I created at the start then re-installed the Realtek driver using the one Gigabyte has on their website for the motherboard. Unfortunately I am still getting BSODs. Is there any way to get a newer version the realtek driver without using Driverguide? I am wondering whether a newer version will help..

 

[zigzag3143]

Newest crash (driver verified) identifies the mis-behaving driver.

It is related to the gdrv.sys which appears to be a driver for Gigabyte's Dynamic Energy Saver Advanced program. ...

I would update, at least, disable, if possible, or remove to test.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\061711-24070-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0321b000 PsLoadedModuleList = 0xfffff800`03460e90
Debug session time: Thu Jun 16 09:46:37.222 2011 (GMT-4)
System Uptime: 0 days 0:27:19.377
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff98038faeff0, fffff98038faeffc, 7f000c, 24}
[COLOR=Red][B]
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 )[/B][/COLOR]

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: fffff98038faeff0, address trying to free
Arg2: fffff98038faeffc, address where bits are corrupted
Arg3: 00000000007f000c, (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
[B][COLOR=Red]
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR][/B]

PROCESS_NAME:  essvr.exe

CURRENT_IRQL:  1

IRP_ADDRESS:  fffff9803b90af3b

LAST_CONTROL_TRANSFER:  from fffff80003399e14 to fffff8000329b640

STACK_TEXT:  
fffff880`07ef24e8 fffff800`03399e14 : 00000000`000000c1 fffff980`38faeff0 fffff980`38faeffc 00000000`007f000c : nt!KeBugCheckEx
fffff880`07ef24f0 fffff800`033c593b : fffff800`0321b000 00000000`20206f49 00000000`0006b597 fffffa80`09aca090 : nt!MmFreeSpecialPool+0x374
fffff880`07ef2630 fffff800`032b0afe : 00000000`00000000 fffff980`3b90afb0 fffff980`0120a6c0 fffff980`3c10aee0 : nt!ExDeferredFreePool+0xf33
fffff880`07ef26e0 fffff800`0329edbf : fffff980`3b90afb3 fffff800`00000001 00000000`00000001 fffff880`00000005 : nt!IopCompleteRequest+0x5ce
fffff880`07ef27b0 fffff800`0373819f : fffff980`3b90aee0 fffffa80`0a798e00 fffff980`3b90af00 00000000`00000000 : nt!IopfCompleteRequest+0x6df
fffff880`07ef2890 fffff880`09eba0c7 : fffff880`09ebaa50 00000000`00000008 00000000`00000000 fffff980`3b90afb0 : nt!IovCompleteRequest+0x19f
fffff880`07ef2960 fffff880`09ebaa50 : 00000000`00000008 00000000`00000000 fffff980`3b90afb0 00000000`00000001 : gdrv+0x30c7
fffff880`07ef2968 00000000`00000008 : 00000000`00000000 fffff980`3b90afb0 00000000`00000001 00000000`00000000 : gdrv+0x3a50
fffff880`07ef2970 00000000`00000000 : fffff980`3b90afb0 00000000`00000001 00000000`00000000 00000000`00000001 : 0x8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
gdrv+30c7
fffff880`09eba0c7 ??              ???

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
---------

0: kd> kb
RetAddr           : Args to Child                                                           : Call Site
fffff800`03399e14 : 00000000`000000c1 fffff980`38faeff0 fffff980`38faeffc 00000000`007f000c : nt!KeBugCheckEx
fffff800`033c593b : fffff800`0321b000 00000000`20206f49 00000000`0006b597 fffffa80`09aca090 : nt!MmFreeSpecialPool+0x374
fffff800`032b0afe : 00000000`00000000 fffff980`3b90afb0 fffff980`0120a6c0 fffff980`3c10aee0 : nt!ExDeferredFreePool+0xf33
fffff800`0329edbf : fffff980`3b90afb3 fffff800`00000001 00000000`00000001 fffff880`00000005 : nt!IopCompleteRequest+0x5ce
fffff800`0373819f : fffff980`3b90aee0 fffffa80`0a798e00 fffff980`3b90af00 00000000`00000000 : nt!IopfCompleteRequest+0x6df
fffff880`09eba0c7 : fffff880`09ebaa50 00000000`00000008 00000000`00000000 fffff980`3b90afb0 : nt!IovCompleteRequest+0x19f
fffff880`09ebaa50 : 00000000`00000008 00000000`00000000 fffff980`3b90afb0 00000000`00000001 : gdrv+0x30c7
00000000`00000008 : 00000000`00000000 fffff980`3b90afb0 00000000`00000001 00000000`00000000 : gdrv+0x3a50
00000000`00000000 : fffff980`3b90afb0 00000000`00000001 00000000`00000000 00000000`00000001 : 0x8
0: kd> k
Child-SP          RetAddr           Call Site
fffff880`07ef24e8 fffff800`03399e14 nt!KeBugCheckEx
fffff880`07ef24f0 fffff800`033c593b nt!MmFreeSpecialPool+0x374
fffff880`07ef2630 fffff800`032b0afe nt!ExDeferredFreePool+0xf33
fffff880`07ef26e0 fffff800`0329edbf nt!IopCompleteRequest+0x5ce
fffff880`07ef27b0 fffff800`0373819f nt!IopfCompleteRequest+0x6df
fffff880`07ef2890 fffff880`09eba0c7 nt!IovCompleteRequest+0x19f
[B]fffff880`07ef2960 fffff880`09ebaa50 gdrv+0x30c7
fffff880`07ef2968 00000000`00000008 gdrv+0x3a50[/B]
fffff880`07ef2970 00000000`00000000 0x8
0: kd> lmvm gdrv
start             end                 module name
fffff880`09eb7000 fffff880`09ec0000   gdrv     T (no symbols)           
    Loaded symbol image file: gdrv.sys
    Image path: \??\C:\Windows\gdrv.sys
    Image name: gdrv.sys
    Timestamp:        Thu Mar 12 23:22:29 2009 (49B9D175)
    CheckSum:         000105CE
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[cort64]

Thanks for all your help. I have uninstalled the Energy Saver (never used it anyway) and so far so good. I will be sure to let you know if we have had total success in the next day or two.

Cheers.

 

[zigzag3143]

Thanks for all your help. I have uninstalled the Energy Saver (never used it anyway) and so far so good. I will be sure to let you know if we have had total success in the next day or two.

Cheers.

Glad I could help and good luck

Ken