Sign in with
Sign up | Sign in
Your question

New rig getting BSoD on select steam games.

Last response: in Windows 7
Share
January 9, 2012 10:40:49 AM

I recently built a new computer and everything seems to be running smoothly; however, certain games will give me the BSoD upon startup and I'm not sure what the problem is. I'm sure it's hardware but certain games will play. For instance, I'm able to play Skyrim(and HL-2) without any incidents whatsoever. However, when I play Portal 2 or Deus Ex: Human Revolution, before the games even load I get a crash, I also get a strange error message about my GFX card when I attempt to load up L4D-2 (will update with link to a SS of the dialog box when I'm home) and that game runs but very poorly. The only non-steam game I have tried is QuakeLive(browser plugin) and it runs fine as well. All drivers are up to date. Dump file from crashes pasted below.

Here is my SYS info:
AMD FX-4100 Zambezi 3.6GHz (3.8GHz Turbo) Socket AM3+ 95W Quad-Core Desktop Processor
ASRock 970 EXTREME3 AM3+ AMD 970 SATA 6Gb/s USB 3.0 ATX AMD motherboard
PowerColor AX6770 1GBD5-H Radeon HD 6770 1GB 128-bit GDDR5 PCI Express 2.1 x16 HDCP video card
CORSAIR Builder Series CX500 V2 500W ATX12V v2.3 80 PLUS Certified Active PFC Power Supply
G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory
Seagate Barracuda ST31000524AS 1TB 7200 RPM 32MB Cache SATA 6.0Gb/s 3.5"
Acer G235HAbd 23'' 5ms 1920x1080 WideScreen LCD monitor 300 cd/m2 1000:1
windows 7 32 bit OS

What I have already ran/checked:
- drivers are up to date.
- memtest86 returned no errors after 5 passes.
- directx 11 is up to date. - sfc /scannow, via cmd.exe, to check for corrupt or missing windows system files. returned no errors.
- ran driver verifier, via cmd.exe, and the system did not BSoD.


Dump file from Blue Screen View
  1. ==================================================
  2. Dump File : 010712-24866-01.dmp
  3. Crash Time : 1/7/2012 3:39:45 PM
  4. Bug Check String :
  5. Bug Check Code : 0x00000124
  6. Parameter 1 : 0x00000000
  7. Parameter 2 : 0x86b56024
  8. Parameter 3 : 0x00000000
  9. Parameter 4 : 0x00000000
  10. Caused By Driver : ntoskrnl.exe
  11. Caused By Address : ntoskrnl.exe+32492b
  12. File Description : NT Kernel & System
  13. Product Name : Microsoft® Windows® Operating System
  14. Company : Microsoft Corporation
  15. File Version : 6.1.7601.17713 (win7sp1_gdr.111025-1505)
  16. Processor : 32-bit
  17. Crash Address : ntoskrnl.exe+32492b
  18. Stack Address 1 : ntoskrnl.exe+d1b6d
  19. Stack Address 2 : ntoskrnl.exe+d2997
  20. Stack Address 3 : ntoskrnl.exe+7da6b
  21. Computer Name :
  22. Full Path : C:\Windows\Minidump\010712-24866-01.dmp
  23. Processors Count : 4
  24. Major Version : 15
  25. Minor Version : 7601
  26. Dump File Size : 131,072
  27. ==================================================
  28.  
  29. ==================================================
  30. Dump File : 010712-33041-01.dmp
  31. Crash Time : 1/7/2012 3:01:21 PM
  32. Bug Check String :
  33. Bug Check Code : 0x00000124
  34. Parameter 1 : 0x00000000
  35. Parameter 2 : 0x86d3b2d4
  36. Parameter 3 : 0x00000000
  37. Parameter 4 : 0x00000000
  38. Caused By Driver : ntoskrnl.exe
  39. Caused By Address : ntoskrnl.exe+32492b
  40. File Description : NT Kernel & System
  41. Product Name : Microsoft® Windows® Operating System
  42. Company : Microsoft Corporation
  43. File Version : 6.1.7601.17713 (win7sp1_gdr.111025-1505)
  44. Processor : 32-bit
  45. Crash Address : ntoskrnl.exe+32492b
  46. Stack Address 1 : ntoskrnl.exe+d1b6d
  47. Stack Address 2 : ntoskrnl.exe+d2997
  48. Stack Address 3 : ntoskrnl.exe+7da6b
  49. Computer Name :
  50. Full Path : C:\Windows\Minidump\010712-33041-01.dmp
  51. Processors Count : 4
  52. Major Version : 15
  53. Minor Version : 7601
  54. Dump File Size : 131,072
  55. ==================================================
  56.  
  57. ==================================================
  58. Dump File : 010712-21886-01.dmp
  59. Crash Time : 1/7/2012 2:28:01 PM
  60. Bug Check String :
  61. Bug Check Code : 0x00000101
  62. Parameter 1 : 0x00000031
  63. Parameter 2 : 0x00000000
  64. Parameter 3 : 0x8d136120
  65. Parameter 4 : 0x00000003
  66. Caused By Driver : ntkrnlpa.exe
  67. Caused By Address : ntkrnlpa.exe+def20
  68. File Description : NT Kernel & System
  69. Product Name : Microsoft® Windows® Operating System
  70. Company : Microsoft Corporation
  71. File Version : 6.1.7601.17713 (win7sp1_gdr.111025-1505)
  72. Processor : 32-bit
  73. Crash Address : ntkrnlpa.exe+def20
  74. Stack Address 1 : ntkrnlpa.exe+7ba6f
  75. Stack Address 2 : ntkrnlpa.exe+7b0be
  76. Stack Address 3 : ntkrnlpa.exe+7af6b
  77. Computer Name :
  78. Full Path : C:\Windows\Minidump\010712-21886-01.dmp
  79. Processors Count : 4
  80. Major Version : 15
  81. Minor Version : 7601
  82. Dump File Size : 143,912
  83. ==================================================
  84.  
  85. ==================================================
  86. Dump File : 010712-18704-01.dmp
  87. Crash Time : 1/7/2012 1:42:01 PM
  88. Bug Check String :
  89. Bug Check Code : 0x00000124
  90. Parameter 1 : 0x00000000
  91. Parameter 2 : 0x862c68fc
  92. Parameter 3 : 0x00000000
  93. Parameter 4 : 0x00000000
  94. Caused By Driver : ntoskrnl.exe
  95. Caused By Address : ntoskrnl.exe+32490b
  96. File Description : NT Kernel & System
  97. Product Name : Microsoft® Windows® Operating System
  98. Company : Microsoft Corporation
  99. File Version : 6.1.7601.17713 (win7sp1_gdr.111025-1505)
  100. Processor : 32-bit
  101. Crash Address : ntoskrnl.exe+32490b
  102. Stack Address 1 : ntoskrnl.exe+d1bad
  103. Stack Address 2 : ntoskrnl.exe+d29d7
  104. Stack Address 3 : ntoskrnl.exe+7daab
  105. Computer Name :
  106. Full Path : C:\Windows\Minidump\010712-18704-01.dmp
  107. Processors Count : 4
  108. Major Version : 15
  109. Minor Version : 7601
  110. Dump File Size : 131,072
  111. ==================================================
  112.  
  113. ==================================================
  114. Dump File : 010712-20139-01.dmp
  115. Crash Time : 1/7/2012 1:38:01 PM
  116. Bug Check String :
  117. Bug Check Code : 0x00000124
  118. Parameter 1 : 0x00000000
  119. Parameter 2 : 0x86a85354
  120. Parameter 3 : 0x00000000
  121. Parameter 4 : 0x00000000
  122. Caused By Driver : ntoskrnl.exe
  123. Caused By Address : ntoskrnl.exe+32490b
  124. File Description : NT Kernel & System
  125. Product Name : Microsoft® Windows® Operating System
  126. Company : Microsoft Corporation
  127. File Version : 6.1.7601.17713 (win7sp1_gdr.111025-1505)
  128. Processor : 32-bit
  129. Crash Address : ntoskrnl.exe+32490b
  130. Stack Address 1 : ntoskrnl.exe+d1bad
  131. Stack Address 2 : ntoskrnl.exe+d29d7
  132. Stack Address 3 : ntoskrnl.exe+7daab
  133. Computer Name :
  134. Full Path : C:\Windows\Minidump\010712-20139-01.dmp
  135. Processors Count : 4
  136. Major Version : 15
  137. Minor Version : 7601
  138. Dump File Size : 131,072
  139. ==================================================
  140.  
  141. ==================================================
  142. Dump File : 010712-23166-01.dmp
  143. Crash Time : 1/7/2012 12:23:11 PM
  144. Bug Check String :
  145. Bug Check Code : 0x00000101
  146. Parameter 1 : 0x00000031
  147. Parameter 2 : 0x00000000
  148. Parameter 3 : 0x8d100120
  149. Parameter 4 : 0x00000002
  150. Caused By Driver : ntkrnlpa.exe
  151. Caused By Address : ntkrnlpa.exe+def20
  152. File Description : NT Kernel & System
  153. Product Name : Microsoft® Windows® Operating System
  154. Company : Microsoft Corporation
  155. File Version : 6.1.7601.17713 (win7sp1_gdr.111025-1505)
  156. Processor : 32-bit
  157. Crash Address : ntkrnlpa.exe+def20
  158. Stack Address 1 : ntkrnlpa.exe+7ba6f
  159. Stack Address 2 : ntkrnlpa.exe+7b0be
  160. Stack Address 3 : ntkrnlpa.exe+7af6b
  161. Computer Name :
  162. Full Path : C:\Windows\Minidump\010712-23166-01.dmp
  163. Processors Count : 4
  164. Major Version : 15
  165. Minor Version : 7601
  166. Dump File Size : 143,912
  167. ==================================================
  168.  
  169. ==================================================
  170. Dump File : 010712-23493-01.dmp
  171. Crash Time : 1/7/2012 12:20:38 PM
  172. Bug Check String :
  173. Bug Check Code : 0x00000101
  174. Parameter 1 : 0x00000031
  175. Parameter 2 : 0x00000000
  176. Parameter 3 : 0x8d100120
  177. Parameter 4 : 0x00000002
  178. Caused By Driver : dxgmms1.sys
  179. Caused By Address : dxgmms1.sys+7b7f
  180. File Description : DirectX Graphics MMS
  181. Product Name : Microsoft® Windows® Operating System
  182. Company : Microsoft Corporation
  183. File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
  184. Processor : 32-bit
  185. Crash Address : ntkrnlpa.exe+def20
  186. Stack Address 1 : ntkrnlpa.exe+7ba6f
  187. Stack Address 2 : ntkrnlpa.exe+7b0be
  188. Stack Address 3 : ntkrnlpa.exe+7af6b
  189. Computer Name :
  190. Full Path : C:\Windows\Minidump\010712-23493-01.dmp
  191. Processors Count : 4
  192. Major Version : 15
  193. Minor Version : 7601
  194. Dump File Size : 143,912
  195. ==================================================


Thank You!
a b $ Windows 7
January 9, 2012 11:15:06 AM

0x00000124 = WHEA_UNCORRECTABLE_ERROR

Basically, some hardware component is broken somewhere in the system, though in some cases, a bad driver can be the problem.

Based on the fact that it seems the crash tends to happen in two exact locations, I'm currently more inclined to lean towards a crappy driver, as a geniune hardware fault would be crashing in different locations...the last dump gives the big hint, I think:

Quote:
178.Caused By Driver : dxgmms1.sys
179.Caused By Address : dxgmms1.sys+7b7f
180.File Description : DirectX Graphics MMS


So for the time being, upgrade to the latest stable driver for your GPU. If you are already running the latest driver, go back a revision. Running a memory test might help, but this doesn't seem like a memory problem to me...

If these steps fail, I would recommend testing with another GPU, in case you have a true hardware failure.
m
0
l
a b $ Windows 7
January 9, 2012 11:18:31 AM

And as a quick note, this is one of the BSOD messages I hate the most, because it indicates a possible HW failure, and the crashes themselves typically happen deep within the Kernal, making it very hard to figure out exactly what component is at fault. I've seen this involve everything from a bad CPU cache right down to bad software...

The fact a DirectX component crashed once leads me to guess GPU though, so I'd focus on that first.
m
0
l
Related resources
January 9, 2012 11:44:17 AM

gamerk316 said:
And as a quick note, this is one of the BSOD messages I hate the most, because it indicates a possible HW failure, and the crashes themselves typically happen deep within the Kernal, making it very hard to figure out exactly what component is at fault. I've seen this involve everything from a bad CPU cache right down to bad software...

The fact a DirectX component crashed once leads me to guess GPU though, so I'd focus on that first.



I don't have another GPU laying around to stick in there and test. How should I got about testing/checking the GPU? changing drivers?
m
0
l
January 9, 2012 12:17:09 PM

Just update to the latest drivers available and give it a go.

I see that your mobo doesn't have integrated graphics, so just update the drivers and report back.
m
0
l
January 9, 2012 11:03:21 PM

I have the latest drivers and directx 11 is up to date.
m
0
l
January 10, 2012 12:03:28 AM

update your motherboard BIOS. update direct x. update windows.
m
0
l
January 10, 2012 12:56:34 AM

I have updated windows and directx. How do I go about updating the mobo BOIS?
m
0
l
a b $ Windows 7
January 10, 2012 6:27:10 PM

Please, stop it. Its not a BIOS issue. I hate it when people give generic steps that don't actually debug anything...

The only real way to stress test a GPU is via something VERY GPU intensive; 3dMark would be a good start. If that crashes consistently, then we probably have a GPU problem. I don't think its VRAM though, as I'd expect to see TDR_Timeout BSOD's...

Also, you mentioned a GPU dialog when starting L4D2; can you post a Screenshot?
m
0
l
January 10, 2012 7:13:11 PM

gamerk316 said:
Please, stop it. Its not a BIOS issue. I hate it when people give generic steps that don't actually debug anything...

The only real way to stress test a GPU is via something VERY GPU intensive; 3dMark would be a good start. If that crashes consistently, then we probably have a GPU problem. I don't think its VRAM though, as I'd expect to see TDR_Timeout BSOD's...

Also, you mentioned a GPU dialog when starting L4D2; can you post a Screenshot?


I believe I have already stress tested my GPU but I'll run it anyways.

m
0
l
!