BSOD in chrome playing vid, BSOD locked with sound in background

[Beast52702]

The system just bsod while watching video on chrome. The bluescreen was locked with a sound repeated in background. It did not restart itself as is normal.

I have recently updated my video drivers and I believe all other drivers to be current. I recently ran memtest 86+ for 7 full passes with no errors, but it could still be the memory as the modules are new(about a month).



Ignore the old minidumps as they are the result of tweaking/overclocking my system. The dump of interest is from today and is attached separately from jcgriff.

My system is the same as in my user profile.

Win 7Ultimate 64bit.
Microsoft security essentials and Malwarebytes are used for realtime protection and scanning.

This is the first non OCing bsod I've had on my rig in a long time,

Please help

 

[zigzag3143]

The system just bsod while watching video on chrome. The bluescreen was locked with a sound repeated in background. It did not restart itself as is normal.

I have recently updated my video drivers and I believe all other drivers to be current. I recently ran memtest 86+ for 7 full passes with no errors, but it could still be the memory as the modules are new(about a month).



Ignore the old minidumps as they are the result of tweaking/overclocking my system. The dump of interest is from today and is attached separately from jcgriff.

My system is the same as in my user profile.

Win 7Ultimate 64bit.
Microsoft security essentials and Malwarebytes are used for realtime protection and scanning.

This is the first non OCing bsod I've had on my rig in a long time,

Please help

Unfortunately the most recent was inconclusive. We can do some testing while waiting for the next one. Most often it is memory or driver related.

Please run these two tests.



1-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 or 6 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.

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



2-Driver verifier

I'd suggest that you first backup your data 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"
- 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.

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 (an estimate on my part).

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.

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

 

[Beast52702]

I am running memtest86+ as we speak. It has run for 4 hours so far with zero errors, it is almost done with pass 3. I will probably let ti run overnight just to be sure. As soon as that completes or shows errors, I will enable driver verifier.

Thanks for the help zigzag

*edit* should I be running both 4 gig sticks at the same time or should I start out running one at a time?

 

[Beast52702]

After a failed memtest, I rma'd my ram and I am now testing 2 new sticks. I got a bsod last night while running prime 95. I am running the sticks at the stated timings of 8-8-8-24-34 @ 1600 mhz. I woke up this morning to a restarted computer so I decided to restart the test with a slight voltage bump. from 1.5 V to 1.53 V.

*Note* these are the manufacturer timings and speed for this ram, however it is xmp specified so maybe it needs more juice on an amd rig? I have also been told that it could be a result of the phenom ii integrated memory controller needing more voltage to run high speed memory. I am unsure of the cause.

[FONT=&quot]Problem signature:[/FONT]
[FONT=&quot] Problem Event Name: BlueScreen[/FONT]
[FONT=&quot] OS Version: 6.1.7601.2.1.0.256.1[/FONT]
[FONT=&quot] Locale ID: 1033[/FONT]

[FONT=&quot]Additional information about the problem:[/FONT]
[FONT=&quot] BCCode: 124[/FONT]
[FONT=&quot] BCP1: 0000000000000000[/FONT]
[FONT=&quot] BCP2: FFFFFA800843D028[/FONT]
[FONT=&quot] BCP3: 00000000B2674000[/FONT]
[FONT=&quot] BCP4: 0000000000000175[/FONT]
[FONT=&quot] OS Version: 6_1_7601[/FONT]
[FONT=&quot] Service Pack: 1_0[/FONT]
[FONT=&quot] Product: 256_1[/FONT]

[FONT=&quot]Files that help describe the problem:[/FONT]
[FONT=&quot] C:\Windows\Minidump\100411-16380-01.dmp[/FONT]
[FONT=&quot] C:\Users\Michael\AppData\Local\Temp\WER-30786516-0.sysdata.xml[/FONT]


I have not run memtest 86+ as I would like my system to be overnight prime stable.

I am loading the 8gb of ram to 90% on Prime by using custom and setting ram usage to 6600 mb.


New dump attached (I'm pretty sure it memory related, but just in case)

Thanks Guys

 

[zigzag3143]

After a failed memtest, I rma'd my ram and I am now testing 2 new sticks. I got a bsod last night while running prime 95. I am running the sticks at the stated timings of 8-8-8-24-34 @ 1600 mhz. I woke up this morning to a restarted computer so I decided to restart the test with a slight voltage bump. from 1.5 V to 1.53 V.

*Note* these are the manufacturer timings and speed for this ram, however it is xmp specified so maybe it needs more juice on an amd rig? I have also been told that it could be a result of the phenom ii integrated memory controller needing more voltage to run high speed memory. I am unsure of the cause.

[FONT=&quot]Problem signature:[/FONT]
[FONT=&quot] Problem Event Name: BlueScreen[/FONT]
[FONT=&quot] OS Version: 6.1.7601.2.1.0.256.1[/FONT]
[FONT=&quot] Locale ID: 1033[/FONT]

[FONT=&quot]Additional information about the problem:[/FONT]
[FONT=&quot] BCCode: 124[/FONT]
[FONT=&quot] BCP1: 0000000000000000[/FONT]
[FONT=&quot] BCP2: FFFFFA800843D028[/FONT]
[FONT=&quot] BCP3: 00000000B2674000[/FONT]
[FONT=&quot] BCP4: 0000000000000175[/FONT]
[FONT=&quot] OS Version: 6_1_7601[/FONT]
[FONT=&quot] Service Pack: 1_0[/FONT]
[FONT=&quot] Product: 256_1[/FONT]

[FONT=&quot]Files that help describe the problem:[/FONT]
[FONT=&quot] C:\Windows\Minidump\100411-16380-01.dmp[/FONT]
[FONT=&quot] C:\Users\Michael\AppData\Local\Temp\WER-30786516-0.sysdata.xml[/FONT]


I have not run memtest 86+ as I would like my system to be overnight prime stable.

I am loading the 8gb of ram to 90% on Prime by using custom and setting ram usage to 6600 mb.


New dump attached (I'm pretty sure it memory related, but just in case)

Thanks Guys

The newest DMP is a 124 BC and it usually refers to hardware.

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Beast52702]

Thanks again for the prompt assistance. Atleast the minidump seems to confirm that it's a hardware issue.

I just got done running prime95 for over 12 hours with no errors, system hangs, or bsod. Then I scan a few documents and it just freezes. No bsod or restart or black screen, just a complete system hang. So it can run at 100% cpu and 90-92% ram usage for 12 hrs, but it freezes when i scan something. Weird.

I just increased the cpu-nb voltage a tad, ill see if that helps. Anyone with any ideas, let me know.

 

[Beast52702]

After increasing the cpu-nb voltage slightly, from 1.1 to 1.175V, and running the DRAM at 1.545V, I have completed 12.5 hours of memtest with 0 errors. I am currently running prime stable(for like 3 hours so far).

I completely removed my Video drivers, then used driver sweeper, and reinstalled the newest drivers. I did this in response to the following system message

"The Desktop Window Manager is experiencing heavy resource contention.
Reason : Graphics subsystem resources are over-utilized.
Diagnosis : A consistent degradation in frame rate for the Desktop Window Manager was observed over a period of time."

I looked on google, but not many definitive answers. Any Ideas as to what this means?