Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › CS:GO BSOD with Hal.dll
New Posts  All Forums:Forum Nav:

CS:GO BSOD with Hal.dll

post #1 of 6
Thread Starter 
BSOD only in Counter-Strike: Global Offensive so far.

My system is not overclocked and has not been for over a year, same components (need to update my sig!).

Hope this isn't hardware, but I did take a look through the minidumps and I think I'll be running memtest and pulling parts out tomorrow morning frown.gif

Here's hoping someone else thinks differently!


041612-8421-01.zip 90k .zip file
Fep
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 D0 ASRock X58 Extreme Radeon 5850 x2 6x2GB Corsair XMS3 1600 
Hard DriveHard DriveHard DriveOS
Samsung 830 OCZ Vertex 3 2x WD5000AAJS Windows 7 x64 [Ultimate] & Linux Mint 
MonitorKeyboardPowerCase
3x ASUS VH242HL-P Razer BlackWidow Ultimate/Steelseries 6Gv2 OCZ ProXStream 1000W LianFish [Modded] 
MouseMouse PadAudioAudio
Razer DeathAdder 3G [Hyper Glide]/Logitech G9 SteelSeries QcK+/Puretrak Talent Creative X-Fi XtremeGamer NuForce uDac 
  hide details  
Reply
Fep
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 D0 ASRock X58 Extreme Radeon 5850 x2 6x2GB Corsair XMS3 1600 
Hard DriveHard DriveHard DriveOS
Samsung 830 OCZ Vertex 3 2x WD5000AAJS Windows 7 x64 [Ultimate] & Linux Mint 
MonitorKeyboardPowerCase
3x ASUS VH242HL-P Razer BlackWidow Ultimate/Steelseries 6Gv2 OCZ ProXStream 1000W LianFish [Modded] 
MouseMouse PadAudioAudio
Razer DeathAdder 3G [Hyper Glide]/Logitech G9 SteelSeries QcK+/Puretrak Talent Creative X-Fi XtremeGamer NuForce uDac 
  hide details  
Reply
post #2 of 6
Hi smile.gif

**First off, before we begin, if you're overclocking any component please return it to stock clocks whilst troubleshooting BSODs.

I've taken a look at your dumps, and they are all x124 hardware bugchecks blaming intelppm.sys which is the Intel Processor Driver. There are many things that can cause a x124 BSOD:

- Inadequate cooling to any component.

- Unstable overclock(s).

- Not having the latest BIOS. In some cases, BIOS updates are a necessity for some boards (like SB boards) as they are still new technology and every update offers stability improvements.

- Not having the latest drivers for your hardware, notably RAID & NIC, but of course other hardware as well.

- Dust. Dust is a big culprit of x124 BSODs. Make sure each of your components and slots are clean and free of dust.

etc....

Here's what I recommend doing:

Since we're getting NOTHING but x124 BSODs with the same culprit every time, I think this is hardware rather than software, so I'd recommend doing hardware troubleshooting first:

1. Memtest. Read the following on how to test your memory for errors.

2. Chkdsk. Run a chkdsk /r in elevated command prompt (run cmd as admin) to see if it finds any bad sectors on your drive.

3. If the above two find nothing, start running stress tests on your 5850s and see if you get any crashes or artifacting.

4. Try running a "Blend" of Prime95 at full stock settings. If you're at stock, there should be no issue passing a Blend test.

5. If hardware is somehow showing nothing, we'll move onto enabling Driver Verifier. If this is software / driver related, Driver Verifier will point it out in a verifier enabled crash dump.

