Solved Month worth of BSODs (at least twice a day)

[terryp1973]

Hello, I hope someone can help me with this never ending problem!


I have had a months worth of BSOD errors. Happening roughly twice a day and mostly when the computer has been idle but not always. The culprit shown on the majority of the minidumps is ntkrnlmp.exe but as you will see not always.


Thanks in advance,


Terry

 

[HonorGamer]

Hello,

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

DT been known to cause problems with Windows 7. Please uninstall.

Probably caused by : [COLOR="Red"]hardware[/COLOR] ( Ntfs!NtfsRestartIndexEnumeration+89 )

I've been seeing a lot of hardware and memory corruption/management. To be safe. Lets do a full hardware check.

BugCheck 0x124

You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for the crash.
​

Coutesy of: writhziden

After you do this, post back the results, and if it isn't fixed yet, we will continue from there.


EDIT: Something else I found which could be the problems.

AsIO.sys                    Mon Dec 17 01:11:49 [COLOR="Red"]2007 [/COLOR](47663D55)

This driver belongs to the program Asus PCProbe Utility, known to cause issues. Please remove it.

RtNdPt60.sys                Mon Dec 10 18:49:52 [COLOR="red"]2007 [/COLOR](475DFAD0)

Drivers before 2009 are known to cause problems on windows 7 machines. Please update: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=10&Level=3&Conn=2

-Gamer

 

[Thedoctor44]

There are a lot of dump files with different possible causes so first thing is first.
Lets rule out most hardware components.

The hardware piece that sticks out the most at this moment is the hard drive.

[COLOR="red"]BugCheck 24[/COLOR], {1904fb, fffff8800be3e038, fffff8800be3d890, fffff88001a600d0}

Probably caused by : [COLOR="Red"]hardware[/COLOR] ( Ntfs!NtfsAllocateRestartTableIndex+60 )

Bugchecks 0x24 consist of faults with the ntfs file system.

Please run a disk check by following these instructions.

http://www.sevenforums.com/tutorials/433-disk-check.html

After that is complete please open the elevated command prompt (run as administrator) and type sfc /scannow
If it finds errors then reboot and scan again (Do this three times in total.)

Then run SeaTools to see if your HDD is failing.
Follow these instructions.

http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

You are getting 0x3B bugchecks as well which are caused by lots of things but mostly caused by graphics drivers, however a faulty GPU can cause such errors so I think ruling it out should help.
Follow these instructions.

http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Lastly please run Memtest86 for at least 8 passes to see if you RAM is failing.
Please run it for at least 8 passes.
Follow these instructions.

   Warning

Most, if not all stress test applications aren't fail safe so please monitor temperatures.
I recommend a program like HWmonitor.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Post back the results.

 

[terryp1973]

Thanks for the help and I think I know what is causing the BSODs. First I ran the Prime95 and received the below on at least three of the CPUs twice.


[Apr 28 18:52] Worker starting
[Apr 28 18:52] Setting affinity to run worker on logical CPU #4
[Apr 28 18:52] Beginning a continuous self-test to check your computer.
[Apr 28 18:52] Please read stress.txt. Choose Test/Stop to end this test.
[Apr 28 18:52] Test 1, 6500 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
[Apr 28 18:53] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Apr 28 18:53] Hardware failure detected, consult stress.txt file.
[Apr 28 18:53] Torture Test completed 0 tests in 1 minutes - 1 errors, 0 warnings.
[Apr 28 18:53] Worker stopped.

Then I ran Memtest86+ and on the first test it locked up around 9 minutes. I thought it may be a fluke and ran the test again and the test stopped around 9 minutes again and gave me errors (see the attached picture). I ran it again and it locked up around 9 minutes again.

Now I guess the next step is to find out what stick(s) is causing the issue. Right? Basically test each one individually with Memtest86+, right? All of the memory is pretty new. Bought them back in December.

Thanks,

Terry

 

[Thedoctor44]

Well the reason it's probably crashing in memtest is because Prime95 has detected a fatal hardware error.
Did your PC actually crash during Prime95?

It sounds very much like a CPU fault, if the CPU is failing then a replacement is needed.

Upload the stress.txt file in your next reply.

 

[terryp1973]

Ummm....doesn't sound good. While running Prime95 the computer did not crash and I ran the blend test at least 4 times with the same type of errors that are located in the "results.txt".

Of further note, I also ran the first test "Small FFTs" for at least 3 hours and did not get an error. Only the "blend test" came back with errors.
I have attached the "results.txt". Is that what you need? The "stress.txt" located in my folder just has a FAQ and other questions and answers in it.

 

[terryp1973]

After I posted my last response I ran the "In-place large FFts" test and about a minute in I received a BSOD. Ran the test again after re-boot and didn't get a BSOD but it did log an error. I have attached that file to this post.


Thanks,

Terry

 

[Thedoctor44]

Please upload the stress.txt file.
And upload the new dump file that you received whilst running the test.

 

[terryp1973]

OK, here is the latest minidumps. There are three minidumps in the zip file attached. The first one in the zip file was after running the "In-place large FFts" stress test. The other two are from the BSODs I had in the mean time.

I am a bit confused on the stress.txt. The only stress.txt I have is in the Prime95 directory and is just has FAQs and other information about what to expect when you run stress tests. Can you help in this matter?

Thanks,

Terry

 

[Thedoctor44]

Sorry I've been busy.
You should replace the CPU if fatal hardware errors have been detected.
Does it still crash on memtest?
I recommend running it again and see if errors come up again.

 

[terryp1973]

Memory Test

Sorry been real busy getting ready to move that I just got to testing each individual stick (4 total) of memory last night. I could not duplicate the problem I had last time when I had all 4 sticks of memory connected. I then installed all of the memory back into the computer and ran MemTest86+ again but it did not lock up nor did it give any memory errors. The computer has been up almost 24 hours with no BSOD. If I go another 24 hours I will mark the thread as solved.

Thanks for all your help.

Terry