Start up/Run normal then freeze up and BSoD

[lTB]

Hi guys,
I am so glad to find out this promising helpful forum.
My pc have been working fine over a year and yet 2 days ago it begin to freeze up and crash after using for a while about 30-45 mins (actually depend on how much load it gets)
My system specs.
- Win 7 professional x64
- Originally installed
- Full retailed version
- 1 year old hardware system (i7- 2600k cpu, Asus P8P67 MLB, 16gb memory)
- Just re-intalled O.S (sadly also re-installed all drivers)

I did scheme through some of the solved topics and decided to run driver verifier, it would crash right away at start up, before getting to the log-in screen.
The error code that I have been able to capture during normal use (not while running driver verifier) is "0x0000000f4"
Attached file is the one created after running driver verifier.
Please help, I really do need this pc for work!
And really do appriciate your help.

 

[JMH]

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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



Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)


NB.
It appears you do not have SP1.
Please run the System Update Readiness Tool (SURT) and then update to SP-1

32 Bit

Download: System Update Readiness Tool for Windows 7 (KB947821) [February 2012] - Microsoft Download Center - Download Details

64 Bit

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2012] - Microsoft Download Center - Download Details

Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

 

[lTB]

Hi JMH,
I ran memtest overnight to get 5 passes.
Could you help to analyze this attached dmp file properly from the normal BSoD while in use.
If not, here is the failure code that I have been able to capture "0x000000F4 (0x0000000000000003.0xFFFFFA800E4A0060.0xFFFFFA800E4A0340.0xFFFFF800031CD240)
Should this code be hard drive related failure; since I just checked the preview on the crucial M4 SSD which I'm using, stated the same issue (would BSoD after an hour of using or so).
Testing with my old lappy's hard drive right now.
Hope it will not crash again.
Big thanks.

 

[zigzag3143]

Hi JMH,
I ran memtest overnight to get 5 passes.
Could you help to analyze this attached dmp file properly from the normal BSoD while in use.
If not, here is the failure code that I have been able to capture "0x000000F4 (0x0000000000000003.0xFFFFFA800E4A0060.0xFFFFFA800E4A0340.0xFFFFF800031CD240)
Should this code be hard drive related failure; since I just checked the preview on the crucial M4 SSD which I'm using, stated the same issue (would BSoD after an hour of using or so).
Testing with my old lappy's hard drive right now.
Hope it will not crash again.
Big thanks.

This one was a fairly rare code

This bug check results from a serious error in a driver or other system file. The file header checksum does not match the expected checksum.
This can also be caused by faulty hardware in the I/O path to the file (a disk error, faulty RAM, or a corrupted page file).

In addition to running verifier (and do that first) please run a chkdsk


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

 

[JMH]

Did you run Driver Verifier as requested?
Results?

You haven't installed SP1 yet.
It would be a good idea to do so asap.

 

[lTB]

It was the SSD!
I am seriously do not think that SSD will fail.
To JMH, yes I did run driver verifier, it will crash in normal boot on start up, it will not crash in safe mode on start up; however, I am not patient enough to wait for it to crash since I have already been kind of leaning to the possible defective SSD. Replaced with the old possibly still working hard drive, and it slows but run normal ever since no matter under heavy loads or idle.
Many thanks guys,
I have learnt a lot in here and will try to keep doing that.
One question though, do you think the "file header checksum does not match expected checksum" affected my SSD or is it caused by the bad SSD?

Best regards.

 

[zigzag3143]

It was the SSD!
I am seriously do not think that SSD will fail.
To JMH, yes I did run driver verifier, it will crash in normal boot on start up, it will not crash in safe mode on start up; however, I am not patient enough to wait for it to crash since I have already been kind of leaning to the possible defective SSD. Replaced with the old possibly still working hard drive, and it slows but run normal ever since no matter under heavy loads or idle.
Many thanks guys,
I have learnt a lot in here and will try to keep doing that.
One question though, do you think the "file header checksum does not match expected checksum" affected my SSD or is it caused by the bad SSD?

Best regards.

Good job and good luck from both of us.