BSOD Keeps Happening Every Night.

[IsLNdbOi]

Ok, so got another BSOD. First BSOD since I turned DV off. The whole time I had DV on I did not have any BSODs. I've attached everything I could find about this new BSOD.

 

[Vir Gnarus]

That definitely complicates things if it's not crashing when DV is on. Trying turning DV on again just to make sure. As for the dump file, I'm afraid this one, and future ones, will not be viable for finding a cause. Unless DV intervenes, we're at a loss. My only recommendation if DV doesn't kick in and BSOD the system, is to just keep providing us new crashdumps and run a battery of hardware tests, and hope something comes up.

Memtest86+: 7+ passes (all tests ran once = 1 pass)
Prime95: Torture Test on Blend, overnight; follow up with Torture Test on Large FFTs, overnight.
Seatools: All tests except Long and Advanced.

Other possible hardware that can typically cause intermittent and spontaneous BSODs like this is the motherboard and the power supply. Make sure chipset drivers for the mobo are updated as well as BIOS. As for PSU, only possible way to test it is to swap it with another one and test stability.

 

[IsLNdbOi]

Another BSOD. First one I've seen that said:
Kernel_Data_InpageError

 

[Vir Gnarus]

Hmm, if you can get me the MEMORY.DMP file (in Windows directory) for this one it may be of assistance. Of course, that's provided you haven't crashed since, otherwise it'll just be the kernel dump for the most recent crash.

Often, however, kernel inpage errors are conducive of some form of hardware failure. It means something bugged out in the crosstalk between RAM and disk, which means either RAM is at fault, the motherboard is at fault, or the disk itself is at fault. Hardware testing will be needed to discern which part it is (though mobos cannot be tested). This could've also been just from some pool memory corruption caused by some misbehaving driver writing over memory it's not supposed too. Unfortunately, Driver Verifier was unable to help in our situation.

If you can provide that kernel dump it may shed a bit more light on this. I won't be able to find just what caused the problem, but I may be at least able to determine how it was caused.

 

[IsLNdbOi]

New BSOD.

 

[IsLNdbOi]

Hmm, if you can get me the MEMORY.DMP file (in Windows directory) for this one it may be of assistance. Of course, that's provided you haven't crashed since, otherwise it'll just be the kernel dump for the most recent crash.

Often, however, kernel inpage errors are conducive of some form of hardware failure. It means something bugged out in the crosstalk between RAM and disk, which means either RAM is at fault, the motherboard is at fault, or the disk itself is at fault. Hardware testing will be needed to discern which part it is (though mobos cannot be tested). This could've also been just from some pool memory corruption caused by some misbehaving driver writing over memory it's not supposed too. Unfortunately, Driver Verifier was unable to help in our situation.

If you can provide that kernel dump it may shed a bit more light on this. I won't be able to find just what caused the problem, but I may be at least able to determine how it was caused.

The MEMORY.DMP file is there, but it's 700MB AND has a little lock icon over it. Saved a copy of it on my desktop though.

 

[IsLNdbOi]

Vir Gnarus, what do I do with this large MEMORY.DMP file?

 

[centaur78]

Hi upload it to dropbox or skydrive and post a link here

 

[Vir Gnarus]

Make sure to archive it first. Zipping it up using zip, rar, 7z, etc., will greatly reduce the size. Not enough to upload to our site, however, but should dramatically speed things up.

EDIT: Wait, hold on that. If you didn't save this MEMORY.DMP file somewhere else, it probably already was overwritten by the most recent crashdump, which was a 0x1A crash. These are worthless to us, regardless if it's a kernel dump or not. If you didn't save the kernel dump prior to having this most recent crash occur, then you'll have to wait. Send us more minidumps on newer crashes. If I find one that looks appealing, I'll ask you to zip it up and send it to us.

 

[IsLNdbOi]

I did save it before another BSOD / crash happened. I copied it to the desktop. I just have to find a place to upload it.

 

[Vir Gnarus]

Mirrorcreator.com is a good option. it's a metaupload site that will upload it simultaneously to multiple filesharing sites so at least one of them will work.

 

[IsLNdbOi]

Here's a link to the memory dump file:
https://www.dropbox.com/s/l795wzj9dtifcdf/Memory Dump.zip

 

[IsLNdbOi]

Anyone get a chance to look at the dump file?

Also, had another BSOD today.

 

[IsLNdbOi]

Anyone been able to look at the dump file?
https://www.dropbox.com/s/l795wzj9dtifcdf/Memory Dump.zip

Also, I don't know if this will help, but Firefox has been crashing ALOT too. When I setup this system, I configured Firefox to put its cache in RAM instead of on my SSD.

ALSO, I setup a static 2GB pagefile on my secondary SSD instead of on my main SSD (the C drive) and turned off the system managed pagefile on the C drive.

 

[Vir Gnarus]

Sorry skip, long weekend. I'll take a look at it now.

 

[Vir Gnarus]

Uh oh, the file's broken. CRC check during extraction failed, meaning that the file probably didn't get uploaded to the site correctly or didn't get shoved into the archive properly. Unfortunately I can't work with this. We'll need to try at another kernel dump. :|

Make sure after you shove it in the archive to do a Test, then when you upload it, download it and run a Test on it again to ensure it's been uploaded successfully.

 

[IsLNdbOi]

Ok, had two of the "Pagefault in Nonpaged Area" BSODs in the past two hours.

I'm attaching the mini dump files and links to the big dump files.

The big dump files RAR'd:
https://www.dropbox.com/s/phjlrqqcjg1o7fy/Memory%20Dump.rar
https://www.dropbox.com/s/9dq939bq5oxt0r0/Memory Dump 2.rar

un-RAR'd:
https://www.dropbox.com/s/ycmcr2tiop7vwu8/MEMORY.DMP
https://www.dropbox.com/s/32atlw01c869fxz/MEMORY 2.DMP

 

[Vir Gnarus]

Thanks. I'll look at em at my earliest convenience. In the meantime, if you haven't already, I recommend turning Driver Verifier back on. At the very least if it doesn't cause your system to crash it'll at least keep it stable for the time being.

 

[IsLNdbOi]

Thanks. Looking forward to what you may or may not find!

 

[IsLNdbOi]

Do you think the frequent Firefox crashes, the modifications I made (placing Firefox's cache AND the Windows pagefile in RAM) have anything to do with these BSODs or is it most likely a driver issue?