Solved BSoD trying to plug in Olympus camera VR-310 through USB port

[andrew111]

Hello there!
I faced a very strange error under very strange circumstances. Stop error code 0x00000023.
EventData
BugcheckCode 35
BugcheckParameter1 0xe0107
BugcheckParameter2 0xfffff880035bc2a8
BugcheckParameter3 0xfffff880035bbb00
BugcheckParameter4 0xfffff88000fbf079
SleepInProgress false
PowerButtonTimestamp 0

It’s a persistent error. It happens every time I’m plugging in to my laptop my Olympus camera VR-310 using USB ports.
I can’t understand and find in Internet what’s the cause of it. Previously all worked fine. But then I updated BIOS to the latest version and now can’t use the camera. And probably this error is in no connection with the BIOS updates.

Here is the archive file with data. Please, help to identify the problem: what it causes, what driver to remove, what driver to update.

 

[koolkat77]

Welcome to Seven Forums,

Do you have McAfee and Norton both installed on your system? If yes please remove them using their removal tool from here: Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase They are a very frequent cause of BSOD-s.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials, Free antivirus for windows.
• Malwarebytes Anti-Malware Free
• Good and Free system security combination
  
  

   Warning

:ar: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Please uninstall this software as well:

[COLOR="Red"]MfeEpePcMonitor[/COLOR]	"c:\program files\[COLOR="Red"]hewlett-packard[/COLOR]\drive encryption\epepcmonitor.exe"	Public	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

You will find this tutorial useful: http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html

Perform a System File Check to check the integrity of all protected Windows 7 :

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:

• SFC /Scannow Command - System File Checker

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

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

This tutorial http://www.sevenforums.com/tutorials/147369-usb-selective-suspend-turn-off.html may help you as well:

To Disable Selective Suspend:

• open the control panel
• go to power options (you may have to set view to small icons)
• click change plan settings
• in the window that opens:
• click change plan settings
• click change advanced power settings, expand usb and ensure usb selective suspend is disabled.

Please remove any Disk Defrag, Back up tool from your system and test your hard drive(s)

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo Standard Edition
• How to Upload and Post a Screenshot and File in Seven Forums

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

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

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

Let us know the results with further BSOD reports if any.

BSOD BUGCHECK SUMMARY

Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Sun Mar  3 16:26:48.704 2013 (UTC + 6:00)
System Uptime: 0 days 4:52:38.034
*** WARNING: Unable to verify timestamp for MfeEpePc.sys
*** ERROR: Module load completed but symbols could not be loaded for MfeEpePc.sys
Probably caused by : partmgr.sys ( partmgr!PmGlobalDispatch+69 )
FAT_FILE_SYSTEM (23)
BUGCHECK_STR: 
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
STOP 0x00000023: FAT_FILE_SYSTEM   
Usual causes:  Disk corruption, insufficient physical memory, Device driver, 
Indexing, Resident antivirus, backup, defrag programs, 
Disk/Drive failing/failure
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Thu Feb  7 14:58:18.501 2013 (UTC + 6:00)
System Uptime: 0 days 0:24:59.360
*** WARNING: Unable to verify timestamp for MfeEpePc.sys
*** ERROR: Module load completed but symbols could not be loaded for MfeEpePc.sys
Probably caused by : partmgr.sys ( partmgr!PmGlobalDispatch+69 )
BUGCHECK_STR: 0x23
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
STOP 0x00000023: FAT_FILE_SYSTEM   
Usual causes:  Disk corruption, insufficient physical memory, Device driver, 
Indexing, Resident antivirus, backup, defrag programs, 
Disk/Drive failing/failure
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Thu Feb  7 14:09:44.743 2013 (UTC + 6:00)
System Uptime: 0 days 0:16:58.992
*** WARNING: Unable to verify timestamp for MfeEpePc.sys
*** ERROR: Module load completed but symbols could not be loaded for MfeEpePc.sys
Probably caused by : partmgr.sys ( partmgr!PmGlobalDispatch+69 )
FAT_FILE_SYSTEM (23)
BUGCHECK_STR:   0x23
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
STOP 0x00000023: FAT_FILE_SYSTEM   
Usual causes:  Disk corruption, insufficient physical memory, Device driver, 
Indexing, Resident antivirus, backup, defrag programs, 
Disk/Drive failing/failure
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[andrew111]

koolkat77, thanks for your help. To perform a System File Check to check the integrity of all protected Windows 7 – this was very useful. The laptop stopped taking more than several seconds to enter into sleeping mode.
As to BSoD I've found the solution.
It was too boring and cumbersome for me to remove and then reinstall programs, do tests without clear understanding what I was doing and why.
The problem was MfeEpePcMonitor, which is used in HP Drive Encryption Tool:
https://community.mcafee.com/docs/DOC-3338

Latest version of McAffe patches is able to cause BSOD. Infortunately, I upgraded the HP program. Since then I had a described problem.
I solved it by uninstalling HP Drive Encryption Tool. Now there is no BSoD anymore.


I did how the topic starters having the same or similar problem did:
Kindle Keyboard Windows 7 BSOD - Microsoft Community
http://www.sevenforums.com/bsod-hel...tign-any-usb-devices-stop-0x23-0xc4-0xc9.html

 

[koolkat77]

I'm glad you found a solution

 

[andrew111]

One more BSOD

Hello there!
Once again with one more problem on BSOD.
Laptop OS crashed on the 31 may.
With results of MS WinDbg and BlueScreenView v1.52 can't understand the reason of error (is it a driver, or HD, or RAM) and how to correct it.
Please, help to identify the problem
Here is the archive file with data.

 

[Arc]

The BSOD is caused by NEC/Renesas USB3 driver.

BugCheck 50, {fffffa80070b1f28, 0, fffff88006a78ce0, 0}

*** WARNING: Unable to verify timestamp for nusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3hub.sys

Could not read faulting driver name
[COLOR=Red]Probably caused by : nusb3hub.sys[/COLOR] ( nusb3hub+10ce0 )

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

Which is very old.

    Image name: nusb3hub.sys
    Timestamp:        [COLOR=Red]Fri Nov 20 15:45:57 2009[/COLOR] (4B066C5D)

Unfortunately you need to update it from a third party source like Renesas/Nec uPD720200/720200a USB3 Controller Drivers Version 2.1.39.0 WHQL .... because HP does not have updates with them.

Let us know the result.