Driver(s) in need of update:
Quote:
ctac32k.sys - Wed Jul 02 04:38:22 2008 (Creative Audio Driver). Update here.


Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\BSOD\Downloads\041612-13812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\MS Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`01c08000 PsLoadedModuleList = 0xfffff800`01e4c650
Debug session time: Tue Apr 17 01:06:33.528 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:02.028
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {4, fffffa800abe0038, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000004, PCI Express Error
Arg2: fffffa800abe0038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x124_4

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  b

STACK_TEXT:  
fffff880`022f6988 fffff800`02202a3b : 00000000`00000124 00000000`00000004 fffffa80`0abe0038 00000000`00000000 : nt!KeBugCheckEx
fffff880`022f6990 fffff800`01d94b33 : 00000000`00000001 fffffa80`0abcbb10 00000000`00000000 fffffa80`0abcb1b0 : hal!HalBugCheckSystem+0x1e3
fffff880`022f69d0 fffff880`00fbbbcf : fffffa80`00000750 fffffa80`0abcbb10 00000000`00000000 fffffa80`0abdfab0 : nt!WheaReportHwError+0x263
fffff880`022f6a30 fffff880`00fbb5f6 : 00000000`00000000 fffff880`022f6b80 fffffa80`0aba4c00 fffff880`022f6b00 : pci!ExpressRootPortAerInterruptRoutine+0x27f
fffff880`022f6a90 fffff800`01c80adc : 00000000`00000000 fffff880`022f6b80 fffffa80`0aba4c00 00000000`00000001 : pci!ExpressRootPortInterruptRoutine+0x36
fffff880`022f6b00 fffff880`039b99c2 : fffff800`01c8d809 00000000`0027bd08 fffffa80`0d596dd8 00000000`ffffffed : nt!KiInterruptDispatch+0x16c
fffff880`022f6c98 fffff800`01c8d809 : 00000000`0027bd08 fffffa80`0d596dd8 00000000`ffffffed 000000bb`76ee1890 : intelppm+0x39c2
fffff880`022f6ca0 fffff800`01c7c95c : fffff880`022ce180 fffff880`00000000 00000000`00000000 fffff800`01d3d030 : nt!PoIdle+0x52a
fffff880`022f6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_4_PCIEXPRESS

BUCKET_ID:  X64_0x124_4_PCIEXPRESS

Followup: MachineOwner
---------

post #3 of 6
Thread Starter 
Thank you very much for the help.

I used your minidump guide to take a quick look and that was very helpful too.

I do have the latest bios and my pc is dust free. I clean it 2x a month with the metro vacuum electric duster, thing is a blast. I also make sure the fans do not spin so as not to damage them.

One thing I did last night was verify the cache of the game. This was recommended on the steam forums. After doing so I have not encountered a BSOD, but I will be running through these steps to make sure nothing is compromised - wouldn't want to run into problems down the line.

That driver is something I need to follow up on though. I recently did a fresh install, making sure to grab drivers and load in good order. I have an image of that tucked away, but what is odd is that sound driver is the latest creative driver for my card - released June, 16th 2010. I will contact Creative support with a question about ctac32k.sys showing July 2008. Some quick googling shows that to show up on more than a few people's BSOD dumps, even after they update.

Ok! Once I get home, memtest, chckdsk, and prime95 on the menu.

Thanks again, appreciate the good info!
Fep
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 D0 ASRock X58 Extreme Radeon 5850 x2 6x2GB Corsair XMS3 1600 
Hard DriveHard DriveHard DriveOS
Samsung 830 OCZ Vertex 3 2x WD5000AAJS Windows 7 x64 [Ultimate] & Linux Mint 
MonitorKeyboardPowerCase
3x ASUS VH242HL-P Razer BlackWidow Ultimate/Steelseries 6Gv2 OCZ ProXStream 1000W LianFish [Modded] 
MouseMouse PadAudioAudio
Razer DeathAdder 3G [Hyper Glide]/Logitech G9 SteelSeries QcK+/Puretrak Talent Creative X-Fi XtremeGamer NuForce uDac 
  hide details  
Reply
Fep
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 D0 ASRock X58 Extreme Radeon 5850 x2 6x2GB Corsair XMS3 1600 
Hard DriveHard DriveHard DriveOS
Samsung 830 OCZ Vertex 3 2x WD5000AAJS Windows 7 x64 [Ultimate] & Linux Mint 
MonitorKeyboardPowerCase
3x ASUS VH242HL-P Razer BlackWidow Ultimate/Steelseries 6Gv2 OCZ ProXStream 1000W LianFish [Modded] 
MouseMouse PadAudioAudio
Razer DeathAdder 3G [Hyper Glide]/Logitech G9 SteelSeries QcK+/Puretrak Talent Creative X-Fi XtremeGamer NuForce uDac 
  hide details  
Reply
post #4 of 6
My pleasure, I also appreciate the very detailed response and it's good to see you have things all planned out.

Good luck & keep me updated smile.gif
post #5 of 6
Thread Starter 
Ok, an update from over the weekend!

Seven passes of memtest passed.

12 hrs. Prime95.

Chkdsk no errors.

Ran GPUTool test for stability for 20 minutes and then played BF3 for a bit. Went to bed with computer on, at 4 a.m. it had crashed repeatedly as there were 7 dumps about 5-10 minutes apart. Ran some more GPUTool and BF3 and got two more BSODs, one while playing BF3 and the second 10 minutes after rebooting, but only browsing the internet. I had GPU-Z and HWMonitor and the only odd thing was the GPU Temp #2 on the Visiontek getting up to 95 degrees C @ 95% load. When I blue screened the second time temps were at idle, though Temp #2 was still 10 degrees hotter than Temp #1 and #3 (65 degrees vs 55).

I removed each card and tested it separately. 30 minutes of GPUTool test for stability and at least an hour of BF3. No BSODs, but still high heat on the Visontek's Temp #2 @ 95% load. Now when I put both cards back in I removed and installed the drivers again. I also disabled ULPS and removed the sound card.

Testing with GPUTool, it takes about 5 minutes for the Visiontek GPU Temp #2 to hit 95 degrees C where it caps (at least for the next 15 minutes), while GPU temp hits 83. The XFX card caps at 77 degrees C. The Visiontek temps seem high... should I run GPUTool for longer? I am afraid the 95 degrees will go up and it seems too high already. No odd noises from the fans, case is open with plenty of air right now too.

After playing BF3 for a bit no BSODs and nothing all day, but the high temp on the Visiontek when using GPUTool to stress still bothers me. If this high heat is abnormal... then I will have to follow up with Visiontek and their lifetime warranty.

Thanks for the help!

Missed a few things - both are reference cards and Temp # 2 on the Visiontek hits 89 degrees C @ 100% load during BF3. Still 10 degrees higher than the others.
Fep
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 D0 ASRock X58 Extreme Radeon 5850 x2 6x2GB Corsair XMS3 1600 
Hard DriveHard DriveHard DriveOS
Samsung 830 OCZ Vertex 3 2x WD5000AAJS Windows 7 x64 [Ultimate] & Linux Mint 
MonitorKeyboardPowerCase
3x ASUS VH242HL-P Razer BlackWidow Ultimate/Steelseries 6Gv2 OCZ ProXStream 1000W LianFish [Modded] 
MouseMouse PadAudioAudio
Razer DeathAdder 3G [Hyper Glide]/Logitech G9 SteelSeries QcK+/Puretrak Talent Creative X-Fi XtremeGamer NuForce uDac 
  hide details  
Reply
Fep
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 920 D0 ASRock X58 Extreme Radeon 5850 x2 6x2GB Corsair XMS3 1600 
Hard DriveHard DriveHard DriveOS
Samsung 830 OCZ Vertex 3 2x WD5000AAJS Windows 7 x64 [Ultimate] & Linux Mint 
MonitorKeyboardPowerCase
3x ASUS VH242HL-P Razer BlackWidow Ultimate/Steelseries 6Gv2 OCZ ProXStream 1000W LianFish [Modded] 
MouseMouse PadAudioAudio
Razer DeathAdder 3G [Hyper Glide]/Logitech G9 SteelSeries QcK+/Puretrak Talent Creative X-Fi XtremeGamer NuForce uDac 
  hide details  
Reply
post #6 of 6
95c is "somewhat" normal for a GPU stress testing tool, but NOT for gaming. Temperatures are only really an issue when you're at a constant 90c+ during gaming. If you saw no artifacts or crashes during the GPU Tool stability testing, disregard the temperatures.

However, if you did see crashing on a specific card in GPU Tool, which you did, then it's likely GPU related smile.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › CS:GO BSOD with Hal.dll