Windows 10: BSOD Usually While Idle (variety of BugChecks)

General Info About The Issue:

-My system usually crashes while 1)idle or 2) under light usage (like web-browsing, etc.)
-It does not crash while gaming which is my primary use for the machine.
-There are a variety of Bugchecks (see attached)
-I can't seem to put my finger on any single action that causes a crash.

Things I Have Tried:
-All of my drivers are up to date (I use Driver Fusion Premium to keep them up to date).
-I have run Memtest86+ for 8+hours with 0 errors.
-I have done clean-installs of Windows several times and several system restores. The problem usually gets better but it slowly creeps back to more frequent crashes.

Other than that, all of the info is in the attached .dmp files.

Any help is appreciated *Huh



Attachment 36119

:)

 

Cant get my pc to quit bluescreening

BugCheck 50, {ffffc2825e765000, 0, fffff8013fcd644f, 2}

Could not read faulting driver name

Probably caused by : Wof.sys ( Wof!FileProvCompressWorkItem+6c )

That is a Windows component which means something else drove it into fault.

BugCheck A, {ffffa40ae0da6aa0, 2, 0, fffff800b9f33cfb}

Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+ab )

BugCheck 3B, {c0000005, fffff801d3b73b40, ffffb80f35f0e990, 0}

Probably caused by : ntkrnlmp.exe ( nt!RtlClearAllBits+26 )

The other minidump was corrupt.

No clear cause and the variety of BugCheck usually indicates a hardware problem.

What was the last Windows update and did this start before or immediately after it?

 

System restarts after sometime without user interaction.

I started the computer in safe mode , and computer ran with a BSOD .

now how am i going to find what's responsible for the BSOD while computer is idle?

 

Hi klimasjo,

Welcome to the 10forums.

A quick question, how many passes were completed with memtest?

 

Hmm.. I did the Memtest a while back. I can run it again and get back to you. Off the top of my head it was *several* but I don't remember exactly. I can run it for longer if my information points to memory issues.

I will say the RAM is starting to age. I bought it probably 4.5 years ago.

 

Well, the point is, you need to run MemTest for at least 8 complete passes for conclusive results.
Less then 8 passes isn't enough and a waste of time.

 

I'll run it again and post when it has done at least 8 passes.

 

Thank you.

I'm currently taking a look at the dump files, it might take a while seeing the number of dump files.

 

There are lots of memory_corruption in the dumps.
There are also some errors that could point to the hard drive.
So lets start with the memory and the hard drive






Diagnostics Test

HDD TEST


Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html

 

Attachment 36149
I obtained a drive health report on the SSD that has my OS on it. I can perform tests on my HDD as well but I am confident it is not the issue (problems started before I ever even installed it). All it contains is a few games and a few very small programs.

EDIT: I am about to start the Memtest. I had to do a little work on my USB Drive (it showed only 56MB available when it is 8GB ~ I figured out the issue and will start the test soon.)

 

Good,
After MemTest, open an admin command prompt and enter the following command
Code: chkdsk X: /r[/quote] X is the letter of the windows partition, please use the letter of your windows partition.

It might take a while for chkdsk to finish, please let it run, even when it looks like it is frozen/stuck.

 

Ran Memtest for about 10.5 hours for 8 passes and it returned 0 errors.

I will run CHKDSK on my hard drive and get back to you. Can a drive that does not have my OS on it cause all these problems? Remember, my OS is on an SSD which is healthy. It would be redundant to run CHKDSK on this drive.

 

Can't say for sure, because I've never experienced it.
But Windows checks the hardware, so I would test the other drive(s)