Solved BSOD was waiting for me when I returned to my laptop this evening.

[Drawn]

Returning from dinner, I was greeted with the BSOD.

I had only my browser up and running at the time.

I believe I was playing some MiniClip 8 Ball online pool hours earlier.

Not much help, I know.

Hoping someone could take a quick look and determine what the cause may have been.

You guys are the pro's.


Cheers.

 

[koolkat77]

Hello Drawn,

Reduce items at start-up:

• How to Change, Add, or Remove Startup Programs in Windows 7

Perform a clean boot:

• How to Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista

Scan with Kaspersky TDSSKiller:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• How to Repair Windows 7 System Files with System File Checker

Post a screenshot of your Hard Drive(s) using Crystal Disk Info software:

• CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test:

• http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

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

• How to Run Disk Check in Windows 7

Keep us posted.

 

[Drawn]

Nothing Found in BSOD info?

Thanks for the response, but your reply suggests you have no specific information to share regarding my recent BSOD.

I would rather have some idea of what we're looking for here?


Cheers.

 

[Arc]

Unfortunately you cannot expect for a single "fix" button .... do only one particular thing and your issue is solved. That is rather a hypothesis than practice.

The crash dump is blaming Intel Management engine.

BugCheck D1, {b8, 2, 0, fffff88000e5870e}

*** WARNING: Unable to verify timestamp for TeeDriverx64.sys
*** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
[COLOR=Red]Probably caused by : TeeDriverx64.sys[/COLOR] ( TeeDriverx64+e4fa )

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

Driver Reference Table - TeeDriverx64.sys

It is a widely used and trusted program. Though not anything compulsory. But still, it is very doubtful that management engine is failing itself. Tests must be done to make it sure that nothing else is contributing to this issue; and only then it is viable to go for the further steps, like removing management engine.

Let us know the results of the tests suggested in post #2.