Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD every 20 or so minutes. what do?

17 Apr 2014   #1
A Taco Stand

Windows 7 Home Premium 64
 
 
BSOD every 20 or so minutes. what do?

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.


My System SpecsSystem Spec
.
17 Apr 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hi A Taco Stand.

All the crash dumps are identical.
Code:
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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
17 Apr 2014   #3
A Taco Stand

Windows 7 Home Premium 64
 
 

Quote   Quote: Originally Posted by Arc View Post
Hi A Taco Stand.

All the crash dumps are identical.
Code:
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   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   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   Tip

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?
My System SpecsSystem Spec
.

17 Apr 2014   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by A Taco Stand View Post
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.
Quote:
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:

testSlot1Slot2
RAM1ErrorError
RAM2GoodGood
It is a RAM, a bad RAM.

But if you have got a result like that:

testSlot1Slot2
RAM1ErrorGood
RAM2ErrorGood
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.
My System SpecsSystem Spec
18 Apr 2014   #5
A Taco Stand

Windows 7 Home Premium 64
 
 

Quote   Quote: Originally Posted by Arc View Post
Quote   Quote: Originally Posted by A Taco Stand View Post
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.
Quote:
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:

testSlot1Slot2
RAM1ErrorError
RAM2GoodGood
It is a RAM, a bad RAM.

But if you have got a result like that:

testSlot1Slot2
RAM1ErrorGood
RAM2ErrorGood
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?
My System SpecsSystem Spec
18 Apr 2014   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Yes, you need to buy new RAM. When buying, make it sure that you are getting the exactly same one of the existing one.
My System SpecsSystem Spec
18 Apr 2014   #7
A Taco Stand

Windows 7 Home Premium 64
 
 

Quote   Quote: Originally Posted by Arc View Post
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?
My System SpecsSystem Spec
18 Apr 2014   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

I think different timings of RAM modules should cause problems.
My System SpecsSystem Spec
Reply

 BSOD every 20 or so minutes. what do?




Thread Tools




Similar help and support threads
Thread Forum
2 minutes to boot to desktop and minutes more fot hard drive activity
ever since I got the laptop it takes almost 2 minutes to boot to the desktop. It then continues to show hard drive read activity without blinking for 6+ minutes. What tests can I run to find out the cause? this happened since the first boot times and even after factory resets. ...
Performance & Maintenance
BSOD after a few minutes (5 to 55 minutes) with Samsung SSD 840 EVO
Hi. I have successfully cloned my existing OS over to the SSD 840 EVO using Samsung magician. My OS boots fine with the SSD 840 EVO but crashes several minutes after startup. Crashes can happen from 5 to 50+ minutes after start up. The crashing process happens slowly, starting with the mouse...
BSOD Help and Support
BSOD every few minutes
hi, i keep getting BSOD every few minutes ranging from start up to 30 mins.im getting different reports all the time.Can you please help. im using HP laptop. i have tried system restore but still the same.so i have installed a fresh win7 sp1 64bit. any help would be much appreciated....
BSOD Help and Support
BSOD every 10 minutes
I have been getting the BSOD every 10 minutes from last few days. I get the following error: Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional information about the problem:
BSOD Help and Support
New Rig BSOD within 15 minutes
Dear All, I just built a Rig (after nearly 8 years of my last rig) with the following specs: i7 950 (Stock 3.07) Kingston HyperX 2000 CL9 @2133 (Stock) 6GB (Triple Channel) Asus P6X58D-E Corsair HX1000 Galaxy GTX480 Super Overclock x2 SLI (but currently using one only to setup system,...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:20.
Twitter Facebook Google+