BSOD (halmacpi.dll the cause?)

WeirdWolf · Nov 18, 2010

111810-12589-01.dmp
18.11.2010 21:32:31
IRQL_NOT_LESS_OR_EQUAL
0x0000000a 0x00000008 0x00000002 0x00000001 0x8281292e halmacpi.dll
halmacpi.dll+392e
Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\Minidump\111810-12589-01.dmp 4 15 7600

Hallo,
I am getting random crashes when playing starcraft2, I tried to solve this problem since days. I used the bluescreenviewer and it says that halmacpi.dll is the cause of the problem. Though I cannot replace or change the file. I have the pc since a few months and the problem is definetly new.

what I did and what didn't help: reinstalling windows, reinstalling game, antivirus, replacing displaydrivers, memtest, defragmentating, giving it to the shop for hardware checks.

I really hope that someone can help me, because I am running out of ideas.

WeirdWolf · Nov 18, 2010

This are the minidumps of my last crashes. Sorry I forgot to attach them.

View attachment 115330

WeirdWolf · Nov 19, 2010

Is there no fix for this?

CarlTR6 · Nov 19, 2010

Hi WeirdWolf; welcome to the forum. Sorry you are having a problem. Please read this thread, follow the instructions and post back. We will be glad to help you.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

WeirdWolf · Nov 21, 2010

Okay I did what the instructions told me to do.

Is Windows 7 . . .
- x86 (32-bit) or x64 ?
32
- the original installed OS on the system?
yes
- an OEM or full retail version?
win7 home premium retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)?
4 months
- What is the age of OS installation (have you re-installed the OS?)
yes I reinstalled it, because I hoped it would solve the error. around 1 week ago

Please tell me if I missed something. I hope you guys can help me.

CarlTR6 · Nov 21, 2010

Thanks for uploading the files. I have looked at all three dumps. All three blame Windows system driver, very unlikely to be the real cause, and two indicate video was involved. Since no direct cause is pointed out, you will have to troubleshoot. Note the usual causes below.

Error code 8E, KERNEL_MODE_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory.

Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

I recommend that while you are troubleshooting, you uninstall Avira. Avira is know to cause BSOD's on some Win 7 systems. After you get your system stable, you can try it again. Download and install Microsoft Security Essential in its place.

I also recommend that you uninstall TuneUP Utilities. Win 7 does not need any tuneup utility. Here is my "sermon" on this subject:

[FONT=&quot]Windows 7 is a totally different operating system than XP. Win 7 is not an evolution from XP. It is a totally new OS and even changed from Vista. Thus the wisdom we learned about XP - tweaking, cleaning, modifying for speed, etc - do not apply at all to Win 7. Forget that knowledge.

Windows is a closed source system. Developers of tuneup utilities and registry cleaners do not have the core code of Win 7 and are not working on definitive information, but rather they are going on past knowledge and experience, most of which is not applicable to Win 7. Automatic cleaners will usually have to do some guesswork.

There is almost no tweaking that can be done to Win 7 to speed it up. The system is designed to diagnose itself and take care of itself which it does remarkably well. Win 7 maintains itself and that includes the registry.

Tuneup utilities are pure snake oil. At best they do nothing except use resources. At worst, they can mess your system up, slowing it down, and even crash it. There is no tuneup utility out there anywhere that can speed Win 7 up and improve its performance, at least not at this time.

This isn't to say that the system does not need to be maintained. Uninstall programs that you don't use, delete unneeded and unnecessary files. Defrag your hard drive. But don't screw with the registry unless you are an in depth expert in the Win 7 registry.

We have seen the adverse effects of tuneup utilities and registry cleaners and registry defraggers in the Crashes and Debugging Section. Most of the time, the cure is a clean install. Using a program such as Ccleaner is fine to get rid of old and unnecessary files. A tuneup utility is not only unneeded, it can actually harm your system. Don't use them.[/FONT]

[FONT=&quot]
A third party antivirus can interfere with the video; but because two of the dumps indicated video problems, I suggest that you test your video card with Furmark following the instructions in this tutorial: [/FONT]http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html. Be sure to monitor your temps while testing. Post your results.

