BSOD Windows 7 - ntoskrnl.exe+7cc40

writhziden · 27 Feb 2012

Alright, let us know how both of those steps go. :)

garthrs · 28 Feb 2012

Installed Corsair GS700

Got 2 BSOD right away...

First sent me to realtek NIC driver.

I updated it to the right driver... Got out the box and saw DYNEX DX-PCIGB... Thought I had realtek.

Second dump was the standard ntoskrnl.exe

writhziden · 28 Feb 2012

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\garthrs\Windows_NT6_BSOD_jcgriff2\022812-19234-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1d000 PsLoadedModuleList = 0xfffff800`03062670
Debug session time: Tue Feb 28 18:37:21.485 2012 (UTC - 7:00)
System Uptime: 0 days 0:06:30.656
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {1ab8f80, a7b000017bf71867, fffff880093b7a90, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4433c )

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

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 0000000001ab8f80, Virtual address for the attempted execute.
Arg2: a7b000017bf71867, PTE contents.
Arg3: fffff880093b7a90, (reserved)
Arg4: 0000000000000000, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  linpack_xeon64

CURRENT_IRQL:  a

TRAP_FRAME:  fffff880093b7a90 -- (.trap 0xfffff880093b7a90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000000a
rdx=000000000000c007 rsi=0000000000000000 rdi=0000000000000000
rip=0000000001ab8f80 rsp=fffff880093b7c28 rbp=fffff880093b7ca0
 r8=fffffa8006dd0000  r9=0000000000000000 r10=fffffa8006dd0060
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe nc
00000000`01ab8f80 1e              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e43fc0 to fffff80002e99c40

STACK_TEXT:  
fffff880`093b7928 fffff800`02e43fc0 : 00000000`000000fc 00000000`01ab8f80 a7b00001`7bf71867 fffff880`093b7a90 : nt!KeBugCheckEx
fffff880`093b7930 fffff800`02e97d6e : bfd536c2`00000003 fffff800`00000000 c00c2a16`00000003 00000000`00001600 : nt! ?? ::FNODOBFM::`string'+0x4433c
fffff880`093b7a90 00000000`01ab8f80 : fffff880`093b7ca0 00000000`01a0f580 00000000`00001100 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`093b7c28 fffff880`093b7ca0 : 00000000`01a0f580 00000000`00001100 00000000`00000000 00001fa0`00010000 : 0x1ab8f80
fffff880`093b7c30 00000000`01a0f580 : 00000000`00001100 00000000`00000000 00001fa0`00010000 00000000`00000008 : 0xfffff880`093b7ca0
fffff880`093b7c38 00000000`00001100 : 00000000`00000000 00001fa0`00010000 00000000`00000008 00000000`d914c9c0 : 0x1a0f580
fffff880`093b7c40 00000000`00000000 : 00001fa0`00010000 00000000`00000008 00000000`d914c9c0 00000000`d91f0f28 : 0x1100


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4433c
fffff800`02e43fc0 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4433c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+4433c

BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+4433c

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

linpack_xeon64...?

Try running Windows with one RAM module at a time in one slot at a time. Try to find a good module and a good slot, then test the other slots with the good module and each module with the good slot. Avoid Static Damage to Your PC | PCWorld when moving modules around.

garthrs · 01 Mar 2012

Hmmm, I lost a post.

First Stick has been checked in the first slot. 8 passes.

I wiped my second drive and installed Windows 7 on it. I'll give that a run tonight, but while I'm at work, Stick #1 in slot #2.

Attached are some more dump files...

writhziden · 01 Mar 2012

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\garthrs\Windows_NT6_BSOD_jcgriff2\022912-27128-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`0305c670
Debug session time: Wed Feb 29 13:54:03.831 2012 (UTC - 7:00)
System Uptime: 0 days 0:32:06.516
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : mouclass.sys ( mouclass!MouseClassServiceCallback+47e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3534363563383837
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  cpuocct.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880009b0218 -- (.exr 0xfffff880009b0218)
ExceptionAddress: fffff80002eee79b (nt! ?? ::FNODOBFM::`string'+0x000000000000cdd1)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880009b02c0 -- (.trap 0xfffff880009b02c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000006 rbx=0000000000000000 rcx=407024748b486824
rdx=000000000000002f rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eee79b rsp=fffff880009b0458 rbp=fffffa8006d28298
 r8=000000000000000d  r9=000000000000000f r10=fffff80002e17000
r11=fffff880009b0430 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt! ?? ::FNODOBFM::`string'+0xcdd1:
fffff800`02eee79b 83494c08        or      dword ptr [rcx+4Ch],8 ds:b830:40702474`8b486870=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8b5fe to fffff80002e93c10

STACK_TEXT:  
fffff880`009af2f8 fffff800`02e8b5fe : fffff800`0309d110 fffff800`02e96f85 fffff800`02fd99e0 fffff880`009b0218 : nt!KeBugCheck
fffff880`009af300 fffff800`02ebf4fd : fffff800`0309d71c fffff800`02fdac30 fffff800`02e17000 fffff880`009b0218 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009af330 fffff800`02ebe2d5 : fffff800`02fde028 fffff880`009af3a8 fffff880`009b0218 fffff800`02e17000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009af360 fffff800`02ecf361 : fffff880`009b0218 fffff880`009afa70 fffff880`00000000 fffffa80`00000006 : nt!RtlDispatchException+0x415
fffff880`009afa40 fffff800`02e932c2 : fffff880`009b0218 fffffa80`06d28298 fffff880`009b02c0 fffff800`02e75406 : nt!KiDispatchException+0x135
fffff880`009b00e0 fffff800`02e91bca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`009b02c0 fffff800`02eee79b : fffff800`02e751d0 00000000`00000000 fffffa80`06d28298 fffffa80`06d28298 : nt!KiGeneralProtectionFault+0x10a
fffff880`009b0458 fffffa80`06d28190 : fffff800`02e75406 fffff880`02fd5180 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0xcdd1
fffff880`009b04c8 fffff800`02e75406 : fffff880`02fd5180 00000000`00000000 00000000`00000001 fffff980`00000006 : 0xfffffa80`06d28190
fffff880`009b04d0 fffff800`02e97843 : fffffa80`06d3cd10 00000000`a000000c 00000000`00000000 fffff800`02f50803 : nt!KeInsertQueueApc+0xa2
fffff880`009b0530 fffff800`0333319f : fffff980`2558cca0 00000000`00000006 fffffa80`063f5a06 00000000`00000000 : nt!IopfCompleteRequest+0xb63
fffff880`009b0620 fffff880`00dedcd6 : 00000000`00000004 fffffa80`063f5a90 fffff980`2558cca0 fffffa80`063f5a90 : nt!IovCompleteRequest+0x19f
fffff880`009b06f0 fffff880`06995c79 : 00000000`00000002 00000000`ffffffff fffffa80`0640da20 fffffa80`063f5de0 : mouclass!MouseClassServiceCallback+0x47e
fffff880`009b0770 fffff800`0333b5d6 : fffff980`0c1befb0 fffffa80`00000000 fffff880`00000001 fffff980`00000001 : mouhid!MouHid_ReadComplete+0x69d
fffff880`009b07f0 fffff800`02e97021 : fffff980`0c1befb3 00000000`00000001 00000000`00000000 fffff800`02f50803 : nt!IovpLocalCompletionRoutine+0x166
fffff880`009b0850 fffff800`0333319f : fffff980`0c1bed30 fffffa80`063e6c06 fffffa80`063eb806 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`009b0940 fffff880`0695a9c4 : fffffa80`063eb830 fffffa80`063eb820 fffffa80`063eb830 fffffa80`063eb820 : nt!IovCompleteRequest+0x19f
fffff880`009b0a10 fffff880`0695ac2d : fffffa80`063f2c02 fffffa80`063f2cb0 fffffa80`063e6ca0 00000000`00000006 : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff880`009b0aa0 fffff800`0333b5d6 : fffff980`0c15cfb0 fffffa80`063e6ca0 fffff880`009b0c01 fffff980`0c15cdc0 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff880`009b0b30 fffff800`02e97021 : fffff980`0c15cfb3 00000000`00000001 00000000`00000000 fffff800`02f50803 : nt!IovpLocalCompletionRoutine+0x166
fffff880`009b0b90 fffff800`0333319f : fffff980`0c15cdc0 fffffa80`0509ee00 fffffa80`060d0000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`009b0c80 fffff880`04213631 : fffffa80`060d0050 fffffa80`05274d02 00000000`00000002 fffffa80`060d0050 : nt!IovCompleteRequest+0x19f
fffff880`009b0d50 fffff880`04213b0f : fffffa80`073f2802 fffff980`0c15cdc0 00000000`ffffffff fffffa80`060d0eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`009b0e30 fffff880`0421166f : fffffa80`060d0eb0 fffffa80`060d01a0 fffffa80`060d1050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`009b0e90 fffff880`04202f89 : fffffa80`060d0050 00000000`00000000 fffffa80`060d0e02 fffffa80`060d0eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`009b0ed0 fffff800`02e9f0ac : fffff880`02fd5180 fffffa80`060d0eb0 fffffa80`060d0ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`009b0f00 fffff800`02e96765 : 2f250d30`260e3026 fffffa80`07420060 00000000`00000000 fffff880`04202db0 : nt!KiRetireDpcList+0x1bc
fffff880`009b0fb0 fffff800`02e9657c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`09c3cbe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mouclass!MouseClassServiceCallback+47e
fffff880`00dedcd6 488d4e20        lea     rcx,[rsi+20h]

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  mouclass!MouseClassServiceCallback+47e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mouclass

