BSOD 0x000000050 on 3 Win7 PCs

[Ryan01]

Hello

I have 3 Windows 7 PCs that have been crashing with the same BSOD. All are Win 7 64-bit. The attached crash reports are for PC #2 and #3.

PC #1 Crashed 3 times: 1/23/13, 5/12/13, 2/11/14

I replaced PC #1 with PC #2 on 3/21/14

PC #2 crashed on 3/25/14 at 2:28:59 PM

PC #3 is in another room. It too crashed on 3/25/14, one minute earlier, at 2:27:59 PM

The BSOD splash says "cpuz135_x64.sys PAGE_FAULT_IN_NONPAGED_AREA" every time. Though our tech specialist looked and found that cpuz is not installed on any of the PCs. He could not find a common denominator to the crashes. He did mention a USB driver issue in January, that he's looking into.

Various online sources mention USB drivers as suspect. That could be relevant since all 3 PCs control laboratory equipment by USB, using Labview. I see one instance on the LV forum about a USB-GPIB module, which I am using on PC #1. But I have the latest driver, and it's only on one PC. So if that is flagging, I'd like to know so I can work around it.

PC #1, #2: Labview 11 SP1 64-bit with DAQmx9.3.5 controlling NI-GPIB-USB-H module.

PC #3: Labview 13 64-bit with DAQmx9.7.5 controlling NI-USB-6341 multi-function DAQ + ORTEC 927 USB-MCA.

Thank you,

Ryan

 

[Arc]

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.

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
[COLOR=Red]Probably caused by : cpuz135_x64.sys [/COLOR]( cpuz135_x64+2366 )

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

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

cpuz135    cpuz135    \??\c:\windows\[B]temp[/B]\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.

 

[Ryan01]

Hi Arc,

Thanks for the info. To answer your question, no, CPUz is not installed on the machine. I did find cpuz135_x64.sys in temp as indicated and shift+deleted it and its containing folder.

I ran Windows Defender Offline (default Quick Scan). The resulting log files are attached in zip of the Support folder. I also ran the stress test, with no errors or warnings.

Alas, I won't be able to get back to this machine for a week or more.

I will leave it running with same software open as during the last crash, so at least can see if it crashes again.

Thanks,

Ryan

 

[Golden]

PC3

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

*******************************************************************************
*                                                                             *
*                        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 :[COLOR="Red"] cpuz135_x64.sys[/COLOR] ( 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]

Thanks Golden. I will do.

 

[Arc]

no, CPUz is not installed on the machine.

It seems to be a virus issue.

I requested cottonball to guide you through virus removal.

 

[cottonball]

Ryan01,

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

:info: 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).
:ar: Please provide the FRST.txt in your reply.

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


:info: 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.

:ar: Please provide the FSS.txt in your reply.

Thank you.

 

[Ryan01]

Cottonball,

Thanks for the help. I have run the scans and attached the results here.