BSOD on start up.

[Lulubop]

I see, sorry. It reads 5/14/2009.

 

[Jonathan_King]

Great, let's hope the BSODs stop now.

 

[Lulubop]

No BSOD yesterday, but here we go again. *sigh*

 

[zigzag3143]

I see, sorry. It reads 5/14/2009.

And it still does in the most recent BSOD.

 

[Jonathan_King]

Time to test hardware.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Test hard drive: HD Diagnostic

See this tutorial on testing CPU: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Aug  1 13:28:31.814 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:47.844
BugCheck 1A, {41284, 1c93001, 0, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Aug  1 13:23:42.607 2010 (UTC - 4:00)
System Uptime: 0 days 0:30:33.012
BugCheck 34, {50830, fffff8800317e4b8, fffff8800317dd20, fffff8000289588c}
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+17c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x34
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[Lulubop]

I stressed tested my CPU with the Intel Burn test and it was said to be unstable. Not sure what to do now.

 

[Jonathan_King]

Test with Prime95, just to get a second opinion: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Are you overclocking at all? If so, restore to defaults. If not, make sure the BIOS settings are set to "Auto".

 

[cluberti]

According to the dumps, the CPU isn't overclocked:

3: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2666
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 30 Stepping 5
ProcessorNameString = REG_SZ Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz
Update Signature = REG_BINARY 0,0,0,0,3,0,0,0
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 300000000

However, I would have to second JK's suggestion of using Prime95 as a "second opinion" (I like that wording too). However, if you flunk out of Prime95, that would confirm the CPU is bad, or you have poor cooling, or a bum PSU, etc. You'll have to focus on your hardware at that point and determine for yourself how you want to proceed in attempting to fix it.

 

[Lulubop]

I will try Prime 95, I'm assuming I'll have to leave my computer on for the as long as the test take? No overclocking, and all the setting on BIOS are auto/default.

 

[Lulubop]

Sorry for the double post. I'm using Core Temp to see how hot the temperatures get, will the test stop automatically when it's becoming to hot, or should I stop when It gets to a certain temperature?

 

[Jonathan_King]

The Prime95 test will run indefinitely, until it errors out or you stop it. Let it run for at least 6 hours, unless it stops on its own sooner.

Use Speedfan to monitor your temps as you do.

SpeedFan - Access temperature sensor in your computer

 

[Lulubop]

Using Prime 95, the Temperatures were immediately in the Mid 90s c Which caused me to stop. They're about high twenties- Mid thirties when just browsing.

 

[Jonathan_King]

I wonder if that is the problem, then. Open up the side of your case, and first, clean out any dust. Then blow a fan inside.

 

[Lulubop]

Well this computer is about 2 weeks old, I opened it up no real dust or anything.

 

[cluberti]

I did some research, and it seems others have seen their i5 750s get up around the 91-92C mark under Prime95 load as well with the stock Intel cooler. If it runs that hot under load, unless they've done some massive engineering that processor is going to have a very short life if you ride it hard. According to Intel's docs on the part, the Tcase (maximum safe operating temperature) is ~72C, so 90C under load would indicate a very poor cooling solution (I'm guessing you're using the stock Intel cooler). There are folks out there who run the same CPU overclocked to 3+GHz and stay under 50C running Prime95, to give you an idea of how poor Intel's cooling solutions are.

 

[Lulubop]

I see, well yea I'm using the stock cooler. I will try to buy some Paste tomorrow and see if that helps, but I don't understand how that would be the cause of BS under a relatively light load since it usually only occurs around start up.

 

[cluberti]

You do realize that startup and shutdown are the busiest time for the CPU, with drivers causing interrupts as they load or unload, clearing the DPC queue backlog, handling all of the events and start (or shutdown) of apps and services, etc...? Assuming a relatively even (and minimal) CPU load during normal usage, startup and shutdown are the hardest times your CPU will face.

 

[Lulubop]

More BSOD. They're becoming more frequent. This is becoming quiet the headache.

 

[Jonathan_King]

Have you addressed the heat issue yet? Make sure you have plenty of ventilation in the case.

Open the side and blow a fan inside while you work.

 

[Lulubop]

Well my computer did not crash from any stress test, and during the intel burn test using the standard memory size opition my computer passed, though it did get very hot.

The first time this problem occurred about two weeks ago, I thought it was because of the memory so I used the Memok feature not realizing that ASUS advises to upgrade your BIOS after. So I'm wondering if this could be BIOS related? Also I feel the need to try and uninstall and reinstall the drivers for my GPU. I'll also look into the temperature situation. It seems as if I'm getting a BSOD every time now.