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

entropical · 20 Feb 2015

Alas, cried victory too soon, he just got hit with a new BSOD on a fresh install on the regular HDD (Samsung)

Attached a new log. Almost crying here :)

Arc · 20 Feb 2015

Two different head to head BSODs, two different bugcheck codes.

Code:

BugCheck 1A, {41284, 7fef9541001, 48, fffff70001080000}

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

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

Code:

BugCheck 1E, {ffffffffc0000005, fffff80002ecadac, 0, ffffffffffffffff}

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

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

That is the sign of failing memory. We tested the RAM, it is free from errors. We replaced the HDDs to, which will take proper care of pagefiles.

Now what remains there that can throw such issues is the motherboard. But we cannot test it. In this situation it will be better to RMA the motherboard.

New motherboards may be faulty. I also sent a brand new motherboard to RMA just today. Today [15]

entropical · 20 Feb 2015

That's depressing to hear.

Do you perhaps have some tips for unseating the heatsink from the motherboard? We have never done this before and I guess we should buy some sand paper to scratch off the pre-applied thermal paste that was on the boxed cooler and then reapply fresh one once the new/repaired motherboard arrives, or can we use the pre-applied one again?

I'll try Google myself but any tips are welcome.

Arc · 21 Feb 2015

Have a look at this video? Its not tough, but little tricky. Its for LGA775, but the procedure is the same for any pin.

It is better to apply new thermal paste.

My board is back within 24 hours. :) I have to report the service center after using it for 24 more hours.

entropical · 21 Feb 2015

Great, that helped us, what was I thinking sand paper lol!

So for now, nothing to report other than he got a new SSD and new motherboard and is installing Windows as we speak. I won't be around for him to Skype with tonight since I'm staying at my parents-in-law for the night.

I'll update tomorrow or the day after on if it's finally fixed

Greetings and thank you, this cannot be said enough!!!

Arc · 21 Feb 2015

Ok, have a good time at the in-laws place. :)

entropical · 22 Feb 2015

Hi again, Arc!

Had a good time at the in-laws and my father has been using his new motherboard and SSD for about 24 hours now quite intensively without any BSOD's.

Only problem he had with the new ASUS Z87-C motherboard is that it would restart automatically after initiating a shutdown but disabling Wake on Magic Packet and Wake on LAN resolved that.

Since my father and I rushed to the conclusion that it was the Crucial MX100 256GB SSD causing the BSODs, I contacted customer support from the shop where I bought it as a present for him and they said I would get my money back when I send it back. No loss there.

The faulty motherboard I don't know about that since he didn't wait and just bought a new one, he's trying to get shop credit for it instead of a repaired unit.

Let's keep our fingers crossed this is the end of our troubleshooting days for now.

Have a nice day Arc, maybe they should implement a tipping system or something 'cause thank you really only goes so far.

Arc · 22 Feb 2015

Fingers crossed. :)

Let us know for any further BSOD.

entropical · 23 Feb 2015

Oh boy, here's a new .dmp file for you if you're interested Arc... fingers crossed didn't help.

It occured while installing drivers for the printer this time.

So by now it's a complete new system minus the RAM... father is losing his mind.
It can only be the RAM by now, don't you think as well?

I think I made a critical error while buying it to not buy a set of so called "matched" RAM but just 2 seperate units in seperate boxes.

Also, it's not listed on the ASUS .pdf file of Qualified Vendors (http://dlcdnet.asus.com/pub/ASUS/mb/...M_QVL_0730.pdf)
Corsair 2x4GB CMV4GX3M1A1333C9 is not listed as far as I can tell

Thanks.

Arc · 23 Feb 2015

Apparently it is ESET that is conflicting with the storage filters.

Code:

fffff880`026b38e8  fffff880`03d7dbb9Unable to load image ehdrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ehdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys
 ehdrv+0x1dbb9

Driver Reference Table - ehdrv.sys

Code:

fffff880`026b4208  fffff880`03cb4a00Unable to load image eamonm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
 eamonm+0x33a00

Driver Reference Table - eamonm.sys

ESET is a brilliant antivirus. But it is the second time within this week I am seeing ESET is causing such an issue. It is a bad luck only.

Uninstall ESET on a test basis. How do I uninstall or reinstall ESET Smart Security/ESET NOD32 Antivirus? - ESET Knowledgebase
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Let us know how it goes.