New Build, Multiple BSOD, Unknown error code

ddg5006 · 10 Mar 2014

Hello all,

I have just build a new computer, I was able to install windows without issue and everything went smoothly, but when I was installing drivers for the MOBO and installing programs while configuring windows the machine would lock up and BSOD, each time giving a different reason. This is a brand new build so i would suspect that it is most likely either the MOBO came faulty or bad PSU? I already ran Memtest86+ and memory came up clean. Anyway I processed the dumps and here they are, if anyone is willing to take a look at this I would greatly appreciate it. Thanks in advance.

Arc · 10 Mar 2014

Various different bugcheck codes.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

Code:

BugCheck 50, {fffffab0046ec6db, 0, fffff80002892dff, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df )

Followup: MachineOwner
------------------------------------------
BugCheck 24, {1904fb, fffff88001f176d8, fffff88001f16f30, fffff880012e0c27}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )

Followup: MachineOwner
-------------------------------------------
BugCheck 1A, {5003, fffff780c0000000, 6838, 78380000f06c}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+297b1 )

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

ddg5006 · 10 Mar 2014

So your suggestion is to run a ran test with at least 8 passes ? The previous test I ran came up clean but it was only 1 pass.

Arc · 10 Mar 2014

Yes, at least 8 passes. If you can run it for even more, that will be better.

ddg5006 · 10 Mar 2014

Ok i'll leave that running overnight and in the morning I'll check the results. But I think something else is going on also because I'm having problems installing things in windows, I just tried to install SP1 and it failed. Also i was having trouble installing chrome earlier but eventually I got it to take. Anything else I should look at beside the ram?

Arc · 10 Mar 2014

If the RAM is tested as good, your first try would be to have a Clean Reinstall - Factory OEM Windows 7 .....

If still it is the same, we will stress the other hardware one by one.

ddg5006 · 10 Mar 2014

ok, putting it to test now, we'll see if any error come up. Thanks for your quick responses. How do I set it for more than 1 pass? just leave it and it will keep going? also should I force multi-threading ?

ddg5006 · 10 Mar 2014

ok so i think we have an answer faster than expected, the first time I ran the test it went through with no problems, this time it hangs on the first pass. It gets stuck right there. I'm going to try and run it in fail safe mode.

Arc · 10 Mar 2014

Most of our senior members recommend the memtest86+ version 4.20. Give it a try?

Nothing more to do. Just leave the test on. It will run automatically till you abort it.

ddg5006 · 10 Mar 2014

ok its running now that I put in fail safe mode but I can use 4.20, I'll just have to make a new USB stick

Edit: Ok i made the new stick, 4.20, it isn't reading my ran timings correctly, is that in indication that there is deff a problem or is it because 4.20 isn't designed to read newer ddr3 ram ?

Check that pic on the next page.