Solved BSOD troubles seem to be while playing games - different BsOD codes

[tbrown26]

My blue screens seem to happen when I am playing games, I have attached some logs and the zip file using the tool in the instructions. I have tried to upgrade my bios and my video card drivers without any luck. I would be grateful for any suggestions or help.
thanks,
Tim


windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH Z77
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17121755136 total



[FONT=Segoe UI, Arial]
Crash Dump Analysis
</B>[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/24/2014 6:14:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112414-7784-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003179181, 0xFFFFF88009D8D020, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 11/24/2014 6:14:39 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003179181, 0xFFFFF88009D8D020, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 11/22/2014 4:16:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112114-8626-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A01E4045B0, 0xFFFFF8A01E404570, 0xFFFFF8A01E4045B0)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 11/13/2014 3:50:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111214-7690-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FFFA9B, 0xFFFFF880086FC530, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 11/9/2014 9:42:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110914-7675-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x1983)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004511983, 0xFFFFF8800B056BD0, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]

 

[essenbe]

Hello, tbrown26. I will try to help you with this.

None of your dump files were overly definitive, as usual. The first thing I would like you to do is fill out your system specs in detail. Sometimes we have to look up a component and Manufacturer and model number helps us to do that.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

After completing that please open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[tbrown26]

memory tests and sfc

I believe I successfully uploaded/saved my system specs via the tool. The SFC found NO integrity violations. windows memory test gave me mixed results. mem86 gave me the following, but I don't understand why the errors don't occurr at the same memory address. should I assume that I need to replace the last stick of memory?

thank you.


FIRST MEM86 TEST
Summary

Report Date2014-11-24 22:21:57Generated byMemTest86 V5.1.0 Free (64-bit)ResultFAIL
System Information

EFI Specifications2.31CPU typeIntel Core i5-3570K @ 3.40GHzMeasured CPU Speed3418 MHz [Turbo: 3498.3 MHz]# Logical Processors4L1 Cache64K (100887 MB/s)L2 Cache256K (52105 MB/s)L3 Cache6144K (32351 MB/s)RAM16431M (20018 MB/s)DIMM #04GB DDR3 XMP PC3-12800Corsair / CMX8GX3M2A1600C9 9-9-9-24 / 800 MHz / 1.650VDIMM #14GB DDR3 XMP PC3-12800Corsair / CMX8GX3M2A1600C9 9-9-9-24 / 800 MHz / 1.650VDIMM #24GB DDR3 XMP PC3-12800Corsair / CMX8GX3M2A1600C9 9-9-9-24 / 800 MHz / 1.650VDIMM #34GB DDR3 XMP PC3-12800Corsair / CMX8GX3M2A1600C9 9-9-9-24 / 800 MHz / 1.650V
Result summary

