BSOD occurs every 6 days, error 0x0000000a

[bk81]

Hi all,

I'm running into a BSOD that seems to occur every six days. The Windows event logs shows the following:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x000000000575fdf0, 0x000000000000000f, 0x0000000000000001, 0xfffff8000360ab07). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071516-17440-01.

The NirSoft Bluescreen analyzer tags it as: IRQL_NOT_LESS_OR_EQUAL 0x0000000a/

Attached is the file generated by DM Log Collector. Any help is highly appreciated.

 

[axe0]

Please run the DM Log Collector again and upload a new zip, the current uploaded one misses several logs.
You could check if there are

1. 18 .txt,
2. 1 .nfo,
3. 1 or more .dmp,

files present, if this is the case then all logs are present
If there are a few missing, no problem as we can get them manually if required

 

[bk81]

I've run the DM log tool again and uploaded the new compressed archive.

In case the files are still missing, where would I find them? The ZIP file only contains eight .DMP files.

Thank you for your help.

 

[axe0]

Those dumps are quite old, at least a few months.

It is a collecting tool, it creates files through certain commands
Try this version of the DM Log Collector.
http://www.sevenforums.com/attachme...9456376-bsod-after-sleep-dm_log_collector.bat

 

[bk81]

Used the batch file and removed all the old dumps. The most recent four should be included.

 

[axe0]

Please run below command in an admin command prompt to create some files, zip them up and upload the zip.

type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&tasklist > "%USERPROFILE%\Desktop\tasklist.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt"&msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"

The files will be created on the desktop.

 

[bk81]

PC crashed again yesterday afternoon.

Attached is the ZIP file of the new reports.

From the Windows has recovered from an unexpected shutdown screen:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 000000000509F698
BCP2: 000000000000000F
BCP3: 0000000000000000
BCP4: FFFFF80003612B60
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\072716-15303-01.dmp
C:\Users\Jeff\AppData\Local\Temp\WER-339520-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[bk81]

And here's the latest BSOD report collected with the batch file.

What's causing this PC to Blue Screen?

 

[axe0]

Please run the command I posted in an admin command prompt, the latest zip only has a single dump. I need to look at the other files.

 

[bk81]

Running the posted command with admin rights again. Made sure this morning that I was running it with elevated privileges.

I had moved out the old dump files before running the collector batch file again.

Hopefully everything you need is attached this time. File is much bigger this time.

Thank you Axe0.

 

[axe0]

The last one was caused by a temp driver called cpuz138_x64.sys, it is only there when you open a program like CPU-Z or Speccy.

For the one before the last it seems there were some problems, thus the one around the time you created this thread. Windows recorded a bad dump file, indicating problems with the memory.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

[bk81]

Yes, I noticed the cpuz138_x64.sys file as well. It was in a odd location:
C:\Windows\Temp

There were no traces of either CPU-Z or Speccy on the PC.

I'm not physically at the PC but will try to have a user run the memory tests. Thank you.

 

[axe0]

It isn't an odd location, unfortunately I've almost forgotten the reason why this driver is in the Windows temp folder so I can't explain

What you could do is simply clear the temp folder, best is after a reboot to ensure not too much is being used.

 

[bk81]

System has 16 GB of RAM and took forever to complete.

After 8 passes, zero errors were found.

Any other leads of what could be causing this repeating BSOD issue?

 

[axe0]

Make a photo of the result and post it.

I doubt you did this

 

[bk81]

I forgot to ask the user to create a picture.

Memtest run for 29+ hours and found no errors. 8 passes on the 16GB were completed.

I'm working on the PC remotely and only the CD worked. Was unable to set the BIOS to boot from a USB stick.

 

[Layback Bear]

How did you install a MemTest86 + C/D remotely?

 

[axe0]

Was unable to set the BIOS to boot from a USB stick.

That happens to many users, the reason is that some settings in the BIOS need to be changed. Unfortunately this is with every motherboard different.

 

[bk81]

How did you install a MemTest86 + C/D remotely?

Saving MemTest to CD and having the user change the BIOS settings to boot from CD worked.

Using removable devices did not allow the PC to boot via USB stick.



MemTest found no issues. What else could I be looking at here? I'm at a loss.