bsod on wake from sleep + bios corruption

win7x64 said:

Having searched for weeks on this problem I've registered here after reading your impressive replies to similar problems.

The system is a recent build, less than 2 months old, and the problem has occurred from the outset.

S3 is enabled in the bios, which is the original Award (F3); rev. F8 is available but one attempt to flash via the internet failed (this mobo does not support floppies) and I had to clear cmos and rebuild the raid array using Intel's Rapid Storage app to get the system to post again and regain access to the bios.

I've tried to make an emulation floppy bios cdrom to update the bios but the program I used (Bart's clean20, which everyone links to in this situation) failed to insert the actual bios file when running the iso build.

A further complication: the latest bsod has corrupted the bios again (it's a dual bios mobo) and I cannot access it at post but the OS will load. I'd also be extremely grateful for the procedure to update the bios and correct this problem in one fell swoop if it's at all possible to do so.

A zip file with the problem report and dump file app's results are found here: Windows_NT6_BSOD_jcgriff2.7z

In short, quite the mess! I'd be extremely grateful for any help offered.

Hi and welcome to SF!
Why do not you use the Gigabyte @ bios?! It can be download here: @BIOS
It's very use to use, but read carefully the instructions. And here is your update bios: http://www.gigabyte.com/products/pro...=3655&dl=#bios
Good luck and let us know the results!

win7x64 said:

Thanks for the welcome and the reply.

Using the @bios utility is what caused the first bios corruption and all reports are that using these sorts of programs is risky (Gigabyte states this as well, btw), so I'd like to avoid trying it again if possible.

That sounds strange to me ... Already upgraded a dozen motherboards and never had problems ... It is noteworthy that always used to update via file, never via internet. You've followed all the instructions to the letter? You can try via Q-flash. Just use a flashdrive with the files. Simply run the bios file you downloaded from Gigabyte's site and copy the files to the flashdrive. Reboot and press END to enter Q-Flash. You can follow the instructions in your owner's manual. Good luck and come back to tell us the result.

win7x64 said:

Unfortunately the latest bsod has corrupted my bios and I can't enter it to use Qflash either.

As it is, I don't want to touch the bios right now and risk my system not posting again until I can deal with all the problems in the proper order.

I've got a sleep bsod that corrupts my bios so tackling that first seems to me to be most important first step--but obviously the corrupt bios is also a mess and I could be wrong about where to start.

I don't even know if a bios update will help the bsod problem in any event--Gigabyte's rev. notes don't indicate anything applicable to my system beyond the one I have, which is only a few months old anyway as this is a new board.

Then I suggest you seek advice from Gigabyte forum. I had a small problem and was very well managed by the members there. Here's the link: forum.giga-byte.co.uk
I really hope you can solve it! Come back to tell us what happens. Best regards!

Your last BSOD was caused by your video card.
Update your drivers from here

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800f89e390, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880044133bc, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+73bc
fffff880`044133bc 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`023c4858 fffff880`044b7000 : 00000000`00000116 fffffa80`0f89e390 fffff880`044133bc 00000000`00000000 : nt!KeBugCheckEx
fffff880`023c4860 fffff880`044b6d0a : fffff880`044133bc fffffa80`0f89e390 fffffa80`0f53fd50 fffffa80`0ff78010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`023c48a0 fffff880`05366f07 : fffffa80`0f89e390 00000000`00000000 fffffa80`0f53fd50 fffffa80`0ff78010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`023c48d0 fffff880`05394d5a : 00000000`ffffffff 00000000`00220c99 fffff880`023c4a30 fffffa80`0ff78010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`023c49b0 fffff880`053906af : fffffa80`0ff78010 ffffffff`feced300 00000000`00000002 fffffa80`11a59140 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`023c49f0 fffff880`0538f023 : fffffa80`0ff78010 00000000`00000002 fffff880`0538edc0 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`023c4ae0 fffff880`0538f2fe : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`023c4b10 fffff880`053622c6 : ffffffff`ff676980 fffffa80`0ff78010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`023c4bb0 fffff880`0538ee7a : 00000000`00000000 fffffa80`0f53fd50 00000000`00000080 fffffa80`0ff78010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`023c4cc0 fffff800`02f747c6 : 00000000`fffffc32 fffffa80`1001d8c0 fffffa80`0c75c040 fffffa80`1001d8c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`023c4d00 fffff800`02cafc26 : fffff880`009eb180 fffffa80`1001d8c0 fffff880`009f5fc0 fffff880`01456534 : nt!PspSystemThreadStartup+0x5a
fffff880`023c4d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+73bc
fffff880`044133bc 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+73bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner

Code:

GVTDrv64.sys Tue Sep 05 03:10:02 2006

Gigabyte EasyTune6 driver (known issues w/Win7) - Please Uninstall

I also saw that you have AVG installed. AVG is known to cause problems on some windows 7 machines. Use this tool to uninstall it and install MSE for the time being.

Download the latest ATI driver from here. Your driver is dated from January. They released a new driver in February.