If Furmark does not show any errors, test your RAM with Memtest following the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Let Memtest run for at least 7 passes. This will take 6-8 hours. Post your results.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82806000 PsLoadedModuleList = 0x8294e810
Debug session time: Wed Nov 17 15:08:17.762 2010 (GMT-5)
System Uptime: 0 days 0:34:53.432
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {80000003, 82c1bccb, 8d752ba4, 0}

Probably caused by : ntkrpamp.exe ( nt!KiInterruptDispatch+c8 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: 80000003, The exception code that was not handled
Arg2: 82c1bccb, The address that the exception occurred at
Arg3: 8d752ba4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP: 
hal!HalEndSystemInterrupt+6f
82c1bccb 5d              pop     ebp

TRAP_FRAME:  8d752ba4 -- (.trap 0xffffffff8d752ba4)
ErrCode = 00000000
eax=8284d054 ebx=8d752d20 ecx=8d752c28 edx=904223f6 esi=85ec6fd0 edi=f17ae7d4
eip=82c1bccc esp=8d752c18 ebp=8d752c18 iopl=0         nv up di pl nz ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000016
hal!HalEndSystemInterrupt+0x70:
82c1bccc c20800          ret     8
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82845828 to 82c1bccc

STACK_TEXT:  
8d752c18 82845828 00000002 000000b0 8d752d20 hal!HalEndSystemInterrupt+0x70
8d752c18 904223f6 00000002 000000b0 8d752d20 nt!KiInterruptDispatch+0xc8
8d752c98 8288b6b5 87338710 8d73b800 8d736000 amdppm!C1Halt+0x4
8d752d20 8286e00d 00000000 0000000e 00000000 nt!PoIdle+0x538
8d752d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInterruptDispatch+c8
82845828 e92b460000      jmp     nt!KiExceptionExit (82849e58)

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiInterruptDispatch+c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

FAILURE_BUCKET_ID:  0x8E_nt!KiInterruptDispatch+c8

BUCKET_ID:  0x8E_nt!KiInterruptDispatch+c8

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

Debug session time: Thu Nov 18 15:29:59.974 2010 (GMT-5)
System Uptime: 0 days 0:41:54.254
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 1, 8281292e}

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveEntryList+39 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000008, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8281292e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829ae718
Unable to read MiSystemVaType memory at 8298e160
 00000008 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!KeReleaseQueuedSpinLock+2e
8281292e 83730403        xor     dword ptr [ebx+4],3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  8d7527a0 -- (.trap 0xffffffff8d7527a0)
ErrCode = 00000002
eax=86d0c1bc ebx=00000004 ecx=00000001 edx=00000002 esi=86d0c008 edi=86b25c74
eip=8281292e esp=8d752814 ebp=8d75282c iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
hal!KeReleaseQueuedSpinLock+0x2e:
8281292e 83730403        xor     dword ptr [ebx+4],3  ds:0023:00000008=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8281292e to 8288c82b

