BSOD 0x000000050 on 3 Win7 PCs

Hi Ryan01.

Debugging two or three different PCs at the same time will be conflicting. So I am concentrating on the PC2 first.

After that one, will concentrate on the others one by one.

For PC2, the BSOD is caused by CPUz hardware monitoring utility.

Code:

BugCheck 50, {fffff80000000018, 0, fffff880073f5366, 0}

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

Could not read faulting driver name
Probably caused by : cpuz135_x64.sys ( cpuz135_x64+2366 )

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

But the strange thing is, it is running from the temp folder.

Code:

cpuz135    cpuz135    \??\c:\windows\temp\cpuz135\cpuz135_x64.sys

As it is temp, you can delete it. For securely deleting temp, you can use CCleaner.

Do you have CPUz installed actually? If so, uninstall it, at least as a test.

Things running from temp are causing issues ... it is always suspicious. Scan the system for possible virus infection with the following programs only.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

And, Stress test the CPU.
Hardware - Stress Test With Prime95

When this one will be narrowed down, I will check the other ones.

PC3

Apparently has the same issue.....apply Arc's PC2 suggestions to PC3 too at this stage.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80000000018, 0, fffff88008aca366, 0}

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

Could not read faulting driver name
Probably caused by : cpuz135_x64.sys ( cpuz135_x64+2366 )

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

TFC is a useful utility that is often used in malware removal to delete temporary files. It can also be safely used as a general purpose temporary file remover, as an alternative to CCleaner.
http://www.bleepingcomputer.com/download/tfc/

Ryan01 said:

no, CPUz is not installed on the machine.

It seems to be a virus issue.

I requested cottonball to guide you through virus removal.

Ryan01,

Please use the following diagnostic tool. It has a powerful detection mechanism, and may help us get to the cause of your issues:

Please use the Farbar Recovery Scan Tool.
Download: Farbar Recovery Scan Tool Download
Select the version that applies to your system.
Save it to your Desktop.
Double-click the downloaded file to run it.

When the tool opens click Yes to the disclaimer.
At the program's console, press the Scan button.

When done, the tool produces a log, FRST.txt, in the same directory from which the tool is run (Desktop).
Please provide the FRST.txt in your reply.

The first time the tool is run, it also makes another log: Addition.txt
Also post the Addition.txt in your reply.


Let's get a view of all services and dependencies scoped by the following tool...
Farbar Service Scanner
Download: Downloading Farbar Service Scanner

Make sure the following options are checked:

Internet Services
Windows Firewall
System Restore
Security Center
Windows Update
Windows Defender

Press: Scan

When done, FSS creates a log, FSS.txt, on the Desktop.

Please provide the FSS.txt in your reply.

Thank you.