BSOD from YouTube, Sites w/ Embedded adds (New Computer)

[mattmartin19]

Damn, that's a first. I got the BSOD (same error message) when I tried to run Big Picture Mode in Steam (plugged into my TV.) I've attached another dump file to include this incident.

 

[blueelvis]

blueelvis, did you mean gigabytle easytune? That's what is mentioned in the linked thread above. I do not have that installed, and to my knowledge, never did. I'm not sure what else grdv.sys is associated with, or how to remove or disable it.

You need to do a manual search then inside your PC for Gigabyte and see if you find any results. If you do not find any results then please do a manual search for "gdrv.sys" and rename it and let me know the folder in which it was present.

 

[blueelvis]

Hi Mattmartin,

First of all, I am extremely sorry for my part wrong analysis. It seems that my WinDBG was having wrong symbols and due to which it was not spitting out the errors properly.

I just rectified the symbols and re analyzed every single dump file you have attached in your thread. The below things were blamed in all the dumps which you provided to me :-

1. Processor 0 Bank 4
2. Processor 1 Bank 4
3. Processor 3 Bank 4

Since, there are different processors involved and each of them have almost similar occurrence in the Dump files, I think there is a possibility that there is not a hardware fault. So, please find that Gigabyte Software and Terminate it

Also, I would advise you to goto BIOS settings and then reset everything to the default values so as to make sure that there is nothing which is being overclocked even if it is being without your permission.

Furthermore, please run Driver Verifier by following this guide :-
Using Driver Verifier to identify issues with Drivers - Windows 7 Help Forums

Let it crash 3-4 times. I just want to make sure that there is no low level software causing this problem. Make sure your Chipset drivers are up-to-date.

 

[mattmartin19]

No apologies necessary, I am continually grateful for your assistance.

Searching for Gigabyte yielded no results. The gdrv.sys file was located in the Windows folder... I renamed it. Also, BIOS setting were reset to default. Now I am getting set up to use driver verifier. I'll post back in a bit with results.

 

[mattmartin19]

So, a few things I noticed. I remaned the gdrv.sys file to gdrv.s_y_s, but when I booted up, there was a new gdrv.sys file in the folder. I don't know what that means. Does it make a new one/modify it every time I boot up? The timestamp seems to indicate something along those lines.

I followed the instructions in the link to use driver verifier. After I restarted, I saw immediate results... I got a BSOD as soon as the log in screen popped up. The error message was:

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

It restarted itself and repeated this process a few times, same error message each time. Does that mean something to you? Since I couldn't do anything else, I eventually used system restore to go back to a point I created before starting driver verifier. I also made dump files following these events (will it still have useful data since I used system restore? I don't know anything about that). Thanks!

 

[blueelvis]

Hi Mattmartin19,

Thanks for quickly doing what I asked. I think we really are near to the solution of your problem (Touchwood! )
Below is the analysis of the Dump file generated by the Driver Verifier (Windows does not change any personal files during System Restore but rather the settings) :-

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: ffffcf80ad768ff0, address trying to free
Arg2: ffffcf80ad768ffc, address where bits are corrupted
Arg3: 000000000055000c, (reserved)
Arg4: 0000000000000024, [B][U]caller is freeing an address where bytes after the end of the allocation have been overwritten[/U][/B]

Debugging Details:
------------------


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_STR:  0xC1_24

SPECIAL_POOL_CORRUPTION_TYPE:  24

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  AdjustService.

CURRENT_IRQL:  1

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

IRP_ADDRESS: ffffcf80ad0aad89

LAST_CONTROL_TRANSFER:  from fffff80379e827bb to fffff80379de1fa0

STACK_TEXT:  
ffffd000`324ac2d8 fffff803`79e827bb : 00000000`000000c1 ffffcf80`ad768ff0 ffffcf80`ad768ffc 00000000`0055000c : nt!KeBugCheckEx
ffffd000`324ac2e0 fffff803`79f24376 : 00000000`00000010 00000000`000213f1 00000000`00000000 00000000`20206f49 : nt!MmFreeSpecialPool+0x307
ffffd000`324ac420 fffff803`79d2b8d8 : fffffa80`0002ffd0 ffffd000`324ac5f0 00000000`00000002 00000000`00000006 : nt!ExFreePoolWithTag+0x1096
ffffd000`324ac4f0 fffff803`79d2d5ec : ffffcf80`ad0aae01 ffffe000`00000001 ffffd000`324ac6a9 ffffd000`324ac740 : nt!IopCompleteRequest+0x78
ffffd000`324ac600 fffff803`7a2f7b6f : 00000000`00000000 ffffcf80`ad0aae00 ffffe000`b26fb850 fffff3fc`ee4f0f72 : nt!IopfCompleteRequest+0x7fc
ffffd000`324ac710 fffff801`86fda0c7 : 00000000`00000000 ffffe000`b2507810 00000000`00000000 ffffcf80`ad0aaea0 : nt!IovCompleteRequest+0x1d7
ffffd000`324ac7e0 00000000`00000000 : ffffe000`b2507810 00000000`00000000 ffffcf80`ad0aaea0 ffffe000`00000004 : gdrv+0x30c7


