Solved event 41 kernel power 0x8000000000000002

[writhziden]

No need to run it if it came back with no integrity violations.


Other software that could be causing conflicts is driver software.

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 210773
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

 

[wickwrackscar]

No need to run it if it came back with no integrity violations.


Other software that could be causing conflicts is driver software.

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:
  

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 210773
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

Ok i will give that a shot, thanks again.

 

[wickwrackscar]

so i did all that restarted the computer and got it to crash. however it did not generate a crash dump.

back when this first started a year or so ago it started as a blue screen and it did generate a minidump, then one day it turned into just a hard reset with no minidump. there is not mini dump folder any longer and i have tried all the guides to make sure i have it set up to generate minidumps.

any ideas?

 

[writhziden]

Can you turn off the automatic restart and provide us with as much crash information as possible? See OPTION ONE, step 6. in http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html. The image shown in that step has automatically restart enabled. Uncheck the box to disable it.

 

[wickwrackscar]

Can you turn off the automatic restart and provide us with as much crash information as possible? See OPTION ONE, step 6. in http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html. The image shown in that step has automatically restart enabled. Uncheck the box to disable it.

so i set the computer to not auto restart, then of course it has not been crashing for the last 2 days. it just now finally crashed today and it restarted anyway, i made sure that the box is still unchecked, also there is still no dump file.

 

[writhziden]

Was there a blue screen when it crashed, or did it restart without one?

 

[wickwrackscar]

It restarted without one. When it happens the screen is just instantly black and the computer has reset.

 

[James7679]

there is not mini dump folder any longer and i have tried all the guides to make sure i have it set up to generate minidumps.
any ideas?

Yes, you need to recreate the minidump folder, navigate to c:\Windows and before creating a new one, just verify that the folder is not there. If there is no folder labelled "minidump" in the Windows folder, then you need to create a new one. Right click in an open area on the right window of the explorer pane. Then select new>folder. Label it as "Minidump"(without the quotes).

After creating the new folder, just to verify that minidumps are enabled, press the windows logo key and pause/break keys at the same time. Then select advanced system settings. Then, under the advanced tab, see startup and recovery? Select properties, under system failure, ensure that "write an event in the system log" is checked, under "write debugging information" "small memory dump" should be selected and the directory should be %SystemRoot%\Minidump. Click OK.

 

[wickwrackscar]

there is not mini dump folder any longer and i have tried all the guides to make sure i have it set up to generate minidumps.
any ideas?

Yes, you need to recreate the minidump folder, navigate to c:\Windows and before creating a new one, just verify that the folder is not there. If there is no folder labelled "minidump" in the Windows folder, then you need to create a new one. Right click in an open area on the right window of the explorer pane. Then select new>folder. Label it as "Minidump"(without the quotes).

After creating the new folder, just to verify that minidumps are enabled, press the windows logo key and pause/break keys at the same time. Then select advanced system settings. Then, under the advanced tab, see startup and recovery? Select properties, under system failure, ensure that "write an event in the system log" is checked, under "write debugging information" "small memory dump" should be selected and the directory should be %SystemRoot%\Minidump. Click OK.

Its funny that you suggested that just now because I actually did just that last night. I dident know if it would do anything but I thought it was worth a try. thanks.

 

[writhziden]

It does not seem like you are getting blue screen crashes, so I do not think minidump settings are the issue here. This is starting to seem like a hardware issue. You said you have already done stress tests on components. Go through the following hardware tests and perform any that you have not performed exactly as they are described in my steps.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[wickwrackscar]

I will give that a shot when i get home. Thanks again.

 

[writhziden]

You're welcome. Let us know the results of the hardware checks as you run them. Best of luck tracking it down.

 

[wickwrackscar]

so i did the furmark test the gpu held steady at 85 c, no artifacts but it does stutter a tiny bit on the background. not much just enough to notice that its happening.

i am running the vmst now.

 

[writhziden]

FurMark test sounds good. Look forward to the video memory test results. If you get messages that certain tests were not supported, those can be ignored. Just let us know if it finds errors.

 

[wickwrackscar]

vmst had 0 errors in 21 passes, will run the others tonight when i get home.

 

[writhziden]

Good news! Graphics card should be clean, then. Hopefully we can narrow down the culprit.

 

[wickwrackscar]

finished the first test from prime 95, the small fft and it had no errors. ran for about 2 hours.

 

[writhziden]

Should be fine, then. What temperatures were you seeing during the small FFT test? Post back after you have done the rest of the Prime95 tests, and include temperatures during idle and during the tests.

 

[wickwrackscar]

so i finished the prime 95 tests and there were no errors. the cpu temp was about 40c at idle and mid 70c during the tests.

 

[writhziden]

The maximum safest temperature for that processor is 76 C. You may consider checking that you have a good amount of thermal compound spread and have good contact between the processor and heatsink; the heatsink should not budge if you wiggle it with your finger. If you have a good amount of thermal compound spread and in good contact, think about getting a new cooling system with a better fan and heatsink. Remember to follow the ESD safety steps I outlined in post #30 when opening up your system.

Also, if you remove the heatsink from the processor, you will have to clean off the old thermal compound and re-apply new thermal compound to the processor. If you do not currently have thermal compound, do not remove the heatsink until you have purchased a supply of thermal compound.

Thermal Paste and How To Use It