BSOD WHILE GAMING ks.sys ntoskrnl.exe

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Jim Lahey, Aug 4, 2012.

  1. Jim Lahey

    Jim Lahey New Member

    Aug 4, 2012
    Likes Received:
    Hey guys, i come to you with an issue i have been trying to work out for months now.

    I constantly get BSOD while gaming. ive done a memtest, replaced the ram, replaced the video card, ran chkdsk, uninstalled usual suspects avast daemon tools etc., and nothing. the most prevalent error message is DRIVER_IRQL_NOT_LESS_OR_EQUAL. ive attached a zip with all my dmp files. i would really appreciate if someone could take a look at them and help me out.View attachment DMP.zipView attachment
  2. Trouble

    Trouble Noob Whisperer

    Nov 30, 2009
    Likes Received:
    Let's start with your Creative SB Audigy LS
    P17.sys 3/2/2009
    Physically remove the card, uninstall any associated software and double check C:\Windows\System32\Drivers and confirm that the driver P17.sys is no longer present, otherwise rename to P17.OLD
    Perhaps try using the integrated sound on the MoBo or obtain another more current card. See if the machines stabilizes.
    While you're at it update this driver as well
    Rt64win7.sys 2/26/2009 from here Realtek
    If Blue Screens persist, then;
    Please read the first post in this sticky thread here How to ask for help with a BSOD problem
    Do your best to accumulate the data required.
    Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
    Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
    Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.

    Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area .
  3. Jim Lahey

    Jim Lahey New Member

    Aug 4, 2012
    Likes Received:
    after removing my audio card i tried playing a game to see if i would get a crash and i did, but there was no blue screen, it just restarted instantly without warning.

    Download Seven | here is the required info
  4. Trouble

    Trouble Noob Whisperer

    Nov 30, 2009
    Likes Received:
    Your most recent dump file (080412-14078-01.dmp) is a hardware BugCheck 124 0x124_AuthenticAMD
    You had an identical BSOD on June 11th (061112-14031-01.dmp)
    Generally speaking these are frequently associated with Over Clocking (not always but often) so if you are currently doing anything like that please return any and all overclock settings to Normal / Defaults.
      Processor Manufacturer        AMD              
      Processor ID                  430f1000fffb8b17
      Processor Version             AMD Phenom(tm) II X4 980 Processor                  
      Processor Voltage             8fh - 1.5V
      External Clock                200MHz
    [U][B]  Max Speed                     [COLOR=#ff0000]3885MHz[/COLOR]
      Current Speed                 [COLOR=#ff0000]3885MHz[/COLOR][/B][/U]
    Seems a peculiar setting

    Additionally they can be cause by a host of other conditions as well, not the least of which are temperature related issues that may be a result of poor ventilation / circulation and or dust or other obstructive elements preventing heat dissipation.
    Looks like you may be a BIOS version or two behind
    BiosVendor = American Megatrends Inc.
    BiosVersion = P1.60
    BiosReleaseDate = 05/20/2010
    Check here ASRock > Products > M3A770DE and consider bring that up to date.
    [U][B]BugCheck [COLOR=#ff0000]124[/COLOR][/B][/U], {0, fffffa8005084028, b47aa000, 145}
    [COLOR=#ff0000][U][B]Probably caused by : hardware[/B][/U][/COLOR]
    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.
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8005084028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b47aa000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000145, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_AuthenticAMD
    PROCESS_NAME:  audiodg.exe
    fffff880`02f6ba88 fffff800`033fda3b : 00000000`00000124 00000000`00000000 fffffa80`05084028 00000000`b47aa000 : nt!KeBugCheckEx
    fffff880`02f6ba90 fffff800`02f8fb03 : 00000000`00000001 fffffa80`050de5d0 00000000`00000000 fffffa80`050de620 : hal!HalBugCheckSystem+0x1e3
    fffff880`02f6bad0 fffff800`033fd700 : 00000000`00000728 fffffa80`050de5d0 fffff880`02f6be30 00000000`00000000 : nt!WheaReportHwError+0x263
    fffff880`02f6bb30 fffff800`033fd052 : fffffa80`050de5d0 fffff880`02f6be30 fffffa80`050de5d0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`02f6bc80 fffff800`033f0e8f : 00000000`00259930 00000000`00000001 fffff880`02f6beb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`02f6bcc0 fffff800`02e80aac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`02f6bcf0 fffff800`02e80913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`02f6be30 000007fe`f77171a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0307faf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f77171a0
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: hardware
    IMAGE_NAME:  hardware
    FAILURE_BUCKET_ID:  [U][B]X64_0x124_AuthenticAMD_[COLOR=#ff0000]PROCESSOR_CACHE[/COLOR][/B][/U]
    BUCKET_ID:  [U][B]X64_0x124_AuthenticAMD_[COLOR=#ff0000]PROCESSOR_CACHE[/COLOR][/B][/U]
    Finally in some rare instances Motherboard software may be directly or indirectly causing the issue. I couldn't help but notice that you have two instances of AMD Overdrive OR EasyTune6
    AODDriver2.sys 1/16/2012
    AODDriver2.sys 3/6/2012
    My suggestion would be to uninstall it or them and check C:\Windows\System32\Drivers to confirm they are no longer present and loading.
    Common Platform Error Record @ fffffa8005084028
    Record Id     : 01cd727733a97753
    Severity      : [B]Fatal [/B](1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : [B]Machine Check Exception[/B]
    Timestamp     : 8/4/2012 20:07:29
    Flags         : 0x00000000
    Section 0     : Processor Generic
    Descriptor    @ fffffa80050840a8
    Section       @ fffffa8005084180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : [B]Fatal[/B]
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : [B]Cache error[/B]
    Operation     : [B]Data Write[/B]
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000100f43
    Processor ID  : 0x0000000000000002
    Instr Pointer : 0x0x000007fef77171a0
    Section 1     : x86/x64 Processor Specific
    Descriptor    @ fffffa80050840f0
    Section       @ fffffa8005084240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : [B]Fatal[/B]
    Local APIC Id : 0x0000000000000002
    CPU Id        : 43 0f 10 00 00 08 04 02 - 09 20 80 00 ff fb 8b 17
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    Proc. Info 0  @ fffffa8005084240
    Section 2     : x86/x64 MCA
    Descriptor    @ fffffa8005084138
    Section       @ fffffa80050842c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : [B]Fatal[/B]
    Error         : [B][COLOR=#ff0000]DCACHEL1_DWR_ERR[/COLOR] (Proc 2 Bank 0)[/B]
      Status      : 0xb47aa00000000145
      Address     : 0x0000000107260b00
      Misc.       : 0x0000000000000000

Share This Page