Test Start time2014-11-24 21:33:08Elapsed Time0:47:42Memory Range Tested0x0 - 41F000000 (16880MB)CPU Selection ModeSingle (CPU #0)# Tests Passed10/11 (90%)Lowest Error Address0x7042A7F0 (1796MB)Highest Error Address0x70C2BF40 (1804MB)Bits in Error Mask0000000000000004Bits in Error1Max Contiguous Errors1Test# Tests PassedErrorsTest 0 [Address test, walking ones, 1 CPU] 1/1 (100%)0Test 1 [Address test, own address, 1 CPU] 1/1 (100%)0Test 2 [Address test, own address] 1/1 (100%)0Test 3 [Moving inversions, ones & zeroes] 1/1 (100%)0Test 4 [Moving inversions, 8-bit pattern] 1/1 (100%)0Test 5 [Moving inversions, random pattern] 1/1 (100%)0Test 6 [Block move, 64-byte blocks] 1/1 (100%)0Test 7 [Moving inversions, 32-bit pattern] 1/1 (100%)0Test 8 [Random number sequence] 1/1 (100%)0Test 9 [Modulo 20, ones & zeros] 1/1 (100%)0Test 10 [Bit fade test, 2 patterns, 1 CPU] 0/1 (0%)18Last 10 Errors[Data Error] Test: 10, CPU: 0, Address: 70C2BF40, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 70C2BF30, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 70C2BB00, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 70C2ACA0, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 70C2AA60, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 70C2A7F0, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 7060BF40, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 7060BF30, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 7060BB00, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 7060ACA0, Expected: FFFFFFFF, Actual: FFFFFFFB

Second MEM86 TEST

Summary

Report Date2014-11-24 22:36:54Generated byMemTest86 V5.1.0 Free (64-bit)ResultFAIL
System Information

EFI Specifications2.31CPU typeIntel Core i5-3570K @ 3.40GHzMeasured CPU Speed3418 MHz [Turbo: 3498.3 MHz]# Logical Processors4L1 Cache64K (100887 MB/s)L2 Cache256K (52105 MB/s)L3 Cache6144K (32351 MB/s)RAM16431M (20018 MB/s)DIMM #04GB DDR3 XMP PC3-12800Corsair / CMX8GX3M2A1600C9 9-9-9-24 / 800 MHz / 1.650VDIMM #14GB DDR3 XMP PC3-12800Corsair / CMX8GX3M2A1600C9 9-9-9-24 / 800 MHz / 1.650VDIMM #24GB DDR3 XMP PC3-12800Corsair / CMX8GX3M2A1600C9 9-9-9-24 / 800 MHz / 1.650VDIMM #34GB DDR3 XMP PC3-12800Corsair / CMX8GX3M2A1600C9 9-9-9-24 / 800 MHz / 1.650V
Result summary

Test Start time2014-11-24 22:22:24Elapsed Time0:10:20Memory Range Tested0x0 - 41F000000 (16880MB)CPU Selection ModeSingle (CPU #0)# Tests Passed0/1 (0%)Lowest Error Address0x7368C080 (1846MB)Highest Error Address0x73C2BF78 (1852MB)Bits in Error Mask00000000000000FFBits in Error8Max Contiguous Errors1Test# Tests PassedErrorsTest 10 [Bit fade test, 2 patterns, 1 CPU] 0/1 (0%)568Last 10 Errors[Data Error] Test: 10, CPU: 0, Address: 7368FCD0, Expected: FFFFFFFF, Actual: FFFFFFEF[Data Error] Test: 10, CPU: 0, Address: 7368F880, Expected: FFFFFFFF, Actual: FFFFFFF7[Data Error] Test: 10, CPU: 0, Address: 7368F660, Expected: FFFFFFFF, Actual: FFFFFFF7[Data Error] Test: 10, CPU: 0, Address: 7368F150, Expected: FFFFFFFF, Actual: FFFFFFEF[Data Error] Test: 10, CPU: 0, Address: 7368F110, Expected: FFFFFFFF, Actual: FFFFFF7F[Data Error] Test: 10, CPU: 0, Address: 7368F0E0, Expected: FFFFFFFF, Actual: FFFFFFBF[Data Error] Test: 10, CPU: 0, Address: 7368F0B0, Expected: FFFFFFFF, Actual: FFFFFFFD[Data Error] Test: 10, CPU: 0, Address: 7368EC20, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 7368E870, Expected: FFFFFFFF, Actual: FFFFFFFB[Data Error] Test: 10, CPU: 0, Address: 7368E770, Expected: FFFFFFFF, Actual: FFFFFFFB

 

[essenbe]

You need to keep track of each stick in each slot. Take 1 stick only and run it in slot 1. If it passes, take it out and run it in slot 2 then continue. If you get even 1 error, stop the test, note which stick and which slot. The idea of memory testing is to not only test the memory sticks, but test the motherboard dim slots too. It is not that uncommon to have a bad dim slot on a motherboard.

Did you download the test from here Memtest86+ - Advanced Memory Diagnostic Tool ? That is the test you need to use.

 

[tbrown26]

thanks. i'll try that and let you know.

 

[essenbe]

OK. Trust me, I know what a Pain it is. I've been there myself more times than I wish to count. But, it is necessary. If you run 1 stick for 8 passes in each slot with no errors, stop and let me know.

 

[tbrown26]

I wasn't able to get the test to run with one memory stick, but I did purchase an extra and was able to find the bad one. I appreciate you help. you are a saint for volunteering your time to help others.

thanks,
Tim

 

[essenbe]

You are very welcome for what little help I was able to give. When you RMA it, be sure to RMA all of it and get a kit in return. Kits are always better because they have been tested to work together, where individual sticks are not, and in some cases won't, even the same model numbers. In many cases they will work, but you have to accept the fact that you are taking a risk. I'm happy to help in any way I can. But, as far as being a Saint, I think I fall very short in that department. I have many references that will happily verify that I am no saint. Thanks a lot and let us know if you need any further help. We are always open.