Windows 7: BSOD - While idling and using

Hello all, I come here after some help to solve the problem of my recurring BSODs, I have had 18 of them (well 18 minidumps are logged) since the 29th of August.

At first I came to think it was due to my PSU not giving off enough power when I leave my computer on overnight - even though it ran fine on WinXP so I turned off all powersaving settings yet it still occurs, and now it is happening while I am using it (just surfing the net or gaming).

My spec is listed - Everything is default, bar the GPU which came factory overclocked. The cpu sits at 30c - 35c and upto 50c when gaming, not sure about the GPU.

Here is the latest minydump and error (this morning)

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 3081

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF880029C332D
BCP3: FFFFF880094F1F40
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


Thank you for any help you can give.

There's a possibility that the machine has been pwned by malware, although I should emphasise that's just a wild stab in the dark.

The crash has something to do with a driver called gdrv.sys, except the one on your machine doesn't look quite like it should, hence the pwnage theory, but that might just be a side-effect of the way that data has been committed to the minidump at the time of the crash.

Does that box have a Gigabyte motherboard? If so, you might want to make sure the BIOS and the motherboard drivers are all up-to-date. If not, I suggest panicking and running every anti-malware scan you can find.

It is a Gigabyte motherboard, I have updated the drivers many times, but I will do it again to make sure - Then ill get onto panicking.

Okay, I just finished updating the bios which I now know I have not updated since I started using Windows 7, so I hope that is the problem of the BSODs.

contagous

this one was caused by gigabyte energy saver gdrv.sys. either the BIOS needs to be updated or your original premise about the PSU might be correct.

Are you over clocking anything?


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


Loading Dump File [C:\Users\K\Desktop\092409-18610-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02e9ee50
Debug session time: Wed Sep 23 21:51:24.786 2009 (GMT-4)
System Uptime: 0 days 16:56:07.300
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880029c332d, fffff880094f1f40, 0}

Probably caused by : gdrv.sys ( gdrv+332d )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880029c332d, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880094f1f40, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
gdrv+332d
fffff880`029c332d 488941e0 mov qword ptr [rcx-20h],rax

CONTEXT: fffff880094f1f40 -- (.cxr 0xfffff880094f1f40)
rax=2468746c61654824 rbx=fffff8800956ca88 rcx=0000000000000020
rdx=fffff8800956ca88 rsi=0000000000000020 rdi=fffffa8003b8f4c0
rip=fffff880029c332d rsp=fffff880094f2928 rbp=fffffa800213d110
r8=000000000000ffff r9=00000000000007ff r10=0000000000010020
r11=0000000000000000 r12=fffffa8001913640 r13=0000000000000020
r14=fffffa8003b8f4c0 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
gdrv+0x332d:
fffff880`029c332d 488941e0 mov qword ptr [rcx-20h],rax ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: GUI.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880029c332d

STACK_TEXT:
fffff880`094f2928 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : gdrv+0x332d


FOLLOWUP_IP:
gdrv+332d
fffff880`029c332d 488941e0 mov qword ptr [rcx-20h],rax

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: gdrv+332d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: gdrv

IMAGE_NAME: gdrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49b9d175

STACK_COMMAND: .cxr 0xfffff880094f1f40 ; kb

FAILURE_BUCKET_ID: X64_0x3B_gdrv+332d

BUCKET_ID: X64_0x3B_gdrv+332d

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

I was overclocking my CPU from 3.0GHz to 3.6GHz, but reverted it after the first two BSODs and my graphics card came overclocked as an "extreme+" edition.

I updated the BIOS last night on the recomendation of H2SO4, and after leaving it on overnight (usually when the BSOD occurs) it is so far so good.

Thank you both for the help so far, and I hope that it was just the BIOS update that was needed.

The (gigabyte-related) gdrv.sys driver communicates with the hardware (BIOS) for purposes relating to power management, apparently. Hence, crashes involving that driver could in theory come down to bad data being fed to it during its interaction with the BIOS code. Hopefully those updates will continue to work for you. If not, please upload more minidumps.

Ugh, just had another BSOD and this time I noticed it did mention "gdrv.sys".

I am now wondering if I installed the BIOS update incorrectly, I used Qflash, selected the USB drive the the .f8 file on it, flashed and then loaded Optimized Defaults. Is that all that was needed or is something missing?