STACK_COMMAND:  kb

FOLLOWUP_IP: 
[COLOR=#ff0000][B][U]gdrv+30c7[/U][/B][/COLOR]
fffff801`86fda0c7 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  [COLOR=#ff0000][B][U]gdrv[/U][/B][/COLOR]+30c7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: [COLOR=#ff0000][U][B]gdrv[/B][/U][/COLOR]

IMAGE_NAME:  [COLOR=#ff0000][B][U]gdrv.sys[/U][/B][/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  49b9d175

FAILURE_BUCKET_ID:  0xC1_24_[COLOR=#ff0000][B][U]gdrv[/U][/B][/COLOR]+30c7

BUCKET_ID:  0xC1_24_[COLOR=#ff0000][B][U]gdrv[/U][/B][/COLOR]+30c7

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc1_24_[COLOR=#ff0000][B][U]gdrv[/U][/B][/COLOR]+30c7

FAILURE_ID_HASH:  {fd14b231-03e3-990a-9b32-092218776c8d}

Followup: MachineOwner
---------

I have highlighted why the Driver Verifier was causing the crash. It was crashing because the driver was trying to free (Deallocate) a piece of memory which was overwritten by some other program.
So, do you see what is causing the crashes (Highlighted in RED)? Psst, it is the GDRV.SYS which is the Gigabyte Easy Saver - mobo power utility driver.

First thing I would like you to check is that once you rename the driver, have you played those videos? Are they still BSODing?
Now, the thing is that, I checked your Event Viewer logs and found that the GDRV.SYS is running as a part of a Service which is setup so that it will start on demand or automatically. Now, in order to resolve your problem (touchwood!), follow these steps :-

1. Press "Start (Windows Key)+R" on your keyboard to open up the Run Prompt.

2. Type in "services.msc".

3. This would open up the Services Window. Search for "GDRV" or anything related to "GigaByte". Most likely it would be directly "GDRV".

4. Right Click on the Service and then Click On Properties. A Properties Dialog Box would open up.

5. In front of the "Startup Type" section, click on the dropdown list and then select "Disabled".

6. Click on "OK".

Now, delete the driver and see if it is regenerating or not. Most likely this should solve the problem. Keep me updated. This case of yours really got me excited ^_^ as it is very rare to see such BSOD.

 

[mattmartin19]

I disabled the Gigabyte entry using the Services Window, but the gdrv.sys file was still regenerating. After that, I uninstalled Gigabyte App Center, since that was the only other Gigabyte program I could find, then I deleted the gdrv.sys file. Once I did that, the gdrv.sys stopped coming back.

Regrettably, something is still awry, because I can still get my BSOD with YouTube, same as before :/

I threw in some new dump files if that helps. Otherwise I'll await further suggestions. Quite the mystery here...

 

[blueelvis]

I disabled the Gigabyte entry using the Services Window, but the gdrv.sys file was still regenerating. After that, I uninstalled Gigabyte App Center, since that was the only other Gigabyte program I could find, then I deleted the gdrv.sys file. Once I did that, the gdrv.sys stopped coming back.

Regrettably, something is still awry, because I can still get my BSOD with YouTube, same as before :/

I threw in some new dump files if that helps. Otherwise I'll await further suggestions. Quite the mystery here...

Awww <_< ,
I was really hoping that this would fix your problem. Unfortunately, the dump files provided by you are having the WHEA_UNCORRECTABLE_ERROR which mentioned Proc 3 Bank 4 with an Internal Unclassified Error.

What you need to do is, cut and paste all the dump files from "C:\Windows\Minidump", paste the dump files somewhere else on your PC and make sure the folder is clean. Once this is done,enable Driver Verifier just like you did it the previous time and let it crash a few times. Let's see how it goes. The cleaning is required so that we get only the Driver Verifier Enabled dumps this time.

Don't lose hope ^_^.

 

[mattmartin19]

I cleaned out the minidump and ran driver verifier again. This time I was able to log in to windows and make my way to my YouTube to generate the crash, so maybe it was good to get rid of the Gigabyte stuff anyway. I made it crash this way 3 times, and attached the new diagnostic files.

And... I hate to leave when we're so close, but that's the way it has to be. I am leaving on vacation today until August 3, so I guess our business here will have to be put on hold for a while (sorry!). Until then, take it easy. Thanks!

 

[blueelvis]

I cleaned out the minidump and ran driver verifier again. This time I was able to log in to windows and make my way to my YouTube to generate the crash, so maybe it was good to get rid of the Gigabyte stuff anyway. I made it crash this way 3 times, and attached the new diagnostic files.

And... I hate to leave when we're so close, but that's the way it has to be. I am leaving on vacation today until August 3, so I guess our business here will have to be put on hold for a while (sorry!). Until then, take it easy. Thanks!

The dump files are still pointing to the Hardware as the cause. Please Enjoy your vacations

In the meanwhile, I will ask seniors around and see what they say about this.