Repeated power kernel event 41 crashes

[DrTom]

I've had 9 of these in the last couple of months, but they seem to be increasing in the last couple of weeks. I've created the zip file as instructed on this site - can anyone suggest how to fix this?

 

[Thedoctor44]

Your Intel WiFi 5100 driver appears to be causing problems

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002a0a477}

Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
[COLOR="Red"]Probably caused by : NETw5s64.sys[/COLOR] ( NETw5s64+b76b )

fffff880`0580c000 fffff880`05eb9000   NETw5s64 T (no symbols)           
    Loaded symbol image file: NETw5s64.sys
    Image path: \SystemRoot\system32\DRIVERS\NETw5s64.sys
    Image name: NETw5s64.sys
    Timestamp:        [COLOR="red"]Tue Sep 15 20:40:39 2009[/COLOR] (4AAFEDB7)
    CheckSum:         006A6E93
    ImageSize:        006AD000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please create a system restore point before changing the drivers. Follow these instructions.

http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

Uninstall the previous driver from the control panel.

Go here to download the updated version of the Intel WiFi Link driver. Download the Wireless_15.3.1_Ds64

https://downloadcenter.intel.com/De...116&keyword=Intel+Wifi+Link+5300+AGN&lang=eng

 

[DrTom]

Gosh I was having problems with that driver before too! I will update the driver and see if that fixes the problem. Thanks so much for your help.

 

[Thedoctor44]

Make sure you create a restore point, I don't want any guilt due to making your system even worse by getting you to install the wrong driver.

 

[DrTom]

I updated that driver, but the problem happened again today. Can anyone tell me if this driver is still causing a problem? thanks!

 

[Thedoctor44]

There are no new dump files. Please upload the new dump files. These are dated from 2013.

 

[DrTom]

Sorry for the delay in replying, I did not see that anyone had responded. Anyhow, I am still having this problem even after updating the driver suggested above. I've used the DM Log Collector to regather the files and have attached them here. Thanks in advance for any help!

 

[Thedoctor44]

The latest dump files still show your driver has the timestamp of 2009.
You can try updating it via device manager.

 

[DrTom]

Thanks Thedoctor44. I had updated to the driver you suggested earlier in the thread, but was having the same problem so I reverted to this older driver (which I thought had been working before). I will try updating in device manager and see if the problem continues.

 

[DrTom]

OK so I've updated the driver using Device Manager, and had the crash again. Can anyone tell me if NETw5s64.sys is still causing this problem? Also, can anyone tell me how to view the "Bugcheck Analysis"? It might be easier for everyone if I knew how to view it myself, instead of having to ask here (haha).

Thanks!!!

 

[Thedoctor44]

There are no new dump files.
Check in these directories:

C:/Windows/minidump

C:/Windows/memory.dmp

If you have Small Memory Dumps then copy them to the desktop, zip them up and upload them in your next reply.

If you have a Kernel Memory Dump then copy it to the desktop, then upload it to a file sharing site like OneDrive then post the link here.

 

[DrTom]

OK let's try again! Attached are the files from C:/Windows/minidump

 

[Thedoctor44]

Nope still nothing, we could give Driver Verifier a try.

Enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It

Driver Verifier will make the system laggy, this is normal so don't worry.

Before enabling DV, make sure that you have earlier System restore points made in your computer.

If there are no points, make a System Restore Point Manually

Post back the results.

 

[DrTom]

I've had the Driver Verifier running since 8 am this morning, but it hasn't crashed yet. Can I turn my computer off overnight, or should I let it run? Overnight I won't be working (which is when the crashes always happen). Thanks.

 

[Thedoctor44]

It's up to you.
You can leaving it running or turn it off and use the PC whenever you want.

 

[DrTom]

OK the driver verifier ran for about 27 hours (but I turned it off when I was sleeping), and a crash didn't happen. It did slow my system down quite immensely however! Does this mean the driver verifier didn't help? Is there a next step I should take? Thanks!

 

[Thedoctor44]

If Driver Verifier find nothing then hardware testing should be the next step.

Stress test your CPU with Prime95

I recommend running Prime95 for around 2 hours

   Warning

As with most stress tests your component's temperature will rapidly increase.
It is advised that you download a temperature monitoring program like HWmonitor
Keep an eye on your temperatures and stop the tests if it starts to overheat

Stress test your graphics card with Furmark

I recommend running it for around 30 minutes

   Warning

Furmark will increase the temperature of your GPU rapidly so keep and eye on your temperatures

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Post back the results.

 

[DrTom]

^^tried the above. with SeaTools, both drives passed short DST, short generic, and long generic. Disk Check revealed no problems. Furmark would not run properly - like 2 or 1 FPS even with low resolution. Prime95 passed 2 hours. Memtest had 5 passes without errors.

I've been having problems with my c1000a wireless router crashing, which is somehow being caused by my T400 laptop (all devices would connect and function on router until I turned on T400 wifi, which would cause the router to crash). I reverted the Intel 5300 AGN driver from the Intel 14.3.2.1 back to the Microsoft 12.4.1.4. The T400 is no longer crashing the router, however I just had another BSOD. I assume this is again caused by the 5300 driver. On rebooting, Windows popped up with a little message saying I could find detail of the error in two files (both attached here).

Can anyone suggest what the heck might be going wrong? I'm wondering if I should replace this stupid Intel 5300 card.

 

[DrTom]

Any suggestions? Just had another crash running Intel 5300 AGN driver version 14.3.0.6.

Driver versions 12.4.1.4 and 14.3.0.6 both cause my machine to crash, whereas driver version 14.3.2.1 causes the wifi router and modem to crash. I'm not sure what to do at this point beyond replacing the 5300 card.

 

[DrTom]

Just had a third crash in as many days. Can anyone recommend a way forward? Or, is there no solution and I should stop posting here? Thanks!