IMAGE_NAME:  mouclass.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc116

FAILURE_BUCKET_ID:  X64_0x1E_0_VRF_mouclass!MouseClassServiceCallback+47e

BUCKET_ID:  X64_0x1E_0_VRF_mouclass!MouseClassServiceCallback+47e

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

A USB/HID related crash...

The rest of the .dmp files were similar to your previous ones.

Start with USB Driver - General Fix for Problems and then use a hard reset to resolve hardware and software issues (which works for all computers, not just HP Pavilions) in case your USB hubs entered a different power state to protect your computer from a surge.

garthrs · 01 Mar 2012

The dump that was in might be before I ran through your steps. I forgot to add that I did that.

Stick #1 passed 8 times in Slot #2.

Did some troubleshooting with the new install. I loaded Win7, updated all the way, and loaded JAVA and minecraft. Played for about a half an hour. No crashes.

Installed Fraps and set it to record to the OLD win 7 drive. 5 minutes in... crash. (Dump attached, not DV enabled)

Set fraps to record to NEW win 7 drive... Played fine (so far).

I'll enable DV and try to get it to crash again. But right now, I'm thinking the drive might be bad... It did pass the WD diagnosis, but i had bad ram pass the MEMtest86+ so I'm taking no chances.

I am currently formatting the old win 7 drive and will test it again once it's done.

Thanks a million for your patience so far. We might have an end in sight.

writhziden · 01 Mar 2012

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\garthrs\Windows_NT6_BSOD_jcgriff2\030112-24367-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02853000 PsLoadedModuleList = 0xfffff800`02a90e70
Debug session time: Thu Mar  1 16:47:50.630 2012 (UTC - 7:00)
System Uptime: 0 days 0:28:26.206
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffffa8005affb60, fffff88009eb5880, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )

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

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

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

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
+0
fffffa80`05affb60 06              ???

CONTEXT:  fffff88009eb5880 -- (.cxr 0xfffff88009eb5880)
rax=fffffa8005006020 rbx=0000000000000000 rcx=fffffa800502f000
rdx=0000000000000247 rsi=fffffa8003ba66c0 rdi=fffff88009eb6430
rip=fffffa8005affb60 rsp=fffff88009eb6258 rbp=fffff88000bc0000
 r8=000000000ba80000  r9=0000000000000000 r10=0000000000000247
