Windows 10: Different BSoDs on New PC Build

I guess when you run option 7 again it'll give unrepairable errors? If so, run option 3 after mounting the ISO downloaded from my onedrive.

 

Sorry it took so long to reply, had to run some errands. Ran option 7 and it cam back with "couldn't find any integrity violations."

 

Alright, good *Smile

Assuming you ran option 7 in safe mode, no problems running in safe mode?

 

I didn't run it in safe mode *Shock

 

No problem, SFC in safe mode was a suggestion for in case your system would give a BSOD before SFC could finish *Smile

If another BSOD hits your system, run the DM Log Collector, upload a new zip and I'll have a look at it when I wake up *Smile

 

Sounds good. Thanks for all of your help and being patient with me.

 

All was going well today, and I launched and played No Man's Sky for a good 2 hours before my first BSoD. It was Faulty Hardware Corrupted Page. WhoCrashed pointed at the RAM being the culprit, but I ran the memory diagnostic and it said it was fine, but it had to restart, and then I got 2 more BSoDs, first as soon as I clicked the start button just after windows opened, and second time before the password screen even came up as it was still loading windows.Attachment 95738

 

Do you put a zip in a zip?

Assuming you ran the built-in memory diagnostics test, please run MemTest86+ for 8 completed passes.
8 passes for 8 GB takes about 8-10h, so recommendation is to run it overnight.






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 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.

 

No I didn't put a zip into a zip intentionally, I just ran the dm_log_collector again. I havent been deleting the old DM_logs though, so maybe that's what happened. Do you need me to attach a fresh one?

 

Deleting the old onces doesn't cause it. I've run the DM Log Collector myself often enough with many old onces present, it never happened.

Not until another BSOD occurs.

 

I was reading the manual again, and it looks like the dimm slots in my motherboard only support up to 4gb, and I have 1 8gb card in there. I'm thinking that's probably the cause of the memory issues. I ordered 2x 4gb that should be here Monday. I wish the motherboard came with the full manual instead of a little quick start guide style manual, it would've saved me so much trouble. I didn't even think to check for a full manual.

 

Alright, keep me posted *Smile

 

Well it's been a week since I installed the new memory, and I figured I should update this thread. Monday morning I ended up having about 5 more crashes, then my new memory arrived, I installed it, and I haven't had a single BSoD since. So I would say that it's confirmed, the issue was that my motherboard couldn't handle a single 8gb memory card, and once I switched to 2x 4gb cards everything worked the way it should. I'm just surprised that one issue could cause so many different BSoDs.

Thanks again for all your help and being patient with me. Hopefully this info can help someone else down the road. If I do end up having any other problems, I'll be sure to check here.

 

A problem with RAM can cause many problems, because of the Memory Management of Windows. This mechanism is very large and complicated and because of the complexity various of reasons can be behind corruption in the Memory Management making troubleshooting it sometimes difficult. The Memory Management is not only used by the RAM, but also the HDD & VRAM.