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

I recently built a new system with my father and he has been having random BSODs with always a different error from day one.

Unfortunately he tried to re-install so all I have is one .dmp file since the re-install.

0x7E dxgmms1.sys was the last one he encountered, I have an email with the other errors he got BSODs from:
0x7E aswmonflt.sys
0x1A ntoskrnl.exe
0x1A ntkrnlmp.exe
0x24 ntfs.sys
0x3B ntoskrnl.exe
0xF4 ntoskrnl.exe


His system specs are in my profile also.

He tested his RAM with memtest86 for 5 hours with no errors he said.

Thanks in advance.

There is only one crash dump, which is not very informative itself.

It also appears that you already have uninstalled Avast which did not help.
But you havent employed an antivirus back. Which is not healthy. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Now, as you reported for versatile BSODs, better we take a memory test. Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

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

Let us know the result. Further actions will be needed depending on the result.
___________________________________

Code:

BugCheck 24, {1904fb, fffff88007811d48, fffff880078115a0, fffff80002ac4fc4}

Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceExclusiveLite+54 )

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

It gives a prima facie assumption that there is something wrong from the part of the hardware; specially when it bounces back even after a clean reinstall.

entropical said:

I recently built a new system with my father and he has been having random BSODs with always a different error from day one.

If memtest86+ detects any error/red line, ask him to stop it there.

He just had another BSOD happen, I made him run the log tool again and attached it. Hopefully this one contains more useful information.

Since we are getting desperate I'll also attach two .doc files which were generated with the program WhoCrashed, maybe they will help troubleshoot this problem.

You enabled driver verifier too? Well tried! But DV caught MSE as the failure.

Code:

BugCheck C4, {91, 0, fffffa800c648b50, 0}

*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : MpFilter.sys ( MpFilter+17f4e )

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

That is not impossible, if MSE is not updated properly. But it will be astonishing that both the good AV products are failing there.

Those filters (both of MSE and AVAST) are storage filters. Plus the bugchecks show NTFS errors. As MX100 does not have any firmware update pending, we cannot say that the firmware is throwing the issue. Plus the conventional disc checks are not for solids.

If possible, can you install windows on a partition of the Hitachi disc or the Samsung disc? See how it goes. Let us know the result.

EDIT: Before doing it, take one more test. See how the computer runs with the system native AHCI controller. Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Uninstalled Intel Rapid Storage technology from Control Panel, there weren't any Intel devices left under IDE ATA/ATAPI controllers when I checked that next.
Now rebooting and if this does not solve it, we will assume it's the brand new SSD that's defective and install windows on one of the regular HDDs?

Thank you for your help.

EDIT: BSOD with Microsoft drivers, he's tearing his hair out and is gonna unplug the SSD and try Windows on one of the regular HDDs.

Will report back.

entropical said:

Now rebooting and if this does not solve it, we will assume it's the brand new SSD that's defective and install windows on one of the regular HDDs?

Yes, we need to take this try.
Some of th hardware components are failing. We tested the RAM which turned out to be good. But we cannot run the conventional disc check tools on a SSD, those are for spinners, not for the solids.

As there is a chance that the storage device is causing the problems, let us try any other disc as the primary disc. As there are two discs already, better let us use either one of them as primary.

EDIT: see next post, cried victory too early

This is probably way too early to tell but we think it's the SSD since the BSOD's disappeared now and they came instantly when installing his programs before.

He's gonna send it back for a refund and get a Samsung EVO 850 SSD instead. Don't really have faith in Crucial anymore.

Thanks for the help Arc, it's very appreciated and if we do get BSODs again I'll bump this thread (if appropriate?)