r11=fffff8a00875a000 r12=fffffa8003bca000 r13=0000000000007138
r14=ffffffffc000000d r15=fffffa8005d60000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
fffffa80`05affb60 06              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  javaw.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffffa8005affb60

STACK_TEXT:  
fffff880`09eb4fb8 fffff800`028c2b29 : 00000000`0000003b 00000000`c000001d fffffa80`05affb60 fffff880`09eb5880 : nt!KeBugCheckEx
fffff880`09eb4fc0 fffff800`028c247c : fffff880`09eb6018 fffff880`09eb5880 00000000`00000000 fffff880`050f3dec : nt!KiBugCheckDispatch+0x69
fffff880`09eb5100 fffff800`028e92dd : fffff960`002ef924 fffff960`002b56ac fffff960`00000000 fffff880`09eb6018 : nt!KiSystemServiceHandler+0x7c
fffff880`09eb5140 fffff800`028f0950 : fffff800`02a13198 fffff880`09eb51b8 fffff880`09eb6018 fffff800`02853000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`09eb5170 fffff800`028fd8cf : fffff880`09eb6018 fffff880`09eb5880 fffff880`00000000 fffff880`09eb6430 : nt!RtlDispatchException+0x410
fffff880`09eb5850 fffff800`028c2c02 : fffff880`09eb6018 00000000`00000000 fffff880`09eb60c0 fffffa80`03ba66c0 : nt!KiDispatchException+0x16f
fffff880`09eb5ee0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceHandler+7c
fffff800`028c247c b801000000      mov     eax,1

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceHandler+7c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

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

Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...

I notice you do not yet have Service Pack 1 installed as of this crash; please install it if you have not yet done so and report back how the system runs.

Also, glad to see you tracked it down to a possible hard disk problem. See how things go after the format.

On a hunch, I also checked your drivers...

Code:

ASACPI	fffff880`03e1d000	fffff880`03e25000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys

Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:

Going to the Asus motherboard support site
When you reach the website:
Scroll down the page and click Utilities
Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
Download and install the driver.
After installation is complete, verify that it installed correctly.
- Click Start Menu
- Click My Computer
- Go to C:\WIndows\System32\drivers\
- Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

Thanks to JMH and zigzag3143 for the above information.

garthrs · 01 Mar 2012

ATK0110 Has been updated. I forgot to do that when I reinstalled win7.

Speaking of which, new installed BS'ed on me, but identified the video card.

Dump file attached.

Not sure why SP1 isn't installed... It says i have zero updates. I'll download it.

When I formatted the suspected bad drive, I did a zero write first. so the drive is now 100% empty.

Most recent crash was while recording to new win 7 drive with fraps while playing minecraft.

writhziden · 01 Mar 2012

Do you have two graphics cards in your system?

Code:

atikmdag	fffff880`04639000	fffff880`050c4000	Mon Dec 05 19:52:23 2011 (4edd8367)	00a43704	None	atikmdag.sys
atikmpag	fffff880`02a00000	fffff880`02a55000	Mon Dec 05 19:12:14 2011 (4edd79fe)	0005f792		atikmpag.sys

ASACPI...

Code:

ASACPI	fffff880`03f68000	fffff880`03f70000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys

Use the link I posted above in my previous post for updating the ASACPI software.

garthrs · 02 Mar 2012

mdag is a kernel management file and mpag is a multivendor miniport driver

I updated my ASACPI to 5/14/2009 ver 1043.5

I noted my temps are up during a crash... They were rock solid early last month when I checked them, but now the are hitting 83+ right before the crashes. I replaced the TIM, just incase... My liquid cooler is working... As far as I can tell. But the temps are 65+ during normal operations and 71+ under a load.

There were a couple of crashes that didn't generate a dump for some reason.