Windows 8 and 8.1 Forums


Irql_Gt_Zero_At_System_Service

  1. #1


    Posts : 27
    Windows 10 Pro 64-Bit & Linux Mint 18

    Irql_Gt_Zero_At_System_Service


    Details to start off:


    Windows 8.1 Pro x64
    R9 270 GPU
    600w Corsair PSU
    Samsung 840 EVO SSD
    8gb corsair vengeance RAM
    AMD Phenom 975 3.6ghz CPU

    -Clean install of windows 8 on the ssd
    -I used DDU to wipe all of amd's drivers, then downloaded the newest gpu drivers and installed them


    This all started after using Windows update to download all of the new updates. I also installed an ssd (840 evo) a few days ago and had no problems, but it was fine, until the update. Shouldn't be the ssd anyways since I tried my HDD and my pc froze once as well.
    I first experienced a freeze during a match of Dota 2, restarted multiple times and the freeze kept occurring only in-game, after certain big events occurred in the game usually. This problem is especially prominent when I'm playing Dota 2, considering it has only happened twice outside of it, once on my HDD and once on my SSD a few seconds after booting up. Today I got my first BSOD in a long time, on my SSD, while installing more windows updates..

    Event viewer's Windows logs contains many errors, which I'm not sure are normal or not. Picture: http://puu.sh/cFqXT/4771a040dd.png

    However, some very common errors seem to be as following:
    The AODDriver4.3 service failed to start due to the following error:
    The system cannot find the file specified.
    ((I deleted the AODDriver4.3 and 4.2.0 folder in regedit and this error went away))

    The Service KMSELDI service terminated unexpectedly. It has done this 1 time(s).

    I'd also like to point out that I did check the box in windows update for the AMD driver after I already had installed the AMD driver from the actual website, which could be a reason.. but it doesn't explain the freeze occurring on my HDD as well.



    (I'm not sure posting the memory.dmp debug log will help, but I didn't see it in the rar file so I put it here anyways)
    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    
    
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    
    
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    Machine Name:
    Kernel base = 0xfffff801`76e8e000 PsLoadedModuleList = 0xfffff801`771582d0
    Debug session time: Thu Nov  6 19:43:44.007 2014 (UTC - 8:00)
    System Uptime: 0 days 0:13:27.784
    Loading Kernel Symbols
    ...............................................................
    ......................................................Page 13ae5c not present in the dump file. Type ".hh dbgerr004" for details
    .........Page 13c3d3 not present in the dump file. Type ".hh dbgerr004" for details
    .
    .........................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00007ff7`cac03018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 4A, {7ffe8ffeb01a, 2, 0, ffffd001adb60cc0}
    
    
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+24b )
    
    
    Followup: MachineOwner
    ---------
    
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
    Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
    Arguments:
    Arg1: 00007ffe8ffeb01a, Address of system function (system call routine)
    Arg2: 0000000000000002, Current IRQL
    Arg3: 0000000000000000, 0
    Arg4: ffffd001adb60cc0, 0
    
    
    Debugging Details:
    ------------------
    
    
    
    
    PROCESS_NAME:  svchost.exe
    
    
    BUGCHECK_STR:  RAISED_IRQL_FAULT
    
    
    FAULTING_IP: 
    +4240f3c09f68
    00007ffe`8ffeb01a ??              ???
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    CURRENT_IRQL:  2
    
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff80176fedae9 to fffff80176fe1fa0
    
    
    STACK_TEXT:  
    ffffd001`adb60a88 fffff801`76fedae9 : 00000000`0000004a 00007ffe`8ffeb01a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd001`adb60a90 fffff801`76feda06 : ffffe000`0a4373c0 000000b9`5e12dab8 00000000`00000000 000000b9`00000218 : nt!KiBugCheckDispatch+0x69
    ffffd001`adb60bd0 00007ffe`8ffeb01a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x24b
    000000b9`5e12da98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`8ffeb01a
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nt!KiSystemServiceExit+24b
    fffff801`76feda06 4883ec50        sub     rsp,50h
    
    
    SYMBOL_STACK_INDEX:  2
    
    
    SYMBOL_NAME:  nt!KiSystemServiceExit+24b
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nt
    
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5318053f
    
    
    BUCKET_ID_FUNC_OFFSET:  24b
    
    
    FAILURE_BUCKET_ID:  RAISED_IRQL_FAULT_svchost.exe_nt!KiSystemServiceExit
    
    
    BUCKET_ID:  RAISED_IRQL_FAULT_svchost.exe_nt!KiSystemServiceExit
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:raised_irql_fault_svchost.exe_nt!kisystemserviceexit
    
    
    FAILURE_ID_HASH:  {a1a8b129-34ee-4922-e8da-a410dee6b5e4}
    
    
    Followup: MachineOwner
    ---------

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Sorry for the delay in responding. Do you still need help with this topic?
    If so, respond and I'll be notified by email.

    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
    NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.
    Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.


    While waiting for a reply, please try these suggestions:
    1. Get ALL available Windows Updates. It may take several trips to get them all
    2. Get ALL available, Windows 8.1 compatible updates from the manufacturer's website.
    3. Start with these free hardware diagnostics: Hardware Diagnostics
    4. If all of the hardware tests pass, then run Driver Verifier according to these instructions: Driver Verifier Settings
      My System SpecsSystem Spec

  3. #3


    Posts : 27
    Windows 10 Pro 64-Bit & Linux Mint 18


    Quote Originally Posted by usasma View Post
    Sorry for the delay in responding. Do you still need help with this topic?
    If so, respond and I'll be notified by email.

    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
    NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.
    Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.


    While waiting for a reply, please try these suggestions:
    1. Get ALL available Windows Updates. It may take several trips to get them all
    2. Get ALL available, Windows 8.1 compatible updates from the manufacturer's website.
    3. Start with these free hardware diagnostics: Hardware Diagnostics
    4. If all of the hardware tests pass, then run Driver Verifier according to these instructions: Driver Verifier Settings
    oddly enough, the problem fixed itself.
      My System SpecsSystem Spec

  4. #4


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Sometimes they do that. The original BSOD for XP and later would suggest that you just reboot after the first one and wait and see if there was another. And, funny thing, they often fixed themselves!

    Should the problem show up again, I am subscribed to this topic and will get notified (by email) that you have replied.
    Good luck!
      My System SpecsSystem Spec

Irql_Gt_Zero_At_System_Service
Related Threads
BSOD, error IRQL_GT_ZERO_AT_SYSTEM_SERVICE in BSOD Crashes and Debugging
Hi! So i was watching movie online and decided to open program named Bluestacks when my computer crashed and i got BSOD named IRQL_GT_ZERO_AT_SYSTEM_SERVICE. I used SF_Diagnostics_Tool and used grab all method. I also added CBS log file which i got from sfc /scannow , it say'd it couldnt fix...
BSOD, error IRQL_GT_ZERO_AT_SYSTEM_SERVICE in BSOD Crashes and Debugging
The BSOD's started getting really violent yesterday. I was ready to throw my laptop out the window. I've had it for about 4-5 months, bought brand new from Futureshop. I got one blue screen once shortly after I bought it, like two months ago or something, but I don't remember what the error was,...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook