Still more BSOD

[hegeron]

I posted a while back in this thread http://www.sevenforums.com/crashes-debugging/135166-bsod-constantly.html#post1161865 and have been following the helpful suggestions.

I've changed the video card and reduced temperatures and there's no overclocking. I ran furmark (which is why I changed the video card).

I'm still not sure how long to run stress tests on the CPU for but I've run them for an hour without issue (max temp around 60)

I ran memtest and the windows memory diagnostic without issue.

At this point I imagine it's a hardware failure but if t is I'm not certain what's failing

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64 bit
- the original installed OS on the system? Yes
- an OEM or full retail version? OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 1.5 Years
- What is the age of OS installation (have you re-installed the OS?) Never reinstalled

 

[DeanP]

Hello hegeron and welcome to Seven Forums,

BSOD blames on your hardware. I would test your hardware for errors.

RAM - Memtest86+: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
- Do this overnight.
- Run at least 7 passes (this will take 6-8 hours)
- To burn .iso, use your current CD burning program or use Isorecorder, Imgburn to burn .iso to CD
- Post back snapshots/results when the test is done

CPU Stress Test: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html
- Read the posts in CPU Stress Test Tutorial for more information.

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80064a18f8, 0, 0}

Probably caused by : hardware

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

If you need any help or want to ask a question - let us know.

 

[hegeron]

Hi there

I ran furmark for the video card and it levelled out at 87-88 degrees celsius.

I'm not sure if that indicates an overheating issue or not

 

[Jonathan_King]

No, that's fine for a GPU.

I'm more concerned about the CPU; do run Prime95 as DeanP suggested.

Finally, make sure SPTD is removed; it has caused BSODs that seems like hardware. It is a component of Daemon Tools, Alcohol 120% and Alcohol 52%, and perhaps a couple other programs. I am not seeing SPTD in any crashes later than January 25, nor do I see any such programs installed. I am assuming you uninstalled it, but if not, please do so.

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 30 22:05:30.551 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:08.675
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 30 19:56:31.424 2011 (UTC - 5:00)
System Uptime: 0 days 4:18:45.548
Probably caused by : atikmdag.sys ( atikmdag+90817 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+90817
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Jan 29 03:30:37.974 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:08.098
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan 26 02:19:39.487 2011 (UTC - 5:00)
System Uptime: 0 days 0:17:07.502
Probably caused by : intelppm.sys ( intelppm!C1Halt+2 )
BUGCHECK_STR:  0x9C_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm!C1Halt+2
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Jan 25 01:14:43.286 2011 (UTC - 5:00)
System Uptime: 0 days 0:42:32.301
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[hegeron]

Thanks for the reply.

I ran memtest86 overnight with no errors.

I have removed Daemon Tools so that shouldn't be an issue.

I've also updated my video card drivers making sure the catalyst software was removed in safe mode. So if there was an issue there it should have been resolved.

The the last BSOD and another one before it happened when the machne was just idling and browsing the web.

For the CPU stress test, since I need to be there to monitor the temperature. WQhat should I consider a safe range and for how long should I run it?

 

[Jonathan_King]

I suggest running Prime95 for maybe 2 hours. If any of the workers stop before then, consider the test failed.

For the maximum temperature, look at about 90C. Supposedly the i7 can operate at up to 100C before it throttles down, but I would be concerned if it got to 90C.

 

[hegeron]

I ran the test for two hours and I've attached the results. The temperature never went above 68/69 degrees celsius. Tere were 2 things I considered odd.

1 - Worker 3 did far fewer tests than the other threads
2 - the first time I ran the test I immediately had a system crash, no dump was made and that was under the blend option. I'm gong to let the computer cool down a bit and see if I can replcate that, but it probably wont tell us anything.

 

[Jonathan_King]

If the Blend test crashes, we can guess that this is probably a RAM problem.

 

[hegeron]

Thanks for the replies.

I've changed the RAM and the crash is still happening. Most recently it seems to be happening after a cold start but I'm not sure that indicates anything or is just coincidence. It's also been happening during low intensity activites like web browsing, the screen will go blank and then reappear with the lower part of the screen corrupted.

Getting confused honestly

 

[Jonathan_King]

Hello again, and apologies for the 3-day delay.

What is the make/model of the PSU?

Also, run driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[hegeron]

Good morning,

OK I've swaped my ram mroe times this weekend than I cared to, it's definately not my original ram. Ironically enough the replacement video card and RAM both are defective so I will return those after work today. I will also try a spare video card f I can find one.

My PSU is a 600w modular power supply with the specs found here
Buy OCZ OCZ600MXSP 600W ATX12V V2.2 / EPS12V SLI Certified CrossFire Certified Modular Active PFC Power Supply - Retail @ iFocus.co.nz

 

[Jonathan_King]

I realized I posted in your other thread.

I'd say start looking for a new motherboard; check with the local PC shop, see if they will sell you one, and allow you to try it out or return it if need be. Maybe you can try RMAing your current board as well; if it comes out clean, all you've lost is the cost of shipping.

A wild shot, disable hyperthreading in the BIOS. That probably won't work; it's worth a try however, no matter how unlikely.

 

[hegeron]

I will robably have to check for a new MB. The main problem here is finding a shop that will allow a return if it doesn't help.

I did the driver verification and got a blue screen. I've attached the events from the last few days, the most recent 2 happened with driver verification going.

 

[Jonathan_King]

Probably completely unrelated, but uninstall Cyberlink completely.

Event[94]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-02-07T10:51:53.167
  Event ID: 7000
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Robulaic
  Description: 
The CyberLink UDF Filesystem service failed to start due to the following error: 
This driver has been blocked from loading

Event[95]:
  Log Name: System
  Source: Application Popup
  Date: 2011-02-07T10:51:53.167
  Event ID: 1060
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Robulaic
  Description: 
\SystemRoot\SysWow64\Drivers\CLBUDFR.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

Other than that, it seems it must be hardware.

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 14:10:36.914 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:25.942
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!RtlDispatchException+122
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[hegeron]

Well I've just had another BSOD (same as the other ones) with a new video card so I'm reasonably confident that it's not the video card or the ram.

So that just leaves the motherboard and the CPU. I've done a 2 hour long burn test without any crashing. So I would guess it's the MB. Is there any reliable way of determining which of the two it is?

 

[DeanP]

Upload the new dumps please.

 

[hegeron]

Here they are, thanks everyone for all the help. This has been very frustrating.

 

[DeanP]

Hello hegeron,
Update these drivers...

pcouffin.sys Wed Dec 06 03:39:30 2006
Used by many CD/DVD programs - rename drivers, see note below.

000.fcl Fri Jan 25 00:12:46 2008
CyberLink FCL Driver
Video editing software, Multimedia Software and Blu-ray playback software by CyberLink

   Note

Renaming drivers: create a restore point, using Windows Explorer, navigate to C:\Windows\System32\Drivers, locate the driver files, and rename them from .sys to .old. Reboot and the drivers will not load. This will break whatever software or hardware these drivers are associated with.

I would also uninstall ASUS Probe Utility, it is a known cause of BSOD.

 

[hegeron]

I've removed those drivers since I can easily reinstall powerdvd, and PC probe was pretty useless and the other driver was from something I'd uninstalled.

 

[Jonathan_King]

No reliable way to tell whether the problem is caused by the CPU or motherboard, unless you can swap out one of the two, and leave the other.

I'd say start with the motherboard, because that seems a bit more likely. If that doesn't help, we are left with the CPU. It stinks, I know, but that's the way it has to happen.