BSOD Help

[NewbixCube]

Computer has been randomly rebooting when under load but just now while only having 5 tabs open in chrome, discord, and skype it blue screened. This is the first time it properly bluescreened and it created a dump file.

EVGA is already sending me a new PSU in a few days since my PSU voltage appeared to be too high and fluctuating too frequently. And I've just ordered a new GPU that is arriving around the same time the PSU is arriving. Before I put any new parts in my PC I wanted to see if this BSOD had any irrelevance from PSU/GPU.

 

Permon Report, Bluescreenview, and Eventviewer zip:

https://mega.nz/#F!J1MQzQab!NNn6W3yX9NaIzb4w6fsrSQ

 

 

WhoCrashed:

Spoiler

On Fri 11/11/2016 3:06:11 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111116-3531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 11/11/2016 3:06:11 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidMmInterface+0x1B30F)
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[Guest]

In one of those bluescreen reports, it mentioned wof.sys. Not knowing what this file was, I used google. Since I am dutch, I got lots of dutch results, such as this one:

 

http://www.solvusoft.com/nl/files/bsod-blauw-scherm-fout/sys/windows/microsoft-corporation/microsoft-windows/wof-sys/

 

(maybe it will get transformed into your native language)

 

My point is: with the ! icon, there was a list of 7 bullets with different causes. 5 out of them 7, are software/drivers related issues. One mentioned memory (ram) failure, and the other mentioned a failing harddrive.

 

There are tools to check the health of your memory and hard drive. If it's not those two components, I would suggest a fresh install of windows to fix this problem.

 

*DISCLAIMER: just pulled this info from google, no guaranteed succes!

[NewbixCube]

3 minutes ago, Dutch-stoner said:

In one of those bluescreen reports, it mentioned wof.sys. Not knowing what this file was, I used google. Since I am dutch, I got lots of dutch results, such as this one:

 

http://www.solvusoft.com/nl/files/bsod-blauw-scherm-fout/sys/windows/microsoft-corporation/microsoft-windows/wof-sys/

 

(maybe it will get transformed into your native language)

 

My point is: with the ! icon, there was a list of 7 bullets with different causes. 5 out of them 7, are software/drivers related issues. One mentioned memory (ram) failure, and the other mentioned a failing harddrive.

 

There are tools to check the health of your memory and hard drive. If it's not those two components, I would suggest a fresh install of windows to fix this problem.

 

*DISCLAIMER: just pulled this info from google, no guaranteed succes!

 

I just installed new SSD so I'll look into that. Although the reboots were happening before I installed this new SSD and removed the old HDD.

GPU drivers are up to date but I'll be cleaning those driver ssoon because of new gpu.

Ram was memtested not long ago.

I'm going to check for more updates and hope I don't have to fresh install windows. Having 300 kb/s makes downloading something like that insane.

[Guest]

So you cloned (or migrated or whatever) your OS from your HDD to your SSD... If you had this problem while using your HDD, and now still on your SSD, this change of drives is not that interesting. It kept all software/driver errors.

 

Also, when you have some old drivers, and add new or upgraded your drivers, some old errors or crap might still be somewhere on your OS. Might even be an update created the error...

 

Considering your memory is fine, and you are using a new SSD, I would really think of some software problems.

 

