Solved BSOD at random times. Recently driver power state failure

[Rotzy]

BSOD at random times. New comments on 12/16

Random system restarts/BSOD. Sometimes it happens while the computer is in sleep mode, sometimes it's while I'm actively using it, sometimes I'll just be reading something on the screen and the system is suddenly restarting. This has been happening for years now but has recently gotten worse.

 

[Debbie B]

Hi,

Try running the Hardware Diagnostics on your computer. If you get any error code, make a note of the error code.

Did you try doing System Restore? If no and if this issue started occurring after doing some recent software changes on your computer, then I would suggest try restoring your system back to a date when it was working fine. System Restore will affect Windows system files, programs, and registry settings only.

For System Restore steps, you can refer to the URL mentioned: http://windows.microsoft.com/en-US/windows7/products/features/system-restore

 

[Arc]

In addition, you may need to update Logitech SetPoint Unifying KMDF USB Filter. LEqdUsb.Sys

kd> !irp fffffa800d18e680
Irp is active with 8 stacks 7 is current (= 0xfffffa800d18e900)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800c293700 00000000 00000000-00000000    pending
          Unable to load image \SystemRoot\system32\DRIVERS\LEqdUsb.Sys, Win32 error 0n2
*** [COLOR=Red]WARNING: Unable to verify timestamp for LEqdUsb.Sys[/COLOR]
*** [COLOR=Red]ERROR: Module load completed but symbols could not be loaded for LEqdUsb.Sys
 \Driver\LEqdUsb[/COLOR]
            Args: 00015400 00000001 00000004 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa80080149b0    

            Args: 00000000 00000000 00000000 00000000
=========================================
0: kd> lmvm LEqdUsb
start             end                 module name
fffff880`0541d000 fffff880`05434000   LEqdUsb  T (no symbols)           
    Loaded symbol image file: LEqdUsb.Sys
    Image path: \SystemRoot\system32\DRIVERS\LEqdUsb.Sys
   [COLOR=Red] Image name: LEqdUsb.Sys
    Timestamp:        Fri Sep 02 11:52:56 2011[/COLOR] (4E607640)
    CheckSum:         0001C3A8
    ImageSize:        00017000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
==========================================
0: kd> !devobj fffffa800c293700
Device object (fffffa800c293700) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa800c2936d0
 \Driver\LEqdUsb DriverObject fffffa800c293e70
Current Irp 00000000 RefCount 0 Type 0000002a Flags 0000200c
DevExt fffffa800c287eb0 DevObjExt fffffa800c293870 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa800c284a00 \Driver\usbccgp
Device queue is not busy.

Get the updates from Support + Downloads.

Let us know the results.

 

[Rotzy]

Thanks for the quick replys!

Hi,

Try running the Hardware Diagnostics on your computer. If you get any error code, make a note of the error code.

Did you try doing System Restore?

I completed a system test using Hardware Diagnostic Tools and everything passed. I have made no hardware/software changes to this computer in a looooong time. In addition, this random restart problem has been plaguing me for as long as I can remember so I doubt a system restore will help.

In addition, you may need to update Logitech SetPoint Unifying KMDF USB Filter. LEqdUsb.Sys
Get the updates from Support + Downloads.

Let us know the results.

I updated the unifying software using unifying210.exe from Logitech. We'll see how things go...

 

[Rotzy]

Another BSOD today. File uploaded. Thank you.

 

[Arc]

McAfee

fffff880`0b9cd700  fffff880`0119b3b0Unable to load image \SystemRoot\system32\drivers\mfehidk.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
 mfehidk+0x8a3b0[/COLOR]

Uninstall McAfee Using McAfee Removal Tool.
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download and install those, and then run full system scans with both of them, one by one.

Let us know the results.

 

[Rotzy]

Hello again and thanks for the help.

I just returned home and have not yet had a chance to remove McAfee but I did have another BSOD. File attached.

Thanks.

 

[Arc]

Remove McAfee and then let us know.

 

[Rotzy]

Removed McAfee and installed Microsoft Security Essentials last night. BSOD this morning.

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88054d9bb46, 1, fffff8000368f693, 5}


Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Let us know the results, with the subsequent crash dumps, if any.

 

[Rotzy]

I enabled Driver Verifier this morning and restarted as required. The computer would BSOD during boot up. Photo attached. I attempted booting 3 times then booted into safe mode and uninstalled SmartDefrag. I then rebooted normally and I am up and running again.

 

[Arc]

The dump file of that crash is not recorder, but you have done a very good job. Hopefully it will cure the issue.

Let us know the further situation.

 

[Rotzy]

I came home this evening and the computer was locked with the screen off. I reset the power to the monitor and it said "no signal". I had to use the power button to reset the computer. I don't know if there was a BSOD that proceeded the computer lockup but I attached a new file anyway.

I've also noticed that the computer is running noticeably slower than it was before I removed McAfee. Any thoughts on this? (I did run full scans with Microsoft Security Essentials after installation and MBAM).


I assume I should let the Driver Verifier run until tomorrow (about 24 hours) before starting to test the ram?

 

[Rotzy]

Almost as soon as I was done writing the last post I had another BSOD. I'm not sure the dump file was created as the BSOD screen froze. I took a picture of it instead. But, the file mentioned in the BSOD was "Mpfp.sys" which I assume is McAfee personal firewall plus. I thought I uninstalled everything McAfee???

Also, I was experiencing extremely slow internet speeds after I enabled Driver Verifier so tonight I disabled it and things are back to normal on that front.

 

[Arc]

Good job on the screenshot! There is no dump for it, but the screenshot made everything clear.

Mpfp.sys is McAfee Personal Firewall Plus Driver. And McAfee is the most well known BSOD causer.

Uninstall McAfee Using McAfee Removal Tool.
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download and install those, and then run full system scans with both of them, one by one.

Let us know the results.

 

[Rotzy]

I ran the McAfee removal tool AGAIN. Is there any way to check services and stop Mpfp.sys from starting (if it wasn't removed with the removal tool this time either)?

 

[Arc]

C:\Windows\System32\drivers
C:\Windows\SysWow64\drivers.

Search those manually, if you have uninstalled McAfee, and still those are there, delete them manually.

 

[Rotzy]

Mpfp.sys was still in the C:\Windows\System32\drivers folder. I deleted it and restarted...

 

[Arc]

And if everything worked ok, disable driver verifier.

 

[Rotzy]

I already disabled Driver Verifier. I was having terrible internet issues with it running.