BSOD after bright color flash on monitors...

[canario440]

First post ever on any type of forum... that's the good news.

I'm going on a couple of years with this problem and am ready to buy (make) a new PC. I had this one made from iBuyPower and have moved a few times since (currently stationed in Germany)... so I don't have all the specs but will dig up whatever's needed if it helps.
Summary of the problem: Usually occurs when I have several browser tabs open or while doing something fairly intensive... and sometimes I check the computer in the morning only to find that it had crashed the night before. I can't recreate the problem... the best I can do is pull up a few youtube clips and sometimes that does it.
When it happens, my mouse will freeze and ~1 sec later a bunch of colors appear on both screens (dual monitors) for ~1/2sec and BSOD commences.
I'm far from a computer genius but know enough to be dangerous.

Here's what I've done so far in a nutshell:
1- Called iBuyPower for help... past warranty period. So nothing there for me
2- Updated the BIOS for my Video card and my motherboard from the manufactures websites
3- Started scanning newegg in preparation for a new computer to build myself
4- Did what I could to make sure BIOS settings were correct... it got really confusing there so I stopped and figured I'd get help from experts on this board...

Here's what I have (known): All installed by iBuyPower
- Purchased ~Apr 2010
- Windows 7 Home Premium 64bit SP1
- AMD Phenom II X4 965 Processor (3.41GHz)
- 8GB RAM DDR3-1600G
- Asus M4A79T Deluxe Rev C3 Motherboard
- ATI Radeon HD 5800 Series Video Card

I'm pretty much on my knee's here... many thanks for any responses up front!

 

[canario440]

Wow... things must be worse than I thought (crickets...)

 

[writhziden]

Problem Devices:

USB Mass Storage Device	USB\VID_066F&PID_8000\18040000E7268D900002DCF617648D90	This device cannot start.
Photosmart C6100 series	ROOT\MULTIFUNCTION\0000	The drivers for this device are not installed.
Photosmart C6100 series	ROOT\MULTIFUNCTION\0001	The drivers for this device are not installed.
Photosmart C6100 series	ROOT\MULTIFUNCTION\0002	The drivers for this device are not installed.
Photosmart C6100 series	ROOT\MULTIFUNCTION\0003	The drivers for this device are not installed.
Photosmart C6100 series	ROOT\MULTIFUNCTION\0004	This device is disabled.

Security Software (this is just to check that it is installed and working properly; nothing needs to be done with this information at this time):

