TechSpot

BSOD while gaming, unable to access dump

By SoloSmith
Aug 30, 2011
Post New Reply
  1. Hey all,

    I recently forked out a small bloomin fortune for a new PC, it appears to BSOD randomly during gaming. I've contacted the place where I bought it, they've offered to fix it but it will take 5-7 days and as I work online, I can't afford to be without a PC for that long.

    I cant access the dump files for some reason so have no idea what the problem is.

    Windows 7 64
    i7 3.4ghz
    8gb Ram
    Geforce GTX 560 ti

    Any help would be greatly appreciated, thanks :)

    P.S I've attached my Dxdiag if that's any help :)
     

    Attached Files:

  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

  3. SoloSmith

    SoloSmith TS Rookie Topic Starter

    That was a total pain in the backside, I've got access to the files now, thanks :D

    I've tried opening in notepad etc but just brings back jargon. I downloaded blue screen viewer

    hal.dll
    ntoskrnl.exe

    These are the files that appear to be causing the BSOD.

    Crash List

    ==================================================
    Dump File : 082911-15069-01.dmp
    Crash Time : 29/08/2011 18:35:18
    Bug Check String :
    Bug Check Code : 0x00000124
    Parameter 1 : 00000000`00000000
    Parameter 2 : fffffa80`085dc028
    Parameter 3 : 00000000`be200000
    Parameter 4 : 00000000`0005110a
    Caused By Driver : hal.dll
    Caused By Address : hal.dll+12a3b
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7cc40
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\082911-15069-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 293,104
    ==================================================

    ==================================================
    Dump File : 082511-14430-01.dmp
    Crash Time : 25/08/2011 15:36:07
    Bug Check String :
    Bug Check Code : 0x00000124
    Parameter 1 : 00000000`00000000
    Parameter 2 : fffffa80`086d6028
    Parameter 3 : 00000000`be200000
    Parameter 4 : 00000000`0005110a
    Caused By Driver : hal.dll
    Caused By Address : hal.dll+12a3b
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7cc40
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\082511-14430-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 293,152
    ==================================================

    ==================================================
    Dump File : 081711-11668-01.dmp
    Crash Time : 17/08/2011 01:47:08
    Bug Check String :
    Bug Check Code : 0x00000124
    Parameter 1 : 00000000`00000000
    Parameter 2 : fffffa80`08607028
    Parameter 3 : 00000000`be200000
    Parameter 4 : 00000000`0005110a
    Caused By Driver : hal.dll
    Caused By Address : hal.dll+12a3b
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7cc40
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\081711-11668-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 293,104
    ==================================================

    ==================================================
    Dump File : 081611-14929-01.dmp
    Crash Time : 16/08/2011 09:10:54
    Bug Check String :
    Bug Check Code : 0x00000124
    Parameter 1 : 00000000`00000000
    Parameter 2 : fffffa80`07f4a028
    Parameter 3 : 00000000`be200000
    Parameter 4 : 00000000`0005110a
    Caused By Driver : hal.dll
    Caused By Address : hal.dll+12a3b
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7cc40
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\081611-14929-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 293,120
    ==================================================

    ==================================================
    Dump File : 081511-11247-01.dmp
    Crash Time : 15/08/2011 22:05:00
    Bug Check String :
    Bug Check Code : 0x00000124
    Parameter 1 : 00000000`00000000
    Parameter 2 : fffffa80`07e2c028
    Parameter 3 : 00000000`be200000
    Parameter 4 : 00000000`0005110a
    Caused By Driver : hal.dll
    Caused By Address : hal.dll+12a3b
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7cc40
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\081511-11247-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 293,120
    ==================================================

    ==================================================
    Dump File : 080811-15537-01.dmp
    Crash Time : 08/08/2011 19:51:03
    Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x0000001e
    Parameter 1 : 00000000`00000000
    Parameter 2 : 00000000`00000000
    Parameter 3 : 00000000`00000000
    Parameter 4 : 00000000`00000000
    Caused By Driver : Rt64win7.sys
    Caused By Address : Rt64win7.sys+19cc0
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7fcd0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\080811-15537-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 293,160
    ==================================================

    ==================================================
    Dump File : 072911-19281-01.dmp
    Crash Time : 29/07/2011 08:27:56
    Bug Check String : DRIVER_POWER_STATE_FAILURE
    Bug Check Code : 0x1000009f
    Parameter 1 : 00000000`00000004
    Parameter 2 : 00000000`00000258
    Parameter 3 : fffffa80`06703040
    Parameter 4 : fffff800`00b9c3d0
    Caused By Driver : tcpip.sys
    Caused By Address : tcpip.sys+31400
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+824da
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\072911-19281-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 573,576
    ==================================================

    The 2 at the bottom seem to be unrelated to the others but not certain, any info would be great. Thanks
     
  4. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Really sorry for the delay. I have been having issues with my internet. Anyway, tcpip.sys is an MS driver that has to do with networking and internet protocol. Rt64win7.sys is a RealTech onboard video driver. I seriously doubt this is your issue in light of your 0x124 errors.

    0x124: WHEA_UNCORRECTABLE_ERROR and is described as "A fatal hardware error has occurred."

    This error code and definition has replaced the older XP code 0x9C: MACHINE_CHECK_EXCEPTION and though it is older the definition still is applicable: This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution. Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).

    Honestly, this is a very difficult error to work with because as it says a clear diagnosis rarely comes forth and I have never seen a minidump with either error codes give a definitive answer. I know IT techs that don't like working with it. What makes it so difficult is that it can be any hardware in your system -- and I mean any.

    Here are some of the causes that were determined to be the source of 0x124/0x9C errors from posters here and abroad: NIC, DVD/CD drives, dust build up around the CPU that caused overheating of said CPU, bulging capacitors hidden by heatsink, video card, psu, motherboard, and external harddrive connected by USB.

    * If any of your hardware is overclocked please put them back to default settings to see if you get system stability.


    See link: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
     
  5. SoloSmith

    SoloSmith TS Rookie Topic Starter

    Thanks very much for your time, much appreciated :D

    I'm going to go down the list and do what I can but my tech knowledge is lacking. I uninstalled my NIC/Audio and GPU drivers, have yet to bluescreen since but until I've been BSOD free for 3-4 days, I won't be sure.

    I know the CPU has been overclocked, the company that built the PC for me asked if I wanted to overclock it and said it would pose no risks. How would I go about taking it back to normal?

    I dont think its an overheating issue as my GPU hits 60 under strain with the rest of my PC being in the 30s, speedfan registers my CPU at -60. I also think it's a bit soon to be having dust problems as I have 3 fans and as the PC is so new and in a well ventilated room, I'm hoping it's ok but I will open it and take a look to be sure.

    Thanks again for your help.
     
  6. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Nice work on your part. :) Before we mess with the overclocking let's do what you first suggested and see if what you have already done continues stability.
     
  7. SoloSmith

    SoloSmith TS Rookie Topic Starter

    I bluescreened shortly after making that post so that didnt work lol

    I took it back into the shop, they ran stress tests etc overnight and couldn't find any problems at all. They set up multiple profiles for me, one overclocked, one at factory, I'm currently spending time testing both to see if any other issues arise.

    Thanks again for your help, your time is much appreciated :)
     
  8. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Glad to help. What tests did they do? Please keep us updated.
     
  9. SoloSmith

    SoloSmith TS Rookie Topic Starter

    He said he ran a 3D stress test, ran the CPU at 100% and tested the Ram. I couldn't play anything 3D for more than 3-4 hours without a BSOD so I have no idea how it didn't happen, sods law lol

    I'll switch between profiles over the next couple of days and will leave any info if theres any change.
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...