BSOD Playing League of Legends - Brand New Custom Built PC

What about possible problems with the hardware that I have .. are these reports that im uploading specifying anything regarding the hardware / failures?

Hi - please see last upload at bottom of page 1.

If anyone can help, I would greatly appreciate it.

Chaserjim said:

Well , I was able to use the computer for about 3 hours before another BSOD. Please let me know what this report says and what I should do in order to correct it.

Thanks again to ZigZag and Lemur for all your efforts.

Attached is the new BSOD report.

Please let me know the next steps!

Jim

The most recent is caused by memory corruption (probably from audiodg)


These crashes were caused by memory corruption (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!!!


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.

Any errors are indicative of a memory problem.

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

RAM - Test with Memtest86+



2-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 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.

Driver Verifier - Enable and Disable


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

Chaserjim said:

Currently I am booting to Memtest86 V4.20

I have 2 x 4gb DDr3 sticks.

The sticks were in slots 1 and 3. I have removed the stick from slot 3 and am testing stick 1 in slot 1.

Stick 1 passed in slot 1. Moving Stick 1 to Slot 3 and running.

My next test will be stick 2 in slot 1 and then to slot 3. That should cover all the memory concerns. I will post if I receive any memory errors during this test.



****** I ran MemTest on the 2 sticks , rotating in each slot. Both sticks came back without any errors detected. Pass rate 100%.

******

Good next verifier.

Ok, it took 5 hours to happen , but I did get a BSOD while verifier was running in the background.

Attached is the BSOD jcgriff - please let me know what to do next! I am constantly refreshing this page..

I tried to perform "verfied /query" from a command prompt, this command opened another command prompt but the characters scrolled past and the prompt closed before I could decipher anything.

Please let me know if I am missing anything ..

I am disabling the verifier and rebooting.

bump

Chaserjim said:

Ok, it took 5 hours to happen , but I did get a BSOD while verifier was running in the background.

Attached is the BSOD jcgriff - please let me know what to do next! I am constantly refreshing this page..

I tried to perform "verfied /query" from a command prompt, this command opened another command prompt but the characters scrolled past and the prompt closed before I could decipher anything.

Please let me know if I am missing anything ..

I am disabling the verifier and rebooting.

Three hours and you are bumpng? Normal turn around is more than 12 hours

The most recent is driver verified and related to audiodg.sys

It is part of your audio driver and is a known cause of crashing. There are several fixes and all you need to do is google audiodg.sys BSOD.

Attached is my most recent BSOD - a little background. Since the last post, I decided to reformat my HD and install windows fresh with SP1 and all driver updates.

I hadnt had a blue screen since - until today, again while in League of Legends.

Attached are the finding and I have also included a diaxdg report. Do you think my grfx card might be the problem?