STACK_TEXT:  
8d7527a0 8281292e badb0d00 00000002 00000000 nt!KiTrap0E+0x2cf
8d752814 9135fb4d 8578cd0c 00000000 86b25c76 hal!KeReleaseQueuedSpinLock+0x2e
8d75282c 91358df1 86b25c74 8578cd0c 86d0c1bc dxgmms1!VidSchiInterlockedRemoveEntryList+0x39
8d75284c 9135dd48 86d0c008 8578cd08 86b25788 dxgmms1!VidSchiFreeQueuePacket+0x4f
8d75289c 9135dd77 0278cd08 8d7528ec 9135f35c dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x48e
8d7528a8 9135f35c 8578cd08 86b32000 86b33090 dxgmms1!VidSchiProcessCompletedQueuePacket+0xd
8d7528ec 9135f451 86b25788 86b33090 00000000 dxgmms1!VidSchiProcessDpcCompletedPacket+0x3e4
8d752908 9135f51e 86b25788 86b27000 86b25788 dxgmms1!VidSchiProcessDpcDmaPacket+0xc5
8d752920 9135f832 86b27000 00000001 86253920 dxgmms1!VidSchDdiNotifyDpcWorker+0xb2
8d752944 9129cbf5 86253920 8d752964 9129ccc4 dxgmms1!VidSchDdiNotifyDpc+0x78
WARNING: Stack unwind information not available. Following frames may be wrong.
8d752950 9129ccc4 85ef2fd0 86253920 00000000 dxgkrnl+0x1bf5
8d752964 9021cf87 86253920 00000000 86b98f00 dxgkrnl+0x1cc4
8d752978 90c205d7 86253920 8d752990 90c20061 atikmpag+0x3f87
8d752984 90c20061 60000400 8d7529a0 90c2035b atikmdag+0x185d7
8d752990 90c2035b 85197100 60000400 8d7529b0 atikmdag+0x18061
8d7529a0 90c2befc 85197100 8d752a7c 8d752a00 atikmdag+0x1835b
8d7529b0 90c88bcc 86251000 8d7529c0 00000040 atikmdag+0x23efc
8d752a00 90c8d823 86b7c000 90c20324 85197100 atikmdag+0x80bcc
8d752ac4 90c8d96d 86b7c000 86b89df4 00000001 atikmdag+0x85823
8d752b0c 90c8de1e 00000001 86b89df4 86b7c000 atikmdag+0x8596d
8d752b70 90c8dfef 86b7c000 86b89df4 00000001 atikmdag+0x85e1e
8d752bd8 90c8c904 86b7c000 86b89df4 00000001 atikmdag+0x85fef
8d752bfc 90c8cc3d 86b7c000 8d752c10 86b7c000 atikmdag+0x84904
8d752c28 90c87d42 86b7c000 863d18c0 8d752c48 atikmdag+0x84c3d
8d752c38 90c20d4d 86b7c000 862539d8 8d752c58 atikmdag+0x7fd42
8d752c48 9021d62f 863d18c0 8638e0e0 8d752c78 atikmdag+0x18d4d
8d752c58 9129c8c1 863d18c0 86253d10 8d73b884 atikmpag+0x462f
8d752c78 828ae3b5 86253d10 86253920 00000000 dxgkrnl+0x18c1
8d752cd4 828ae218 8d736120 8d73b800 00000000 nt!KiExecuteAllDpcs+0xf9
8d752d20 828ae038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
8d752d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiInterlockedRemoveEntryList+39
9135fb4d 8ac3            mov     al,bl

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VidSchiInterlockedRemoveEntryList+39

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc265

FAILURE_BUCKET_ID:  0xA_dxgmms1!VidSchiInterlockedRemoveEntryList+39

BUCKET_ID:  0xA_dxgmms1!VidSchiInterlockedRemoveEntryList+39

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

Debug session time: Sun Nov 21 08:11:05.722 2010 (GMT-5)
System Uptime: 0 days 2:28:39.061
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {aa5e5118, 1c, 1, 828974a2}

