Kernel-power event ID 41 task category 63

Can someone please help me with a BSOD problem I am having? If so what information do you need.

 

Regards

 

Shaun

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
If you are overclocking stop.  (chances are if you dont know if you are, you are not)
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  

The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy (compress them)
*Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.

Link for how to  upload below.


To ensure minidumps are enabled:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Please also run MSinfo32 and upload the output as well.
To run MSinfo32 please go to start>run>MSinfo32
Go to "file" "save" and upload the saved file with the DMPS

System specs are extremely useful so please include whatever you know.

Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...

You can read more about BSODS here
You can learn how to test your memory here


Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I only have one DMP file in my Minidump folder, even though it has crashed a few times already. Does this mean I need to wait until I get the next BSOD in order to send you two DMP files?

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Sledge1

We prefer 2 or more but can start with the first one.
Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

This is to the dump file:

 

http://sdrv.ms/19sNDAC

 

This is to the MSINFO file:

 

http://sdrv.ms/16ZiN2d

 

I think all the system info is in the MS file?  But I have attached to this computer a wifi enabled HP printer, with the HP driver software on it, plus a netgear wireless router, connected wirelessly. Not sure if you need anything else?

 

 

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Sledge1

This one crash was Related to usbcir.sys USB Consumer IR Driver for eHome from Microsoft Corporation.  Since that is a part of the OS I would run a system file check to verify (and hopefully repair) the file

To run a system file check (SFC)

Open an elevated cmd window
(Go to start>type CMD>right click and run as administrator)

Type SFC /scannow

You may have to run this up to 3 times.

Let us know the results at the end



Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I wan scannow 3 times and each time it came up saying:

 

"Windows Resource Protection did not find any integrity violations."

 

Not sure if this is relevant, but I had a USB hard drive connected when it crashed with the DMP file I sent you. But I have had a BSOD before when the USB drive was not connected.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I have had two further crashes in the last hour or so.  I did not get the traditional BSOD, my screen went all jagged and fuzzy. But here are the DMP files:

 

http://sdrv.ms/14VAbXR

 

 

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Sledge1

It is beginning to look like memory

These crashes were caused by memory corruption (probably a driver).  Please run these two tests to verify your memory and find which driver is causing the problem.  

Dont forget to upload any further DMP files (especially those when verifier is running)

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!   If you dont know what this means you probably arent

1-Memtest.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Get it here
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.

You can read more about running memtest here

Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.


2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Here is the procedure:

Go to Start and type in "verifier" (without the quotes) and press Enter
Select "Create custom settings (for code developers)" and click "Next" (or  Type "verifier /standard /all"  (no quotes) if you want to verify all of them (this will slow your computer down))
Select "Select individual settings from a full list" and click "Next"
Select everything EXCEPT FOR "Low Resource Simulation" and for win 8 dont check Concurrency stress test, and DDI compliance checking click "Next"
Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Further Reading
http://support.microsoft.com/kb/244617

About Driver Verifier
Driver Verifer information  driver verifier Windows Vista - Microsoft Search
Driver Verifier issues within Vista/ Windows 7  http://support.microsoft.com..default.aspx?+verifier1&res=20
Driver Verifier Special Pool Feature  http://support.microsoft.com/kb/188831

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks. I am a little perplexed now...

 

I run memtest, and on the first pass it found faults. I then removed one of the RAM stick and ran it again. This time, after running memtest for 6 passes it found nothing. I then moved the remaining memory stick into the empty slot which had been vacated by the previous stick. I then ran memtest again, and once again, after 6 passes it came up with nothing. So I thought "great it must be the stick, not the slot." But just to be sure I decided to re-run the first stick that I had removed that I thought was faulty. This time after 6 passes it came up with nothing. I then returned the other stick (the one I thought was good), and re-ran memtest for 6 passes with both sticks in. This time memtest came up with nothing!

 

Is this normal? Could it be that the card was maybe not sitting right or something?

 

I have not run the verifier test yet. Should I?

 

Regards

 

Shaun

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Sledge

It does sound inconsistent.  I would forget about memtest for the moment and move to verifier.  If it is in fact memory verifier will give us some clues to that fact, and if not it will tell us the driver that is giving you grief.
Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated April 1, 2019 Views 6,390 Applies to: