Random BSOD how to fix?

[Sathle]

I uploaded the files about the my BSOD. This computer is fairly new. My friend helped me build it since this is my first custom pc, but recently it has been crashing and I don't know how to fix it.

 

[Arc]

Two BSODs, two are totally different.

BugCheck 1A, {411, fffff680001f7888, 87a0000196cfc884, effff680001f7889}

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

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

BugCheck DE, {2, fffff8a0117116a0, fffff8a011079f51, 1501ec8c0}

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

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

Both the bugchecks are memory related issue. It is not necessarily a bad RAM; some other things may contribute in it.
But the first place to start troubleshooting is to test the RAM. 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. A camera snap of the memtest86+ screen before closing the program would be a great feedback.

 

[Sathle]

I'm following the instructions, but its not conducting the test when the computer is booting up. It tells me to configure in the BIOS, and I think that's where I'm stuck because I don't know how to access that. There's no boot up option and my computer boots up in like 4 seconds so either I missed it.. or I'm not pressing the right keys. Is there a way I can access the BIOS through the command prompt or something? I tried looking some up, but they don't work.

 

[BorisTheAnimal]

Hello Sathle.

Could you please tell us your motherboard make and model?

 

[Arc]

Hello Sathle.

Could you please tell us your motherboard make and model?

SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H97M-D3H
BiosVersion = F7
BiosReleaseDate = 08/03/2015
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.

 

[Arc]

I'm following the instructions, but its not conducting the test when the computer is booting up. It tells me to configure in the BIOS, and I think that's where I'm stuck because I don't know how to access that.

To enter into BIOS setup, you need to tap "Delete" key on the keyboard.

But changing the boot order in the BIOS is not a must. Better you use the Boot Menu Key (F12 for you) to guide the computer to boot from the installer.

BIOS Setup and Boot menu Key ....

View attachment 382900
​

Boot menu ....

View attachment 382901
​

When you are on the Boot Menu, use the scroll keys to select the device (CD/USB containing memtest86+) to boot from.

 

[Sathle]

Ok, I'll give that a try. Thanks for the help btw!

 

[Sathle]

Ok I got it to run the test. It's doing that now, do I wait for when the bottom right where it says pass and errors for pass to be 8? and then exit? It turned out that restarting doesn't bring up the boot menu. Realized I had to shutdown before starting it back up. It does look like it will take awhile, like the instructions said.

 

[Arc]

If it starts showing errors/red lines, take a camera snap and close the program.
Look at these three places ....

View attachment 382922​

Yes, 8 passes will take a long time to be completed. You need to have patience.

 

[Sathle]

There aren't any errors after 8 passes, I will upload a picture this afternoon.

 

[Arc]

There aren't any errors after 8 passes,

OK, next enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Sathle]

I'll do that later tonight or tomorrow then, since I need the computer today. Or can I run the driver and use the computer at the same time?

 

[Layback Bear]

Please read the tutorial again to make sure your settings are correct.

From the tutorial.

After a reboot, driver verifier should be enabled. Use your computer as you normally would, although expect frequent BSODs if there are driver issues. If the system doesn't crash after 24 hours, disable driver verifier.

 

[Sathle]

So it's been about 24 hours since I enabled driver verifier and no BSODs. If I'm overloading the drivers, there should be more reason to crash compared to when it runs normally. I don't detect any lag either. Actually, a concern I may have is that this may be a hardware problem. Can these tests pinpoint hardware issues? Or maybe I'm access memory that isn't there?

 

[Arc]

Driver verifier did not cause any lagging? That's abnormal.

But if DV did not cause any BSOD, then yours is not a driver related issue. Plus, RAM is not failing, as you stated.

Now what may cause memory management errors other than the RAM and any driver? It may sound bad, but that might be the memory controller, a component of the motherboard.

But we cannot test the motherboard. Moreover, the memory controller errors should kick in during memtest86+ test.

So, it is becoming very hard to detect what may be causing the issue.

IMHO you should go for a clean reinstall to ensure that things like system services/native drivers/third party drivers etc are not anyhow contributing to the BSOD.

 

[Sathle]

Would setting it back to factory settings help? Would that cause me to have to reinstall all the drivers again?

 

[Arc]

Would setting it back to factory settings help? Would that cause me to have to reinstall all the drivers again?

If you do the factory restore, it will assume loads of old drivers.
A clean reinstall is always good.

 

[BorisTheAnimal]

I just saw on the Gigabyte Support site that there is a Beta BIOS available for his motherboard and the fix would be memory compatibility, would it be a smart thing to update even though it is in Beta stage, on the other hand what I've understood from reading through this thread the problem may be with the RAM.

What do you think Arc?

 

[Arc]

This should be a good shot, mate. But I am afraid of only one thing that if by any chance the BIOS update does not go as expected, I will not be able to control the situation.

EDIT: Sathle, can you apply the RAM in the other (unused) channel? Does it change anything?