Probably caused by : amdppm.sys ( amdppm!C1Halt+4 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: aa5e5118, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 828974a2, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82981718
Unable to read MiSystemVaType memory at 829611e0
 aa5e5118 

CURRENT_IRQL:  1c

FAULTING_IP: 
nt!KeUpdateRunTime+5
828974a2 83e4f8          and     esp,0FFFFFFF8h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  8d71cba4 -- (.trap 0xffffffff8d71cba4)
ErrCode = 00000002
eax=00009e01 ebx=8d71cd20 ecx=8d71cc28 edx=00000002 esi=212f42bb edi=8fa013f6
eip=828974a2 esp=8d71cc18 ebp=8d71cc18 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!KeUpdateRunTime+0x5:
828974a2 83e4f8          and     esp,0FFFFFFF8h
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828974a2 to 8285dc3b

STACK_TEXT:  
8d71cba4 828974a2 badb0d00 00000002 00000000 nt!KiTrap0E+0x2cf
8d71cc18 82c2c430 00000002 000000d1 8d71cd20 nt!KeUpdateRunTime+0x5
8d71cc18 8fa013f6 00000002 000000d1 8d71cd20 hal!HalpClockInterruptPn+0x158
8d71cc98 828a000a 8535f278 8d705800 8d700000 amdppm!C1Halt+0x4
8d71cd20 828942cd 00000000 0000000e 00000000 nt!PoIdle+0x524
8d71cd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
amdppm!C1Halt+4
8fa013f6 c3              ret

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  amdppm!C1Halt+4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: amdppm

IMAGE_NAME:  amdppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf07

FAILURE_BUCKET_ID:  0xA_amdppm!C1Halt+4

BUCKET_ID:  0xA_amdppm!C1Halt+4

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

2: kd> lmtsmn
start    end        module name
82fab000 82ff3000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8fa2f000 8fa89000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
906c5000 906d7000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
8fa00000 8fa11000   amdppm   amdppm.sys   Mon Jul 13 19:11:03 2009 (4A5BBF07)
8b4f9000 8b502000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
98ad7000 98ae0000   asyncmac asyncmac.sys Mon Jul 13 19:54:46 2009 (4A5BC946)
8b4cd000 8b4d6000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b4d6000 8b4f9000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
8fa11000 8fa2e000   AtihdW73 AtihdW73.sys Fri Sep 24 01:43:53 2010 (4C9C3A99)
90c36000 912c9000   atikmdag atikmdag.sys Tue Oct 26 22:26:21 2010 (4CC78DCD)
90618000 90655000   atikmpag atikmpag.sys Tue Oct 26 22:14:03 2010 (4CC78AEB)
9693c000 96951000   avgntflt avgntflt.sys Fri May 07 08:28:31 2010 (4BE4076F)
8fbb9000 8fbdc000   avipbb   avipbb.sys   Thu May 27 10:11:26 2010 (4BFE7D8E)
8bb66000 8bb6d000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
8fbab000 8fbb9000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
82e37000 82e3f000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
82099000 820b2000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
974e0000 974fe000   cdd      cdd.dll      unavailable (00000000)
8bb40000 8bb5f000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
82e81000 82f2c000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8bae9000 8bb0e000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
82e3f000 82e81000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8b777000 8b7d4000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
906b8000 906c5000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
968b2000 968bf000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8fb93000 8fbab000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
8fb87000 8fb93000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
8bad8000 8bae9000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
9683f000 96858000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
968ca000 968d3000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
968bf000 968ca000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
968d3000 968e4000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
968a8000 968b2000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
912c9000 91380000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1)
91380000 913b9000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
8b536000 8b547000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8b502000 8b536000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8b7e2000 8b7eb000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8baa6000 8bad8000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
8b9ce000 8b9ff000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
82c29000 82c60000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
913b9000 913d8000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
96858000 968a8000   HdAudio  HdAudio.sys  Mon Jul 13 19:51:46 2009 (4A5BC892)
968fa000 9690d000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
9690d000 96913480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
968ef000 968fa000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868)
82014000 82099000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
8ba9e000 8baa6000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
90c19000 90c31000   i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B)
913f2000 913ff000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
80bb6000 80bbe000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
9076f000 907a3000   ks       ks.sys       Wed Mar 03 22:57:52 2010 (4B8F2FC0)
8b764000 8b777000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8b860000 8b885000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
913d8000 913e8000   L1E62x86 L1E62x86.sys Sun Mar 28 22:08:36 2010 (4BB00BA4)
9696b000 9697b000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
96921000 9693c000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
82e1b000 82e26000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 19:13:13 2009 (4A5BBF89)
968e4000 968ef000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
90762000 9076f000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
96916000 96921000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8b4b7000 8b4cd000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
820b2000 820c4000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
820c4000 820e7000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
820e7000 82122000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
82122000 8213d000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
8bbbf000 8bbca000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
82e00000 82e08000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8b739000 8b764000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8fb7d000 8fb87000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
8ba8e000 8ba9e000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8b547000 8b5fe000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
906ef000 906fa000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
906fa000 9071c000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
90600000 90611000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
8fae1000 8faef000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
8fa89000 8fabb000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
8b822000 8b860000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
8bbca000 8bbd8000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
8fb73000 8fb7d000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
82818000 82c29000   nt       ntkrpamp.exe Sat Jun 19 00:01:36 2010 (4C1C4120)
8b60a000 8b739000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8bb5f000 8bb66000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
8fac2000 8fae1000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
906a0000 906b8000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E)
8b436000 8b447000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
8213d000 82144000   parvdm   parvdm.sys   Mon Jul 13 19:45:29 2009 (4A5BC719)
8b401000 8b42b000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8b4a2000 8b4a9000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
8b4a9000 8b4b7000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b7d4000 8b7e2000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
82144000 821db000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
96810000 9683f000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
82e26000 82e37000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
906d7000 906ef000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
9071c000 90734000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
90734000 9074b000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
9074b000 90762000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
8fb32000 8fb73000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
8bba7000 8bbaf000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8bbaf000 8bbb7000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8bbb7000 8bbbf000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8ba61000 8ba8e000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
9697b000 9698e000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
821db000 821e5000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
90c0f000 90c19000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
8faef000 8fb09000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
8ba59000 8ba61000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
98a1b000 98a6c000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
969af000 969fe000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
9698e000 969af000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
8fb2c000 8fb31a00   ssmdrv   ssmdrv.sys   Tue May 05 06:05:18 2009 (4A000F5E)
90c31000 90c32380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8b885000 8b9ce000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
821e5000 821f2000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
8bbef000 8bbfa000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
8bbd8000 8bbef000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
8fb1c000 8fb2c000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
974b0000 974b9000   TSDDD    TSDDD.dll    unavailable (00000000)
98a6c000 98a6cd00   TuneUpUtilitiesDriver32 TuneUpUtilitiesDriver32.sys Thu Sep 17 07:54:55 2009 (4AB2238F)
8fbdc000 8fbfd000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
907a3000 907b1000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
96914000 96915700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
90c00000 90c0f000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
907b1000 907f5000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
913e8000 913f2000   usbohci  usbohci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
90655000 906a0000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
8b42b000 8b436000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8bb6d000 8bb79000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
8bb79000 8bb9a000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
8b447000 8b457000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8b457000 8b4a2000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8ba1a000 8ba59000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8fb09000 8fb1c000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
8bb9a000 8bba7000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
82f2c000 82f9d000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
82f9d000 82fab000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8fabb000 8fac2000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
97250000 9749b000   win32k   win32k.sys   unavailable (00000000)
82ff3000 82ffc000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
96951000 9696b000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)

