Kernel-Power Event 41 (random restarts)

Hi,

I have a computer which is now almost a year old install but to tell the truth it has never functioned really well. First I had a lot of problems where many seemed to be caused by bad firmware on my OCZ SSD that I use for windows 7 and applications. However I still have some problems which currently manifests in two ways:
1) Random Kernel Power Event 41 (Unexpected shutdowns)
2) Frequent application crash when my son is playing LEGO Indiana Jones 2

I started to browse this forum for ideas on how to find a solution to this problem and in one of the Kernel Power Event threads I read that it could be a good idea to run the Verifier.exe tool to cause more BSODs instead of just random restarts. This seemed actually to work well so after restarting the computer with these new settings I got two BSODs in a short time just when I was running the SF Diagnostic tool.

For some reason however the Diagnostic tool fails (without error message!) to save the folder to my desktop. Is this a known issue and if this does not work can somebody list the location and filenames for manually collection the logs to a zip for upload? (I saw that a lot of files were created because when I tried to run the tool again - thinking that it failed somehow - I was asked if I wanted to overwrite a bunch of text files).

Thanks a lot for any advice!

A quick bump, for the last part of my OP. Since the SF Diagnostic Tool failed in zipping the log files, can somebody please specify the location of the log files that the SF_XXX.zip contains so that I can add the relevant logs to this post?

Thanks.

Added all the logs I found SF to collect to the first post. This includes the minidump from the BSOD which happened as soon as I switched on Verifier.exe (I did not get BSOD's without Verifier.exe though)

Please is there someone who can help me take a look at these?

Welcome to SevenForums. Sorry for the late reply.

With verifier enabled it looks like very old ATI drivers are the cause of the BSOD.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88004b21050, fffff8800a151530, 0}

*** 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+b5050 )

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

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

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

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


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

FAULTING_IP: 
atikmdag+b5050
fffff880`04b21050 488911          mov     qword ptr [rcx],rdx

CONTEXT:  fffff8800a151530 -- (.cxr 0xfffff8800a151530)
rax=0000000000000000 rbx=0000000000000250 rcx=0000000000000000
rdx=0000000000000000 rsi=fffff98024f2eb40 rdi=0000000000000000
rip=fffff88004b21050 rsp=fffff8800a151f18 rbp=0000000000000000
 r8=0000000000000010  r9=0000000000000009 r10=fffff8800a152a60
r11=fffff8800a151e80 r12=0000000000000000 r13=fffff98022ffe740
r14=fffff98022ffe760 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
atikmdag+0xb5050:
fffff880`04b21050 488911          mov     qword ptr [rcx],rdx ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88004e276e5 to fffff88004b21050

STACK_TEXT:  
fffff880`0a151f18 fffff880`04e276e5 : 00000000`00000003 fffffa80`0722a098 00000000`00000000 00000000`00000000 : atikmdag+0xb5050
fffff880`0a151f20 00000000`00000003 : fffffa80`0722a098 00000000`00000000 00000000`00000000 fffff980`24f2eb40 : atikmdag+0x3bb6e5
fffff880`0a151f28 fffffa80`0722a098 : 00000000`00000000 00000000`00000000 fffff980`24f2eb40 fffff880`04de4f8b : 0x3
fffff880`0a151f30 00000000`00000000 : 00000000`00000000 fffff980`24f2eb40 fffff880`04de4f8b fffff880`0a152320 : 0xfffffa80`0722a098


FOLLOWUP_IP: 
atikmdag+b5050
fffff880`04b21050 488911          mov     qword ptr [rcx],rdx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+b5050

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ddc6c20

STACK_COMMAND:  .cxr 0xfffff8800a151530 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_VRF_atikmdag+b5050

BUCKET_ID:  X64_0x3B_VRF_atikmdag+b5050

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

0: kd> lmvm atikmdag
start             end                 module name
fffff880`04a6c000 fffff880`053ab000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Wed May 25 08:40:32 2011 (4DDC6C20)
    CheckSum:         008F5471
    ImageSize:        0093F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to Clean Left Over Driver Files with Driver Sweeper

• Drivers - Clean Left over Files after Uninstalling

• AMD Driver Autodetect

I would check for overheating issues, make sure there is no dust inside the case.
For monitoring the heat/celsius of the system, use Speccy or HWMonitor:

• Speccy - System Information - Free Download
• CPUID - System & hardware benchmark, monitoring, reporting

BTW, Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

Perform a System File Check:

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it:

• Disk Check

You're welcome :)

And thanks for the nfo files.

writhziden said:

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Code:

Modell	OCZ-VERTEX3 ATA Device

Here are some links that may help:

• http://www.ocztechnology.com/files/s...s_consumer.pdf
• http://www.ocztechnology.com/files/s...te%20Guide.pdf

Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

fnokke said:

WIth Kernel-41 Event I also first thought it might be related to temperature and installed HWMonitor, but in all cases of failures I found the graphic card to be only about 77 deg celsius and the warmest CPU about 58 deg celsius, so I discarded this idea. Do you agree?

the CPU temp is fine but I have doubts on the GPU temp. The ASUS site has no max temp listed, but 77C is hot for a passively cooled GPU, in my opinion. You might check for and clean out dust on the GPU cooling fins.

The dump is silent about anything..:

Code:

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

Use !analyze -v to get detailed debugging information.

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

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

A stop 7F's usual causes are:

Code:

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP 

Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking 
failure, 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

Have you tried memtest?