BSOD playing WoW or LoL

[dkazriel]

Windows 7 Professional x64
Initially Vista was installed
I got the OS from the academic alliance Microsoft has with my college.
Fresh REinstall of Windows 7, I had the same errors with the first install of Win 7 (maybe a couple weeks old)

The system is roughly 1-2 years old, I have upgraded the GPU and RAM in the past 6 months.

I get frequent crashes while playing League of Legends or World of Warcraft. When I try to login to Warcraft specifically my internet connection gets cut off for about 20-30 seconds and then comes back up. I can't stay logged in to the game for a consistent amount of time. I could be fine for a few hours or a couple minutes.

I also have BlueScreenView and AppCrashView reports if those will help at all.

 

[dkazriel]

Intel Core 2 Quad Q6600
3GB Kingston HyperX DDR2 1066
Gigabyte LGA 775 P45 Mobo
ASUS ENGTX460 (GeForce GTX460)
Western Digital Caviar Blue 500GB 7200RPM SATA 3.0Gb/s

 

[zigzag3143]

Windows 7 Professional x64
Initially Vista was installed
I got the OS from the academic alliance Microsoft has with my college.
Fresh REinstall of Windows 7, I had the same errors with the first install of Win 7 (maybe a couple weeks old)

The system is roughly 1-2 years old, I have upgraded the GPU and RAM in the past 6 months.

I get frequent crashes while playing League of Legends or World of Warcraft. When I try to login to Warcraft specifically my internet connection gets cut off for about 20-30 seconds and then comes back up. I can't stay logged in to the game for a consistent amount of time. I could be fine for a few hours or a couple minutes.

I also have BlueScreenView and AppCrashView reports if those will help at all.

These crashes were caused by memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.


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.

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

 

[dkazriel]

I just finished running MemTest and it said "Pass complete, no errors"

 

[dkazriel]

The issue I'm going to have with the verifier (which I'm currently doing now) is that it's not always just a BSOD but both games frequently crash. Is this going to give feedback on that as well?

 

[dkazriel]

League of Legends just crashed as it usually does, here is the message I received...

Problem signature:
Problem Event Name: BEX
Application Name: League of Legends.exe
Application Version: 1.0.0.130
Application Timestamp: 4ecdb494
Fault Module Name: MSVCR80.dll
Fault Module Version: 8.0.50727.4940
Fault Module Timestamp: 4ca2b271
Exception Offset: 00008aa0
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 2104
Additional Information 2: 210425e42a4b5d5e5b84d5927f92118a
Additional Information 3: 958b
Additional Information 4: 958b171a538067c3c84f5593f2993dd5

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[zigzag3143]

League of Legends just crashed as it usually does, here is the message I received...

Problem signature:
Problem Event Name: BEX
Application Name: League of Legends.exe
Application Version: 1.0.0.130
Application Timestamp: 4ecdb494
Fault Module Name: MSVCR80.dll
Fault Module Version: 8.0.50727.4940
Fault Module Timestamp: 4ca2b271
Exception Offset: 00008aa0
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 2104
Additional Information 2: 210425e42a4b5d5e5b84d5927f92118a
Additional Information 3: 958b
Additional Information 4: 958b171a538067c3c84f5593f2993dd5

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

It is almost impossible to spot trends from a single DMP file so if you have more than one please upload them. If you only have one please wait until the computer crashes again then upload both.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.



The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[dkazriel]

I have the system health report that I was told to save as a .html and upload the problem is I can't seem to upload that file type.

 

[zigzag3143]

I have the system health report that I was told to save as a .html and upload the problem is I can't seem to upload that file type.

We dont really need the health report. We need the DMP files and they need to be compressed to upload

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

It is almost impossible to spot trends from a single DMP file so if you have more than one please upload them. If you only have one please wait until the computer crashes again then upload both.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.



The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[dkazriel]

Here's what I have for now in the minibump folder.

 

[zigzag3143]

Here's what I have for now in the minibump folder.

These crashes were caused by memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.


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.

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

 

[dkazriel]

Here are the dump files after a BSOD, hope this helps!

 

[dkazriel]

I've already run both of those.

 

[writhziden]

Did you run Memtest86+ for 7 passes yet? You posted within an hour that you had run it, and it takes ~7-10 hours on average to do 7 passes.

Edit: Also, pay very close attention to parts 2 and 3 of the Memtest86+ tutorial referenced by zigzag3143

Edit2: Your problem seems to be memory related, which is why we are stressing this test. It is possible you have a bad module/mismatched modules that are not compatible with each other or a bad memory module slot. Without running Memtest86+ for at least five passes (preferably seven to thoroughly test), it is impossible to tell whether it truly is a memory problem or something else underlying your BSODs.

 

[zigzag3143]

Here are the dump files after a BSOD, hope this helps!

Only one of these was with driver verifier enabled and it did not find a mis behaving driver.

The others still point to memory corruption.

 

[dkazriel]

I ran memtest for 9 passes, no errors found.

 

[writhziden]

Alright. Have you updated your BIOS recently? Another thing to do is install DirectX again since it is gaming related. Find the latest DirectX and see if you can repair your current installation (or if it is newer, install the newest version).

 

[dkazriel]

I've never updated a bios before and I'll try updating DX now.

 

[writhziden]

I've never updated a bios before and I'll try updating DX now.

To update your BIOS, find your computer model vendor's homepage, and see if they have a BIOS update for your model to flash the BIOS. If you have a custom built machine, go to the motherboard's manufacturer's homepage and see if there is a BIOS update to flash the BIOS for your motherboard.

 

[dkazriel]

Here's another BSOD.