However... You said you replaced your HDD with an SSD, and removed the HDD... So you can put in your HDD again, format it, and do a fresh/clean install of windows. (you keep your current installation on your SSD) If the problem gets fixed, you know what you have to do. If the problem still exists, start praying. (won't do jack sh*t, but well, your screwed then anyways)

[NewbixCube]

1 minute ago, Dutch-stoner said:

So you cloned (or migrated or whatever) your OS from your HDD to your SSD... If you had this problem while using your HDD, and now still on your SSD, this change of drives is not that interesting. It kept all software/driver errors.

 

Also, when you have some old drivers, and add new or upgraded your drivers, some old errors or crap might still be somewhere on your OS. Might even be an update created the error...

 

Considering your memory is fine, and you are using a new SSD, I would really think of some software problems.

 

However... You said you replaced your HDD with an SSD, and removed the HDD... So you can put in your HDD again, format it, and do a fresh/clean install of windows. (you keep your current installation on your SSD) If the problem gets fixed, you know what you have to do. If the problem still exists, start praying. (won't do jack sh*t, but well, your screwed then anyways)

I'm following some steps from what you linked atm. Doing a system scan atm.

The thing is before I added this SSD. I barely started getting reboots when I started playing H1Z1. I played 6 hours after I bought it and it rebooted. Then it kept rebooting like every hour or so. But it wasn't rebooting for any other game nor was it giving any memory dumps at all. Then eventually I got a reboot while playing Rust. I then swapped in the SSD and cloned the HDD to the SSD thinking maybe the HDD was on its last leg. I kept getting reboots while playing H1Z1. But for the first time now while idle I got a full BSOD with memory dump and all.

[NewbixCube]

25 minutes ago, Dutch-stoner said:

In one of those bluescreen reports, it mentioned wof.sys. Not knowing what this file was, I used google. Since I am dutch, I got lots of dutch results, such as this one:

 

http://www.solvusoft.com/nl/files/bsod-blauw-scherm-fout/sys/windows/microsoft-corporation/microsoft-windows/wof-sys/

 

(maybe it will get transformed into your native language)

 

My point is: with the ! icon, there was a list of 7 bullets with different causes. 5 out of them 7, are software/drivers related issues. One mentioned memory (ram) failure, and the other mentioned a failing harddrive.

 

There are tools to check the health of your memory and hard drive. If it's not those two components, I would suggest a fresh install of windows to fix this problem.

 

*DISCLAIMER: just pulled this info from google, no guaranteed succes!

It's telling me to use WinThruster to search my registry for wof.sys and errors. How trusted is this program? Or can I use something else like CCleaner?

[Guest]

This site was a random google result when I tryed to find out what wof.sys is. I would NEVER install any kind of "registry search program", because they are usually all crap/doing nothing or asking for your money. If you have to, I would use CCleaner.

[Guest]

Btw, I only linked that page to inform you your hardware is mostlikely just fine, and that it would be "a" software/driver problem. If it were my computer, I would try to install a fresh new OS on that (removed) HDD, and try to test if the system will remain stable. In my opinion, it's hard to fix some random .sys error/crash.

[NewbixCube]

Just now, Dutch-stoner said:

Btw, I only linked that page to inform you your hardware is mostlikely just fine, and that it would be "a" software/driver problem. If it were my computer, I would try to install a fresh new OS on that (removed) HDD, and try to test if the system will remain stable. In my opinion, it's hard to fix some random .sys error/crash.

Sadly whenever that HDD is plugged in it sounds like a grinder. So I want to reframe from plugging it in ever again... If I were to reinstall windows but use the option to keep games and other files I wonder how long it would take with 300 - 500 kbs lol

[Guest]

An HDD which starting to sound like a grinder, is a dying HDD... And with that new info, here is what I think has happened...

 

-You were using your computer with failing harddrive.

-There was a read/write error, which caused a crash.

-The problem got ignored, because the piece of info was read incorrectly, maybe auto/copied to a different spot on your HDD, while keeping the problem. (the read error just stayed there)

-When cloning/migrating, the corrupt file was also copied, including the errors.

-You still have your errors, and since you don't want to reinstall, you are going to keep this problem.

 

Considering windows only reported the crash, and not a warning error of any kind (or you forgot to mention this to us), windows does not see this error in advance, making a windows recovery attempt, likely to fail. (as-in fix your problems)

 

I would still try to use the failing HDD as a test, because a clean install might work for a while. Just long enough for you to notice an improvement.

 

Also, when your harddrive REALLY fails, it will not burn your computer down. It will 99% sure not damage any other components. Using an HDD untill it does not work at all, is fine. (just keep dataloss in mind)

 

*PS: going to bed now.

[NewbixCube]

1 minute ago, Dutch-stoner said:

An HDD which starting to sound like a grinder, is a dying HDD... And with that new info, here is what I think has happened...

 

-You were using your computer with failing harddrive.

-There was a read/write error, which caused a crash.

-The problem got ignored, because the piece of info was read incorrectly, maybe auto/copied to a different spot on your HDD, while keeping the problem. (the read error just stayed there)

-When cloning/migrating, the corrupt file was also copied, including the errors.

-You still have your errors, and since you don't want to reinstall, you are going to keep this problem.

 

Considering windows only reported the crash, and not a warning error of any kind (or you forgot to mention this to us), windows does not see this error in advance, making a windows recovery attempt, likely to fail. (as-in fix your problems)

 

I would still try to use the failing HDD as a test, because a clean install might work for a while. Just long enough for you to notice an improvement.

 

Also, when your harddrive REALLY fails, it will not burn your computer down. It will 99% sure not damage any other components. Using an HDD untill it does not work at all, is fine. (just keep dataloss in mind)

 

*PS: going to bed now.

I did some CCleaning and a few other things. I'm gonna monitor to see if I get another BSOD. Then try using the new PSU, if it still occurs I'll bite the bullet and fresh install windows. Sounds prissy I'm sure but it's a REAL slow download with my current speeds especially when I'm not the only one on that net.

 

I appreciate the help and guidance on everything! I'll keep posted as the days go.