Unloaded modules:
98a6d000 98ad7000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8bb0e000 8bb1b000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8bb1b000 8bb26000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8bb26000 8bb2f000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8bb2f000 8bb40000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

[FONT=&quot]

[/FONT]

WeirdWolf · Nov 21, 2010

Thanks for the reply, I will try these things tomorrow and I will write if this problem was solved or not. Though I don't get this bsod every day, so it may take soem time.

Do you think that installing vista would help? I maybe could rent it from a friend, because I heared that you can install it on a laptop and a pc at the same time.

CarlTR6 · Nov 21, 2010

Very good, please update us when you can. We will be here. I really can't tell you about Vista I came to Win 7 directly from XP and skipped Vista.

WeirdWolf · Nov 26, 2010

Got a new crash. Did everything I could, don't know if this is a new problem... :cry:

WeirdWolf · Nov 26, 2010

Forgot the ram is okay, the benchmarks and stresstest of the card also work. I also changed the mouse and the keyboard and deinstalled all unnecessary programs. Like I said it only happens when I play, not when I surf in the internet or write something.

WeirdWolf · Nov 26, 2010

Would someone recomment me installing/getting vista?

CarlTR6 · Nov 26, 2010

We need that actual dump. That was only a text file.

WeirdWolf · Nov 27, 2010

Sorry here is the real dump file. I also added something from "system information" it says conflicts...
Thanks for your help.

CarlTR6 · Nov 27, 2010

Doe you get the BSOD's when you play any game or mainly when you play Starcraft? Your dump indicates SC2.exe, Starcraft, triggered the crash; but the dump blames hardware as the cause. Is your Starcraft a cracked copy? If so uninstall it; the crack for Starcraft creates problems.

Error code 8E, KERNEL_MODE_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20738.x86fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0x82a4b000 PsLoadedModuleList = 0x82b94890
Debug session time: Fri Nov 26 11:15:50.362 2010 (GMT-5)
System Uptime: 0 days 1:13:49.032
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 82ac8f37, 807e4edc, 0}

