Ntoskrnl.exe causing BSOD while gaming.

Discussion in 'Software' started by coloradooo3, Apr 11, 2011.

  1. coloradooo3

    coloradooo3 Private E-2

    I have checked the forums for similar problems, and found 100's of them, but each one was different.

    I get BSOD when playing games. Its alright while doing anything but gaming. When ever i play Crysis 2, or FO:NV 10min-1hour in to the game i receive a BSoD. WhoCrashed and BlueSceenViewer insist its a ntoskrnl.exe problem.

    I upgraded most of my drivers to latest versions, updated Bios, ran Memtest86+ for 8 passes (no problems found), ran Seagate (no problems found).

    Im running out of options here. Any suggestions?
     
  2. satrow

    satrow Major Geek Extraordinaire

    If the BSOD is consistent, the same error every time, go to C:\Windows\Minidump and copy the latest minidump file to your Desktop, zip and upload it here, I'll try to interpret it.

    You've checked that it's not heat-related?

    How to attach items to your post.
     
  3. coloradooo3

    coloradooo3 Private E-2

    These are the Minidumps created today.
     

    Attached Files:

  4. satrow

    satrow Major Geek Extraordinaire

    I don't see any obviously old or suspect 3rd party drivers loaded, I do see signs that make me think it may be an ATA/IDE problem, WinDebug gives hardware as being the cause.

    Is 8 minutes uptime long enough for you to update the motherboard chipset drivers? What 'board is it?
    Code:
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8004b54228, 0, 0}
    
    Probably caused by : [B]hardware[/B]
    
    Followup: MachineOwner
    ---------
    
    2: 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: 0000000000000000, Machine Check Exception
    Arg2: fffffa8004b54228, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`033b66b0 fffff800`03528d29 : fffffa80`04b54200 fffffa80`03a0fb60 00000000`00000002 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`033b6bd0 fffff800`03408217 : fffffa80`04b54200 fffff800`03482658 fffffa80`03a0fb60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`033b6c00 fffff800`0336f865 : fffff800`034e43a0 00000000`00000001 fffffa80`047bfb90 fffffa80`03a0fb60 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`033b6c40 fffff800`032efa21 : fffff880`00c3be00 fffff800`0336f840 fffffa80`03a0fb00 fffff800`03484658 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`033b6c70 fffff800`03582cce : 00000000`00000000 fffffa80`03a0fb60 00000000`00000080 fffffa80`039fc5f0 : nt!ExpWorkerThread+0x111
    fffff880`033b6d00 fffff800`032d6fe6 : fffff880`03164180 fffffa80`03a0fb60 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033b6d40 00000000`00000000 : fffff880`033b7000 fffff880`033b1000 fffff880`039e6500 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME:[B] hardware[/B]
    
    IMAGE_NAME:  [B]hardware[/B]
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    Sevenforums troubleshooting 0x124.
     
  5. coloradooo3

    coloradooo3 Private E-2

    My motherboard is Asus P5P43TD, chipset is upgraded to 9.1.1.1014 which is supposedly, latest.

    EDIT: I also have 2 bootable OS. W7 x86 and W7 x64. Exact same BlueScreenView and WhoCrashed, reports, on both OS's. Been having these for 4 months now, but rarely (1/2months) until recently. Or could i say until SP1 came around. Been placing my suspicion on that.
     
  6. coloradooo3

    coloradooo3 Private E-2

    Also, this could not be heat related, because BSoD's occurred even at 60C VGA temps. CPU temps never, even under test load, got over 54C.
     
  7. satrow

    satrow Major Geek Extraordinaire


MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds