Solved Kernel-Power Event 41 (random restarts)

[fnokke]

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!

 

[fnokke]

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.

 

[fnokke]

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?

 

[fnokke]

Bump. Please take a look at my logs! Many thanks.

 

[koolkat77]

Welcome to SevenForums. Sorry for the late reply.

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

[FONT="Courier New"][SIZE="3"]*******************************************************************************
*                                                                             *
*                        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 : [COLOR="Blue"]atikmdag.sys[/COLOR] ( 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:  [COLOR="blue"]dwm.exe[/COLOR]

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: [COLOR="blue"]atikmdag.sys[/COLOR]
    Timestamp:        [COLOR="blue"]Wed May 25 08:40:32 2011[/COLOR] (4DDC6C20)
    CheckSum:         008F5471
    ImageSize:        0093F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4[/SIZE][/FONT]

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

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

• 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 rb:
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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

• http://www.sevenforums.com/tutorials/433-disk-check.html

 

[fnokke]

Thanks a lot for your reply! I had no idea that I should search for drivers somewhere else than on the graphic card manufacturer (in this case ASUS hp for HD6450 1GB where I had the latest driver installed). Anyhow I have now sweeped the AMD display drivers and the reinstalled the latest recommended by amddriverdownloader. Hoping this may solve some problems!

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?

I have also run sfc and checkdisk which both came out completely clean.

I will now try for a while and see whether the graphics driver seems to have been the bottleneck, else I will activate Verifier again to see if I can cause new BSODs.

Thanks for now!

(Also attached new zip including the msinfo32 files)

 

[koolkat77]

You're welcome

And thanks for the nfo files.

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.

Modell	OCZ-VERTEX3 ATA Device

Here are some links that may help:

• http://www.ocztechnology.com/files/..._Update_Guide_10_02_2012_Windows_consumer.pdf
• http://www.ocztechnology.com/files/ssd_tools/OCZ SSD v1.7 Firmware Update Guide.pdf

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

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

 

[Britton30]

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.

 

[fnokke]

OK, so apparently it was not only the ati driver causing problems. After installing that I decided to give my son a new shot at playing his LEGO Indiana Jones 2. It did not take very long (perhaps 5-10 min) before the application crashed. I decided to give verifier a try again and it seemed actually not to cause any new BSODs, but after a while the computer hanged with a strange grainy nonsense graphic and a monotonic sound.

However since I was not getting BSODs anyway and I felt the system was getting a bit sluggish with verifier activated I decided to try to test the temp again with HWMonitor and deactivated verifier. At this point I sometimes got around 74 deg for graphics and upto almost 70 degrees for hottest CPU (but most often the CPU was around 55-60).

At any rate it was simply annoying trying to play the game so we gave that up and instead tried to watch some streaming media. After maybe 3 silverlight crashes in an hour the computer actually had two BSODs again blaming from what I can understand ntkrnlmp.exe ? (Attached minidump)

I have been a bit suspicious of my cooling as I did not get a new fan when I upgraded the MB, CPUs and graphics card ... in particular the old fan lacks the extra connector to hook in to get variable fan speed monitored by the MB, so instead I have it at fixed speed. I just want my computer to become stable and of course have no problem in buying a new fan with the extra connector, but I do not want to spend the money without knowing that it is a likely source of error ...

Thanks again for all the help!

 

[koolkat77]

The dump is silent about anything..:

*******************************************************************************
*                                                                             *
*                        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:

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?

 

[fnokke]

Thanks Koolkat,

I think I did a memtest in the past too but just to make sure I downloaded v4.2 and ran it overnight with 7 passes and no errors.

However, I also found that the minidump of the BSOD 20 min before the 7F I posted was different, maybe that can give some other clue to what is wrong with my system? Feels like I am running out of tests?

 

[koolkat77]

STOP 0x0000001A: MEMORY_MANAGEMENT  http://www.carrona.org/bsodindx.html#0x0000001A

Usual causes:  Device driver, memory, kernel

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff70001080000, cd24, 2a009a40fffffffe}

Probably caused by : dxgkrnl.sys ( dxgkrnl!memmove+154 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005002, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000cd24
Arg4: 2a009a40fffffffe

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


BUGCHECK_STR:  0x1a_5002

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  plugin-contain

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880097a2980 -- (.trap 0xfffff880097a2980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=000000000401a020
rdx=fffff8a006349fe0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800463b924 rsp=fffff880097a2b18 rbp=fffff880097a2ca0
 r8=0000000000025964  r9=000003e900007530 r10=0000000200000001
r11=0000000003fa0020 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgkrnl!memmove+0x154:
fffff880`0463b924 4c0fc349e0      movnti  qword ptr [rcx-20h],r9 ds:00000000`0401a000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e6e6e7 to fffff80002eddfc0

STACK_TEXT:  
fffff880`097a2818 fffff800`02e6e6e7 : 00000000`0000001a 00000000`00005002 fffff700`01080000 00000000`0000cd24 : nt!KeBugCheckEx
fffff880`097a2820 fffff800`02edc0ee : 00000000`00000001 00000000`0401a000 fffffa80`074cfb00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x45f28
fffff880`097a2980 fffff880`0463b924 : fffff880`0467cee6 00000000`ffffe17e 00000000`00000000 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`097a2b18 fffff880`0467cee6 : 00000000`ffffe17e 00000000`00000000 00000000`00000002 00000000`00000000 : dxgkrnl!memmove+0x154
fffff880`097a2b20 fffff960`001f057a : 00000000`0671e7c0 00000000`fff80000 00000000`00000000 00000000`00000001 : dxgkrnl!DxgkGetDisplayModeList+0x73a
fffff880`097a2bf0 fffff800`02edd253 : 00000000`00000001 00000000`03fa0018 00000000`0671e701 00000000`05130000 : win32k!NtGdiDdDDIGetDisplayModeList+0x12
fffff880`097a2c20 00000000`747214ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0671e798 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x747214ca


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!memmove+154
fffff880`0463b924 4c0fc349e0      movnti  qword ptr [rcx-20h],r9

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgkrnl!memmove+154

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

FAILURE_BUCKET_ID:  X64_0x1a_5002_dxgkrnl!memmove+154

BUCKET_ID:  X64_0x1a_5002_dxgkrnl!memmove+154

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

Probably you should take memtest for longer.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

 

[fnokke]

Well, what do you know, when testing the sticks one by one I got a hit! The first stick passed in both slots and overnight with just one stick now means 12-13 passes. But, the other stick showed errors very early. So know I have been testing for a while with just the one good memory stick and have not had any crashes so far. It will mean 4 GB instead of 8 GB but since I usually only run one application at a time on this computer I am guessing it will not make a big difference.

The game (LEGO Indiana Jones 2) mentioned in my original post actually crashed the first time we tried to play it after fixing this but after restarting it it has worked now for several consecutive hours so I hope it was actually just some bad handling on the part of the game in that instance.

Thanks a lot for helping out!

 

[koolkat77]

Good news.

Let us know if you have any other problems.