Random BSOD errors, new custom build system, tried reformat.

Now, both the crash dumps are pointing to teh same things with two different bugcheck code.

One ....

Code:

BugCheck 3B, {c0000005, fffff800030e2e36, fffff88002bcbec0, 0}

Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+46 )

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

Code:

fffff880`02bcb518  fffff880`01a21572Unable to load image snapman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
 snapman+0x21572

Code:

fffff880`02bcb748  fffff880`018f8a01Unable to load image fltsrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fltsrv.sys
*** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys
 fltsrv+0x2a01

The other .....

Code:

BugCheck 24, {1904fb, fffff880081e46a8, fffff880081e3f00, fffff880012a373b}

Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenAttributeCheck+eb )

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

Code:

fffff880`081e3f48  fffff880`019c0d2fUnable to load image fltsrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fltsrv.sys
*** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys
 fltsrv+0x4d2f

Code:

fffff880`081e4538  fffff880`01a21633Unable to load image snapman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
 snapman+0x21633

The failing modules are ....

• Driver Reference Table - fltsrv.sys
• Driver Reference Table - snapman.sys

So you can see, bot are Acronis. And, all the Acronis programs contribute to BSODs very frequently.

See how it goes minus Acronis? You may have some other backup choices like ....

• Download Macrium Reflect 6.0.482 - FileHippo.com
• Download AOMEI Backupper Standard 2.2 - FileHippo.com

Both are very good programs and they mostly does not cause any issue.

I am really feeling bad that a lot of things are coming problematic for his computer.

This BSOD happened while extracting a WinRAR archive and the second one whilst trying to boot on one stick of RAM.

We also found out that we left some branding stickers on the RAM sticks which we have now removed, maybe they caused them to overheat? They came off without residue or problem so they probably were meant to be removed? Probably not since it would have shown errors in memtest86+ then but who knows.

For troubleshooting someone else recommended us to test with one stick of RAM, which he did and put it in the slot according to his motherboard manual but that resulted in a BSOD on boot he said. I asked him: did you test the other stick afterwards but no, he put both RAM sticks back in their original slots.


Thank you!

It BSODs on anything and everything.

I would ask for more eyes on this issue, to make it sure that I am not missing anything.

Hello entropical, let me see a few things if you don't mind. Would you please go into bios and give me the values of the +12V, +5V and +3.3V. Also, while in bios, please look in the Advanced tab, Sata configuration and tell me what the Sata configuration is. Also tell me if your BIOS Version is 2202..

Also, please , if you don't already have it, download and install CPUz CPU-Z | Softwares | CPUID and post screenshots (Screenshots and Files - Upload and Post in Seven Forums) of the CPU tab, the Mainboard tab the Memory tab and the SPD tab. On the SPD tab, in the upper left you can select each Dimm Slot. Please just post screenshots of just the Dimm slots with ram in them.

While we are posting screenshots, Please click start, type Device manager, click on Device Manager and post a screenshot of it for me. Also please post a screenshot of Disk Management https://www.sevenforums.com/tutorials...-capture-image

Also, please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

All of those screenshots may take 2 or 3 posts, which is fine with me. Hopefully we can find something. But, from what I can see, I would agree with Arc that it looks a lot like a ram problem.