mbamservice.exe	c:\program files (x86)\malwarebytes' anti-malware\mbamservice.exe	2912	8	200	1380	4/18/2012 1:54 PM	Not Available	Not Available	Not Available
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	972	8	200	1380	4/18/2012 1:52 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	2988	8	200	1380	4/18/2012 1:52 PM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	3636	8	200	1380	4/18/2012 1:53 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\canario440\Echo\041812-139558-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`0325f650
Debug session time: Wed Apr 18 05:47:31.808 2012 (UTC - 6:00)
System Uptime: 0 days 0:24:38.932
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80080cc028, b419a000, 145}

Probably caused by : hardware

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80080cc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b419a000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000145, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f0a88 fffff800`03615a3b : 00000000`00000124 00000000`00000000 fffffa80`080cc028 00000000`b419a000 : nt!KeBugCheckEx
fffff880`009f0a90 fffff800`031a7b33 : 00000000`00000001 fffffa80`080cdd30 00000000`00000000 fffffa80`080cdd80 : hal!HalBugCheckSystem+0x1e3
fffff880`009f0ad0 fffff800`03615700 : 00000000`00000728 fffffa80`080cdd30 fffff880`009f0e30 fffffa80`05a3a900 : nt!WheaReportHwError+0x263
fffff880`009f0b30 fffff800`03615052 : fffffa80`080cdd30 fffff880`009f0e30 fffffa80`080cdd30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f0c80 fffff800`03608e8f : 00000000`001e1388 00000000`00000001 fffff880`009f0eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f0cc0 fffff800`0309656c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`009f0cf0 fffff800`030963d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f0e30 fffff800`030b4522 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03b88090 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x122


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

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

• If you are overclocking any hardware, please stop.
  
  
• 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 a 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).
  
  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.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Make sure to read through the http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html link carefully.

 

[canario440]

Right... not sure if I'm overclocking anything to be honest.

Looks like I have a lot of work to do... good news it's Friday and I have time. Many thanks for the response!

I'll report the results back

 

[canario440]

Still running tests... but here's an update thus far:
Fur Mark:
- 1920x1080
- 99% load
- min temp 50C, max temp 68C, steady temp ~63C (the instances where 68C was reached was only during short spikes... this was accompanied by a very quick jolt/zap to my 2nd monitor)
- score: 1493

Video Mem Test:
- Trying 16bpp RGB: 565 mode... ok
- Trying 16bpp RGB: 555 mode... ok
- Trying 16bpp BGR: 565 mode... not supported
- Trying 32bpp RGB: 888 mode... ok
- Trying 32bpp BGR: 888 mode... not supported
0 Errors found (same for all passes)

Prime95 stress test: 2hrs+ running
- Worker (CPU) #1: Self tests 20K, 8K, 28K, 12K, 24K, 10K, 32K, 16K, 20K... all passed
- Worker (CPU) #2: same as above
- Worker (CPU) #3: same as above
- Worker (CPU) #4: same as above

Intel Burn Test in progress...

* I've noticed more frequent occurrences of the zapping/jolt that usually occurred when watching a youtube video or streaming some kind of media. I was pretty certain that I would see lots of errors when performing these graphics card tests... nothing so far (should I be frustrated?). So is my luck with computers...

In either case, I find it amazing that anyone you wicked smaht types are able to interpret the results. Really appreciated!

More to follow...

 

[writhziden]

Everything looks pretty good. Some concern with the jolt/zap to the second monitor, but not really sure what that means. Can you describe what happens in a little more detail?


Let us know how the Memest86+ diagnostics go.

 

[canario440]

Computer just crashed so I'm attaching the dump using the Who Crashed application...

I captured a short clip of the glitch... they gray lines don't look as pronounced in person but maybe that's just the camera. This happens during normal use about every 10min... sometimes more, sometimes less... but it does happen regularly, often when starting a video (streaming or from HDD). But randomly as well...

It's not anything I can recreate...

Onto Memest86+...

 

[canario440]

Forgot to mention Intell Burn test results:
- 5 passes for each test
- Max temp for processor according to AMD website provided in one of the above tutorial links is 62C

- standard test: success, max temp reached = 57C
- High test: success, max temp reached = 61C
- Very High test: success, max temp reached = 62C

 

[writhziden]

Temperatures are a bit high, which may be contributing to the problem. Make sure your system is clear of any dust (use compressed air, and never use a vacuum on the inside of the system). Also, you may want to remove the graphics card and make sure its contacts with the board are clean. Avoid Static Damage to Your PC when removing or replacing components.

 

[canario440]

Memtest86+ results:
- Wall time: 12:16hrs
- Cached: 8190M
- Rsvd: 160K
- MemMap: e820
- Cache: On
- ECC: Disabled
- Test: Std
- Pass: 7
- Errors: 0
- ECC errors: n/a

Also ran several iterations of the Windows Memory Diagnostics Tool... (4 times w/8 passes)... each showed no errors after reboot.

Time to concede to Bill Gates?

 

[writhziden]

Alright, that means it is not likely memory, but it does not rule out the possibility entirely. Memtest86+ only tests certain memory stress scenarios. Windows causes stress in different ways than Memtest86+, so sometimes it helps to test one module at a time by just doing your normal routine in Windows and seeing if it crashes. You want to do your normal routine for as long (or better, twice as long) as it normally takes for a crash to occur while doing the things that normally cause crashes.

Did you re-seat the graphics card?