Event ID 41 Kernal Power error cause BSOD's

chipp300 · 20 Oct 2010

Hi eveyone! This is my first post here and recently registered. Anyways, I've noticed earlier posts here regarding this event ID 41 issue and I figured I would post here because I'm basically unsure of what else to do and the community here seems very helpful. I recently bought a system with all the components pre-installed below:

MOBO : P7P55D-3
OS: WINDOWS 7 Ultimate x64
Memory : 8 GIGS DDR3
Vid card: Nvidia GTX 470
CPU: Intel Core i7 860
Also, the os is OEM and not even a day old

I haven't had this pc for no more than 2 days (as of this writing) and already I'm getting BSOD's! Basically, the system can run fine for roughly 2 hours and all of a sudden, the system flips out, BSOD appears for about 5 seconds, and forces my comp to restart. I don't believe this error is hardware related because I've opened up the case and made sure there were no lose wires, cooling appears to be normal, and I don't hear the tower making any unusal / loud noises. On my end, I have deleted and re-installed various drivers (sound, video, mobo, etc.) and even re-installed the OS and still no luck. When I check the event log, I see in the last 24 hours that Event ID 41 Kernal Power error being the issue and the log states the following:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

-System
-Provider[ Name] Microsoft-Windows-Kernel-Power[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID41Version2Level1Task63Opcode0Keywords0x8000000000000002-TimeCreated[ SystemTime] 2010-10-20T22:30:40.548015900Z
EventRecordID2247Correlation-Execution[ ProcessID] 4[ ThreadID] 8
ChannelSystemComputerch1pp-PC-Security[ UserID] S-1-5-18

-EventData
BugcheckCode209BugcheckParameter10xffffea003a1a47ceBugcheckParameter20x5BugcheckParameter30x1BugcheckParameter40xfffff88010bbe8dcSleepInProgressfalsePowerButtonTimestamp0

So I'm at a loss of what else to do, besides shipping the computer back and having them fix it--but I would much rather not go that route. I tried to follow the posting rules the best I could and provided the dump log in a .rar file as the attachment. The System Health Report did not work for me so I hope that I provided the neccessary info needed to help remedy my problem.

Thanks!

zigzag3143 · 20 Oct 2010

chipp300 said:

Hi eveyone! This is my first post here and recently registered. Anyways, I've noticed earlier posts here regarding this event ID 41 issue and I figured I would post here because I'm basically unsure of what else to do and the community here seems very helpful. I recently bought a system with all the components pre-installed below:

MOBO : P7P55D-3
OS: WINDOWS 7 Ultimate x64
Memory : 8 GIGS DDR3
Vid card: Nvidia GTX 470
CPU: Intel Core i7 860
Also, the os is OEM and not even a day old

I haven't had this pc for no more than 2 days (as of this writing) and already I'm getting BSOD's! Basically, the system can run fine for roughly 2 hours and all of a sudden, the system flips out, BSOD appears for about 5 seconds, and forces my comp to restart. I don't believe this error is hardware related because I've opened up the case and made sure there were no lose wires, cooling appears to be normal, and I don't hear the tower making any unusal / loud noises. On my end, I have deleted and re-installed various drivers (sound, video, mobo, etc.) and even re-installed the OS and still no luck. When I check the event log, I see in the last 24 hours that Event ID 41 Kernal Power error being the issue and the log states the following:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

-System
-Provider[ Name] Microsoft-Windows-Kernel-Power[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID41Version2Level1Task63Opcode0Keywords0x8000000000000002-TimeCreated[ SystemTime] 2010-10-20T22:30:40.548015900Z
EventRecordID2247Correlation-Execution[ ProcessID] 4[ ThreadID] 8
ChannelSystemComputerch1pp-PC-Security[ UserID] S-1-5-18

-EventData
BugcheckCode209BugcheckParameter10xffffea003a1a47ceBugcheckParameter20x5BugcheckParameter30x1BugcheckParameter40xfffff88010bbe8dcSleepInProgressfalsePowerButtonTimestamp0

So I'm at a loss of what else to do, besides shipping the computer back and having them fix it--but I would much rather not go that route. I tried to follow the posting rules the best I could and provided the dump log in a .rar file as the attachment. The System Health Report did not work for me so I hope that I provided the neccessary info needed to help remedy my problem.

Thanks!

These two crashes were caused by two different things. The first portcls.sys which is a sound driver, the second your video driver. Both show memory involvement.

I would
1-run memtest to test the memory
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

2-Update the sound and video drivers

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

3-run a system file check

SFC /SCANNOW Command - System File Checker

chipp300 · 20 Oct 2010

Thanks for the quick reply! I'm gonna perform those tasks and reply once I've finished. Thanks again!

chipp300 · 20 Oct 2010

Memtest shows no errors with the memory itself. As far as the drivers is concerned, I'm not 100% sure which ones to use for the creative x-fi titanium Fatility championship edition; seeings how the only one creative keeps directing me to is the pro series drivers... I assume both of these cards are practically identical wheras the champion version provides an I/O front panel (which only half works at the moment). Are there any other drivers that I could use instead of the ones that creative provides?

chipp300 · 20 Oct 2010

Ok, I've done everyting you've told me to do and this is what I found:

- Memtest shows no errors whatsoever with the memory.
- Ran a systemfilecheck and found no errors there either.
- I used Guro3d's Driver Sweeper to uninstall every bit of drivers I had.
Including a realtek one (onboard) which I didn't even realize was on my system.
Tha could explain that portcls.sys file that was found in the dump file I posted earlier. Perhaps that was causing the 'clash' between the video card and soundcard drivers... Now everything is up-to-date including direct x 11.
- I did a very quick test with a game. Launched successfully and played flawlessly so that's a good sign. Since it crashed the last time I tried playing it.

All that's left now is to leave the pc running and see if it doesn't crash again--since these crashes take roughly 2 hours of up-time for the crashes to occur. Will update again if it has been completely resolved or not. Thanks for the help!

CarlTR6 · 21 Oct 2010

Good work and thanks for reporting back. I have my fingers crossed.

chipp300 · 21 Oct 2010

I have also been talking with users about this issue here:
Event ID 41 Kernal Power error cause BSOD's __

Despite my best efforts, the problem still persists. I have updated my BIOS as well but still no-go

. According to blue screen viewer, it was caused by something new and it's called tcpip.sys+ 3e190. I'm basically at a lose at this point and about ready to simply just ship it back and have them fix it instead (since my warranty will cover it) and maybe have them put another soundcard in as well. Anyways, I've posted the new dump file below and just wanted to thank eveyone again for all your help thus far. On my end, this is everything I've done so far:

-Ran a memtest and found no errors
-Performed a sfc / scanow which also found no errors
-Have uninstalled, reinstalled / updated my video / soundcard drivers to their most recent versions (that I can find anyways)
-have reinstalled the os with only the bare essentials and it still crashes
-updated my BIOS

I believe that's it. I've posted the dump log as an attached .rar file in the extension for further troubleshooting. Thanks again everyone for the help!

CarlTR6 · 21 Oct 2010

It is very unlikely that tcpip.sys caused the crash; it is an MS system driver. Something else caused tcpip.sys to crash. Reinstalling the OS to bare essentials and crashing points to a hardware problem. Can you run in the Safe mode without crashing?

The only out of date driver I see loaded on your system is this one.

AsUpIO.sys Sun Jul 05 22:21:38 2009 - AsUpIO.sys – Asus utility driver. ASUSTeK Computer Inc.-Support-. I think it is part of PCProbe.

If there is no update for this driver, first create a system restore point. Navigate to C:\Windows\System32\Drivers, locate this driver and rename it from .sys to .bak. Reboot. This will break the utility the drive belongs to. Let's see if it in interfering with tcpip.sys.

Test your CPU and your memory with Prime. Read this tutorial carefully.

https://www.sevenforums.com/tutorials...t-prime95.html

Run 3 separate tests, one on each of the setting (Blend, Small FFTs, Large FFTs). Post back with your results.

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a2e50
Debug session time: Wed Oct 20 18:29:16.965 2010 (GMT-4)
System Uptime: 0 days 1:48:37.027
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffea003a1a47ce, 5, 1, fffff88010bbe8dc}

Probably caused by : hardware ( portcls!CInterruptSync::`vector deleting destructor'+f8 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffea003a1a47ce, memory referenced
Arg2: 0000000000000005, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88010bbe8dc, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d0e0
 ffffea003a1a47ce 

CURRENT_IRQL:  5

FAULTING_IP: 
portcls!CInterruptSync::`vector deleting destructor'+f8
fffff880`10bbe8dc 01448ae6        add     dword ptr [rdx+rcx*4-1Ah],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880030b09e0 -- (.trap 0xfffff880030b09e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880030b0b98 rbx=0000000000000000 rcx=fffffa80085f7bf0
rdx=00000000189c57d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88010bbe8dc rsp=fffff880030b0b70 rbp=fffffa80085f7c30
 r8=fffff8800591e800  r9=0000000000000000 r10=fffffa800831bc80
r11=00000000129b25b5 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
portcls!CInterruptSync::`vector deleting destructor'+0xf8:
fffff880`10bbe8dc 01448ae6        add     dword ptr [rdx+rcx*4-1Ah],eax ds:26bf:ffffea00`3a1a4776=????????
Resetting default scope

MISALIGNED_IP: 
portcls!CInterruptSync::`vector deleting destructor'+f8
fffff880`10bbe8dc 01448ae6        add     dword ptr [rdx+rcx*4-1Ah],eax

LAST_CONTROL_TRANSFER:  from fffff80002ed4ca9 to fffff80002ed5740

STACK_TEXT:  
fffff880`030b0898 fffff800`02ed4ca9 : 00000000`0000000a ffffea00`3a1a47ce 00000000`00000005 00000000`00000001 : nt!KeBugCheckEx
fffff880`030b08a0 fffff800`02ed3920 : 00000000`04708000 fffffa80`08b80830 fffffa80`074c4000 fffffa80`08295650 : nt!KiBugCheckDispatch+0x69
fffff880`030b09e0 fffff880`10bbe8dc : 00000000`01770000 fffffa80`08ae4e68 fffffa80`08f7ff00 00000000`00000000 : nt!KiPageFault+0x260
fffff880`030b0b70 fffff800`02ed1339 : fffffa80`074c40c8 fffff880`030b0c70 fffffa80`074c40c0 00000000`00000000 : portcls!CInterruptSync::`vector deleting destructor'+0xf8
fffff880`030b0ba0 fffff800`02ed1118 : fffff880`03088180 fffff880`030b0c70 fffffa80`06e61660 00000000`7efad000 : nt!KiScanInterruptObjectList+0x69
fffff880`030b0bf0 fffff800`02eddec2 : fffff880`03088180 fffff880`00000002 00000000`00000002 fffff880`00000000 : nt!KiChainedDispatch+0x128
fffff880`030b0d80 00000000`00000000 : fffff880`030b1000 fffff880`030ab000 fffff880`030b0d40 00000000`00000000 : nt!KiIdleLoop+0x32


STACK_COMMAND:  kb

FOLLOWUP_IP: 
portcls!CInterruptSync::`vector deleting destructor'+f8
fffff880`10bbe8dc 01448ae6        add     dword ptr [rdx+rcx*4-1Ah],eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  portcls!CInterruptSync::`vector deleting destructor'+f8

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_portcls.sys

BUCKET_ID:  X64_IP_MISALIGNED_portcls.sys

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

Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e47e50
Debug session time: Wed Oct 20 12:47:55.606 2010 (GMT-4)
System Uptime: 0 days 0:00:22.668
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8880a99dff8, 2, 1, fffff88004904dc6}

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

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8880a99dff8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004904dc6, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb20e0
 fffff8880a99dff8 

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+f6dc6
fffff880`04904dc6 4c891cd0        mov     qword ptr [rax+rdx*8],r11

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880031217c0 -- (.trap 0xfffff880031217c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800a99e000 rbx=0000000000000000 rcx=fffffa800a4909a0
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004904dc6 rsp=fffff88003121950 rbp=0000000000000000
 r8=00001cff70fc2000  r9=00000000000000ff r10=0000000000000000
r11=00001cff70fc2000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nvlddmkm+0xf6dc6:
fffff880`04904dc6 4c891cd0        mov     qword ptr [rax+rdx*8],r11 ds:0030:fffff888`0a99dff8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c79ca9 to fffff80002c7a740

STACK_TEXT:  
fffff880`03121678 fffff800`02c79ca9 : 00000000`0000000a fffff888`0a99dff8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03121680 fffff800`02c78920 : 00000000`00000000 000000ff`70fc201c fffffa80`09ff1000 fffffa80`0a1618e4 : nt!KiBugCheckDispatch+0x69
fffff880`031217c0 fffff880`04904dc6 : 00000000`0000001f 00000000`00000000 fffff880`05377b00 fffff880`049ca0ca : nt!KiPageFault+0x260
fffff880`03121950 00000000`0000001f : 00000000`00000000 fffff880`05377b00 fffff880`049ca0ca 00000000`00000001 : nvlddmkm+0xf6dc6
fffff880`03121958 00000000`00000000 : fffff880`05377b00 fffff880`049ca0ca 00000000`00000001 fffff880`04904e42 : 0x1f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+f6dc6
fffff880`04904dc6 4c891cd0        mov     qword ptr [rax+rdx*8],r11

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+f6dc6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4caecb0c

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+f6dc6

BUCKET_ID:  X64_0xD1_nvlddmkm+f6dc6

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

Kernel base = 0xfffff800`02e4d000 PsLoadedModuleList = 0xfffff800`0308ae50
Debug session time: Thu Oct 21 09:47:11.807 2010 (GMT-4)
System Uptime: 0 days 0:01:23.868
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 : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

2: 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: 
+5aaf952f019fdf70
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002f8c3a8 -- (.exr 0xfffff88002f8c3a8)
ExceptionAddress: fffff80002ec8e20 (nt!KiProcessExpiredTimerList+0x0000000000000110)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f8c450 -- (.trap 0xfffff88002f8c450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa800aa0fb38
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec8e20 rsp=fffff88002f8c5e0 rbp=fffffa80090d0730
 r8=fffff88002f66301  r9=0000000000000002 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!KiProcessExpiredTimerList+0x110:
fffff800`02ec8e20 f00fba2f07      lock bts dword ptr [rdi],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002eb546e to fffff80002ebd710

STACK_TEXT:  
fffff880`02f8b498 fffff800`02eb546e : fffff880`00000008 fffff880`00000000 fffff880`02f8bc10 fffff800`02eea668 : nt!KeBugCheck
fffff880`02f8b4a0 fffff800`02ee340d : fffff800`030cbb7c fffff800`03005e84 fffff800`02e4d000 fffff880`02f8c3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8b4d0 fffff800`02eeaa90 : fffff800`0300cb14 fffff880`02f8b548 fffff880`02f8c3a8 fffff800`02e4d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8b500 fffff800`02ef79ef : fffff880`02f8c3a8 fffff880`02f8bc10 fffff880`00000000 00fffa80`0b2dd5f0 : nt!RtlDispatchException+0x410
fffff880`02f8bbe0 fffff800`02ebcd82 : fffff880`02f8c3a8 fffffa80`090d07c0 fffff880`02f8c450 00000000`00000000 : nt!KiDispatchException+0x16f
fffff880`02f8c270 fffff800`02ebb68a : 00000000`00000020 00000000`00000001 00000000`00000002 fffff800`02fafc24 : nt!KiExceptionDispatch+0xc2
fffff880`02f8c450 fffff800`02ec8e20 : fffffa80`0b2df120 fffffa80`0ac70168 fffffa80`0ac70168 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8c5e0 fffff800`02ec94be : 00000000`31fd5ad0 fffff880`02f8cc58 00000000`00001500 fffff880`02f66588 : nt!KiProcessExpiredTimerList+0x110
fffff880`02f8cc30 fffff800`02ec8cb7 : 00000000`0dca63c1 00000000`00001500 00000000`0dca6368 00000000`00000000 : nt!KiTimerExpiration+0x1be
fffff880`02f8ccd0 fffff800`02ec5eea : fffff880`02f64180 fffff880`02f6f0c0 fffff880`00000000 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff880`02f8cd80 00000000`00000000 : fffff880`02f8d000 fffff880`02f87000 fffff880`02f8cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02eb546e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

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

2: kd> lmtsmn
start             end                 module name
fffff880`04562000 fffff880`045a0000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00ec7000 fffff880`00f1e000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c5d000 fffff880`02ce7000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`045c4000 fffff880`045da000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`010a4000 fffff880`010af000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`045a0000 fffff880`045a8000   ASACPI   ASACPI.sys   Wed Jul 15 23:31:29 2009 (4A5E9F11)
fffff880`03d7f000 fffff880`03d85000   AsIO     AsIO.sys     Mon Aug 03 03:03:16 2009 (4A768BB4)
fffff880`03d79000 fffff880`03d7f000   AsUpIO   AsUpIO.sys   Sun Jul 05 22:21:38 2009 (4A515FB2)
fffff880`00de8000 fffff880`00df1000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0107a000 fffff880`010a4000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`01833000 fffff880`0183a000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03d68000 fffff880`03d79000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`063b4000 fffff880`063d2000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00690000 fffff960`006b7000   cdd      cdd.dll      unavailable (00000000)
fffff880`06e00000 fffff880`06e1d000   cdfs     cdfs.sys     Mon Jul 13 19:19:46 2009 (4A5BC112)
fffff880`01800000 fffff880`0182a000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00cbf000 fffff880`00d7f000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`0197b000 fffff880`019ab000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c61000 fffff880`00cbf000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0116d000 fffff880`011e0000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`045b4000 fffff880`045c4000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`06e1d000 fffff880`06e2b000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03cc7000 fffff880`03d4a000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`05d02000 fffff880`05d3f000   CT20XUT  CT20XUT.SYS  Wed Jul 07 09:44:15 2010 (4C3484AF)
fffff880`03c00000 fffff880`03ca8b80   ctaud2k  ctaud2k.sys  Wed Jul 07 09:42:14 2010 (4C348436)
fffff880`06e69000 fffff880`06fcd000   CTEXFIFX CTEXFIFX.SYS Wed Jul 07 09:44:03 2010 (4C3484A3)
fffff880`05ce6000 fffff880`05d02000   CTHWIUT  CTHWIUT.SYS  Wed Jul 07 09:44:19 2010 (4C3484B3)
fffff880`0449c000 fffff880`044cd000   ctoss2k  ctoss2k.sys  Wed Jul 07 09:38:24 2010 (4C348350)
fffff880`044cd000 fffff880`044d5000   ctprxy2k ctprxy2k.sys Wed Jul 07 09:42:17 2010 (4C348439)
fffff880`061ba000 fffff880`061f2000   ctsfm2k  ctsfm2k.sys  Wed Jul 07 09:38:10 2010 (4C348342)
fffff880`03d4a000 fffff880`03d68000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`02dc1000 fffff880`02dd0000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01965000 fffff880`0197b000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04256000 fffff880`04278000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`06e37000 fffff880`06e40000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`06e2b000 fffff880`06e37000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`06e40000 fffff880`06e53000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`06ff0000 fffff880`06ffc000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`0428d000 fffff880`04381000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04381000 fffff880`043c7000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`05c9c000 fffff880`05ce6000   emupia2k emupia2k.sys Wed Jul 07 09:38:03 2010 (4C34833B)
fffff880`010fb000 fffff880`0110f000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`010af000 fffff880`010fb000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0192b000 fffff880`01965000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`015b5000 fffff880`015ff000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`0602d000 fffff880`061ba000   ha20x22k ha20x22k.sys Wed Jul 07 09:41:25 2010 (4C348405)
fffff800`02e04000 fffff800`02e4d000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`043c7000 fffff880`043eb000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`05d5c000 fffff880`05d75000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`061f2000 fffff880`061fa080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`06e53000 fffff880`06e61000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`062ec000 fffff880`063b4000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`01922000 fffff880`0192b000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`03dab000 fffff880`03dc1000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00d7f000 fffff880`00d9f000   jraid    jraid.sys    Wed Oct 07 07:26:03 2009 (4ACC7ACB)
fffff880`02dd0000 fffff880`02ddf000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`05d82000 fffff880`05d90000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00ba0000 fffff800`00baa000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`04459000 fffff880`0449c000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`0158a000 fffff880`015b5000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`044d5000 fffff880`044da200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`05dc1000 fffff880`05dd6000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05d9e000 fffff880`05dc1000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c09000 fffff880`00c4d000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`05d90000 fffff880`05d9e000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`02ddf000 fffff880`02dee000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`05d75000 fffff880`05d82000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00dce000 fffff880`00de8000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`063d2000 fffff880`063ea000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`06200000 fffff880`0622d000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`0622d000 fffff880`0627b000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0627b000 fffff880`0629e000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`01898000 fffff880`018a3000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f27000 fffff880`00f31000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`0110f000 fffff880`0116d000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02db6000 fffff880`02dc1000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01910000 fffff880`01922000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01438000 fffff880`0152a000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04400000 fffff880`0440c000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`0440c000 fffff880`0443b000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`06017000 fffff880`0602c000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02d5b000 fffff880`02d6a000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02ce7000 fffff880`02d2c000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`0152a000 fffff880`0158a000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`018a3000 fffff880`018b4000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02c51000 fffff880`02c5d000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02e4d000 fffff800`03429000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01254000 fffff880`013f7000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`0182a000 fffff880`01833000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`06000000 fffff880`06017000   nusb3hub nusb3hub.sys Mon Oct 26 10:19:44 2009 (4AE5B000)
fffff880`044db000 fffff880`0450a000   nusb3xhc nusb3xhc.sys Mon Oct 26 10:19:48 2009 (4AE5B004)
fffff880`053fe000 fffff880`053ff180   nvBridge nvBridge.kmd Fri Oct 08 02:47:30 2010 (4CAEBE82)
fffff880`06fcd000 fffff880`06ff0000   nvhda64v nvhda64v.sys Mon Jun 21 18:07:25 2010 (4C1FE29D)
fffff880`0482c000 fffff880`053fd180   nvlddmkm nvlddmkm.sys Fri Oct 08 03:41:00 2010 (4CAECB0C)
fffff880`02d35000 fffff880`02d5b000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00f71000 fffff880`00f86000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f31000 fffff880`00f64000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00ff7000 fffff880`00ffe000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00e00000 fffff880`00e10000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`072fe000 fffff880`073a4000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`03dc1000 fffff880`03dfe000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c4d000 fffff880`00c61000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`045da000 fffff880`045fe000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0443b000 fffff880`04456000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04800000 fffff880`04821000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`03ca9000 fffff880`03cc3000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02c00000 fffff880`02c51000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`04278000 fffff880`04283000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`0187d000 fffff880`01886000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01886000 fffff880`0188f000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0188f000 fffff880`01898000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`018d6000 fffff880`01910000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`05dd6000 fffff880`05dee000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`0450c000 fffff880`04562000   Rt64win7 Rt64win7.sys Wed Jun 23 05:10:45 2010 (4C21CF95)
fffff880`00d9f000 fffff880`00dce000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`073a4000 fffff880`073af000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`045a8000 fffff880`045b4000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02d6a000 fffff880`02d87000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`01410000 fffff880`01418000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`07267000 fffff880`072fd000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`07200000 fffff880`07267000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`073af000 fffff880`073dc000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`04456000 fffff880`04457480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`073dc000 fffff880`073ee000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`019e1000 fffff880`019ee000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`018b4000 fffff880`018d2000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02da2000 fffff880`02db6000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00590000 fffff960`0059a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03d85000 fffff880`03dab000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`02dee000 fffff880`02e00000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`05d3f000 fffff880`05d5c000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`0450a000 fffff880`0450bf00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`043eb000 fffff880`043fc000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`05c42000 fffff880`05c9c000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04200000 fffff880`04256000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00f64000 fffff880`00f71000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`0183a000 fffff880`01848000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`01848000 fffff880`0186d000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`01400000 fffff880`01410000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00f86000 fffff880`00f9b000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f9b000 fffff880`00ff7000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01000000 fffff880`0104c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02d87000 fffff880`02da2000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`0186d000 fffff880`0187d000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e14000 fffff880`00eb8000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00eb8000 fffff880`00ec7000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02d2c000 fffff880`02d35000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00060000 fffff960`0036f000   win32k   win32k.sys   unavailable (00000000)
fffff880`00f1e000 fffff880`00f27000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`019ab000 fffff880`019b9000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`019b9000 fffff880`019c5000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`019c5000 fffff880`019ce000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`019ce000 fffff880`019e1000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

chipp300 · 21 Oct 2010

Alright fellas, I've decided to just "throw in the towel" and have them deal with this issue. I've done everyting that was suggested in this forum, and have had no luck. Really sucks too, considering that I really like Windows 7 and how smooth it runs, but I can't keep spending all this time trying to resolve an issue that's leaning more and more on the hardware side of things so I'm going to take advantage of my warranty and have the company replace any faulty components. Also, I'm attaching a letter / script for them to read as to what causes the crashes to happen and wanted to know what else I should include in it? What I mean is what other tests can I have these folks perform to insure that this problem never arises again for me?

CarlTR6 · 21 Oct 2010

I think you have made a wise decision since you are under warranty. The techs will probably run Memtest and Prime, also. They will probably run each for 24 hours. They will have other bench tests they can do, also, to check voltages and so forth. It is a good idea to give them as much information as possible especially what you were doing at the times of crashes. Please let us know what you find out.