Probably caused by : hardware ( nt!KiTimerExpiration+45 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: 82ac8f37, The address that the exception occurred at
Arg3: 807e4edc, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP: 
nt!KiTimerExpiration+45
82ac8f37 df              ???

TRAP_FRAME:  807e4edc -- (.trap 0xffffffff807e4edc)
ErrCode = 00000000
eax=000400d2 ebx=00000808 ecx=807c5a54 edx=00000000 esi=807c4120 edi=00000000
eip=82ac8f37 esp=807e4f50 ebp=807e4fac iopl=0         nv up di ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010086
nt!KiTimerExpiration+0x45:
82ac8f37 df              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  SC2.exe

CURRENT_IRQL:  2

MISALIGNED_IP: 
nt!KiTimerExpiration+45
82ac8f37 df              ???

LAST_CONTROL_TRANSFER:  from 82ac74ce to 82ac8f37

FAILED_INSTRUCTION_ADDRESS: 
nt!KiTimerExpiration+45
82ac8f37 df              ???

STACK_TEXT:  
807e4fac 82ac74ce 00045506 a0cbfd34 00000000 nt!KiTimerExpiration+0x45
807e4ff4 82ac6c9c a0cbfce4 00000000 00000000 nt!KiRetireDpcList+0xcb
807e4ff8 a0cbfce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
82ac6c9c 00000000 0000001a 00d6850f bb830000 0xa0cbfce4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+45
82ac8f37 df              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiTimerExpiration+45

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

I see that you have not uninstalled Avira. Avira is known to cause BSOD's on some Win 7 systems and one of the Avira drivers is outdated. Completely uninstall Avira. Download and use Revo Uninstaller (free). Download and install Microsoft Security Essentials in place of Avira and make sure Windows Firewall is turned on. Here is the outdated Avira driver:

ssmdrv.sys Tue May 05 06:05:18 2009 - ssmdrv.sys - AVIRA SnapShot Driver

At this point, I do not see a need to install Vista.

WeirdWolf · Nov 27, 2010

Okay deinstalled every remaining fragments of avir now and I installed win7 64bit (used win7 32 before). I still got a crash. I did everything I could do, I also installed starcraft2 with another retail copy of my friend this time. There is nothing on this windows aside from sc2 winrar and it still crashes. This is very frustating I cannot count the hours I wasted trying to solve this problem, I am about to throw this "new" pc out of the window. Starcraft2 worked on this pc for 3 months and suddenly the crashes started.
I did memtest and prime95 again without any errors. Do you think it is a hardware problem, what could be broken? I already went to the shop a few weeks ago they tested some benchmarks and said they couldn't find anything.

I have no other games aside from starcraft2 and starcraft2 is pretty pcfriendly/polished and like I said it worked for 3 months.

PS: the pc seems a little bit louder, but that could just be my immagination... the temerature is okay though.

Here is the first crash I got from win7 64, it looks a little bit different. I was never so mad system like I am now!:devil:

CarlTR6 · Nov 27, 2010

Error code, UNEXPECTED_KERNEL_MODE_TRAP. Usual causes: Memory corruption, Hardware (memory in particular), Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02859000 PsLoadedModuleList = 0xfffff800`02a96e50
Debug session time: Sat Nov 27 14:36:35.462 2010 (GMT-5)
System Uptime: 0 days 1:23:24.303
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff800028d7b9c}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+38c659 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff800028d7b9c

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SC2.exe

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff800028ca469 to fffff800028caf00

STACK_TEXT:  
fffff880`02f69ce8 fffff800`028ca469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02f69cf0 fffff800`028c8932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f69e30 fffff800`028d7b9c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`05ff3ff0 fffff880`04b8e659 : fffff880`04bc4308 fffff8a0`08afeb68 fffffa80`03d11040 fffffa80`047a8010 : nt!KiSecondaryClockInterrupt+0x12c
fffff880`05ff4188 fffff880`04bc4308 : fffff8a0`08afeb68 fffffa80`03d11040 fffffa80`047a8010 fffff880`05ff4430 : atikmdag+0x38c659
fffff880`05ff4190 fffff8a0`08afeb68 : fffffa80`03d11040 fffffa80`047a8010 fffff880`05ff4430 fffffa80`047a8010 : atikmdag+0x3c2308
fffff880`05ff4198 fffffa80`03d11040 : fffffa80`047a8010 fffff880`05ff4430 fffffa80`047a8010 fffff880`04bc4986 : 0xfffff8a0`08afeb68
fffff880`05ff41a0 fffffa80`047a8010 : fffff880`05ff4430 fffffa80`047a8010 fffff880`04bc4986 fffffa80`04093988 : 0xfffffa80`03d11040
fffff880`05ff41a8 fffff880`05ff4430 : fffffa80`047a8010 fffff880`04bc4986 fffffa80`04093988 0000000f`11628000 : 0xfffffa80`047a8010
fffff880`05ff41b0 fffffa80`047a8010 : fffff880`04bc4986 fffffa80`04093988 0000000f`11628000 fffff8a0`00aee540 : 0xfffff880`05ff4430
fffff880`05ff41b8 fffff880`04bc4986 : fffffa80`04093988 0000000f`11628000 fffff8a0`00aee540 fffff880`04cefb48 : 0xfffffa80`047a8010
fffff880`05ff41c0 fffffa80`04093988 : 0000000f`11628000 fffff8a0`00aee540 fffff880`04cefb48 000118d0`000004fe : atikmdag+0x3c2986
fffff880`05ff41c8 0000000f`11628000 : fffff8a0`00aee540 fffff880`04cefb48 000118d0`000004fe fffffa80`039f3078 : 0xfffffa80`04093988
fffff880`05ff41d0 fffff8a0`00aee540 : fffff880`04cefb48 000118d0`000004fe fffffa80`039f3078 fffff880`04cefb48 : 0xf`11628000
fffff880`05ff41d8 fffff880`04cefb48 : 000118d0`000004fe fffffa80`039f3078 fffff880`04cefb48 fffff880`07120000 : 0xfffff8a0`00aee540
fffff880`05ff41e0 000118d0`000004fe : fffffa80`039f3078 fffff880`04cefb48 fffff880`07120000 fffffa80`047a8010 : atikmdag+0x4edb48
fffff880`05ff41e8 fffffa80`039f3078 : fffff880`04cefb48 fffff880`07120000 fffffa80`047a8010 fffffa80`04093958 : 0x118d0`000004fe
fffff880`05ff41f0 fffff880`04cefb48 : fffff880`07120000 fffffa80`047a8010 fffffa80`04093958 fffff8a0`08afeb68 : 0xfffffa80`039f3078
fffff880`05ff41f8 fffff880`07120000 : fffffa80`047a8010 fffffa80`04093958 fffff8a0`08afeb68 fffff8a0`00aee540 : atikmdag+0x4edb48
fffff880`05ff4200 fffffa80`047a8010 : fffffa80`04093958 fffff8a0`08afeb68 fffff8a0`00aee540 00000000`00000000 : 0xfffff880`07120000
fffff880`05ff4208 fffffa80`04093958 : fffff8a0`08afeb68 fffff8a0`00aee540 00000000`00000000 fffffa80`04093040 : 0xfffffa80`047a8010
fffff880`05ff4210 fffff8a0`08afeb68 : fffff8a0`00aee540 00000000`00000000 fffffa80`04093040 fffff800`02a59730 : 0xfffffa80`04093958
fffff880`05ff4218 fffff8a0`00aee540 : 00000000`00000000 fffffa80`04093040 fffff800`02a59730 fffff880`02f63180 : 0xfffff8a0`08afeb68
fffff880`05ff4220 00000000`00000000 : fffffa80`04093040 fffff800`02a59730 fffff880`02f63180 00000000`00000001 : 0xfffff8a0`00aee540


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+38c659
fffff880`04b8e659 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  atikmdag+38c659

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc78ea1

FAILURE_BUCKET_ID:  X64_0x7f_8_atikmdag+38c659

BUCKET_ID:  X64_0x7f_8_atikmdag+38c659

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

I see one out of date driver.

L1E62x64.sys Thu Jun 11 02:45:22 2009 - Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20) OEM - none at http://www.atheros.com/pt/index.html

Do you use Ethernet or Wireless? If you use wireless, you can rename this driver from .sys to .old. Reboot and it will not load. Navigate to C:\Windows\System32\Drivers and locate L1E62x64.sys. If you use Ethernet, you may have to upgrade to a new Ethernet Adapter.

BSOD (halmacpi.dll the cause?)

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer