BSOD every 20 or so minutes. what do?

[A Taco Stand]

My computer has been crashing randomly about 20 after I start it up for the last few days and I've barely been able to get a complete crash dump before it crashes. In fact it crashed once while I tried posting this. I think it's either a virus or bad driver but I don't know for certain any help is appreciated thank you.

 

[Arc]

Hi A Taco Stand.

All the crash dumps are identical.

BugCheck 1A, {403, fffff68000032b80, fda000012d6f6867, fffff6fc0096b7b0}

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

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

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.

If it does not show any error, 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.

 

[A Taco Stand]

Hi A Taco Stand.

All the crash dumps are identical.

BugCheck 1A, {403, fffff68000032b80, fda000012d6f6867, fffff6fc0096b7b0}

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

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

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.

If it does not show any error, 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.

I ran the RAM memtest and I immediately began to see errors/redlines so the problem is the RAM. Do i run the driver verifier now?

 

[Arc]

I ran the RAM memtest and I immediately began to see errors/redlines so the problem is the RAM. Do i run the driver verifier now?

No. Run Driver Verifier only if memtest does not show errors.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

Otherwise you may change the entire kit with a new one, to save the time. But the risk factor of malfunctioning slots will remain there.

 

[A Taco Stand]

I ran the RAM memtest and I immediately began to see errors/redlines so the problem is the RAM. Do i run the driver verifier now?

No. Run Driver Verifier only if memtest does not show errors.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

Otherwise you may change the entire kit with a new one, to save the time. But the risk factor of malfunctioning slots will remain there.

I did the second step and found that it was faulty RAM stick.Do i need to buy a new one?

 

[Arc]

Yes, you need to buy new RAM. When buying, make it sure that you are getting the exactly same one of the existing one.

 

[A Taco Stand]

Yes, you need to buy new RAM. When buying, make it sure that you are getting the exactly same one of the existing one.

like this one? it runs the same frequency and voltage the only real difference i see is the timeing would that be a problem?

 

[Arc]

I think different timings of RAM modules should cause problems.