Windows 8 BSOD (SYSTEM_SERVICE_EXCEPTION)

Discussion in 'Operating Systems' started by Rvenger, Feb 10, 2013.

  1. Rvenger

    Rvenger Elite Member <br> Super Moderator <br> Video Cards
    Super Moderator

    Joined:
    Apr 6, 2004
    Messages:
    6,293
    Likes Received:
    4
    Hi All,

    I was wondering if anyone ran into this BSOD. It seems like a common issue because my main rig just blue screened on me with a "SYSTEM_SERVICE_EXCEPTION" name. My Windows 8 laptop did this constantly until I searched and found out that it was a common issue with Windows 8. I installed Windows 7 on my laptop and all problems went away. Now my main rig is doing the same and it's gotta be an application or driver causing it. The strange thing is that everytime it BSOD with System service exception, it shows a different DLL that caused the problem every time.


    Did anyone run into this issue with windows 8 before?


    Thanks!

    R
     
  2. Loading...

    Similar Threads - Windows BSOD (SYSTEM_SERVICE_EXCEPTION) Forum Date
    Windows 10 random BSOD's Operating Systems Aug 22, 2017
    Windows 10 Bootup BSOD Issue Operating Systems Apr 9, 2017
    tcpip.sys causing BSOD in Windows 10 x64 Operating Systems Dec 8, 2016
    Random BSODs on Windows 10 Pro Operating Systems Dec 28, 2015
    Windows 8.1 Update BSODs Operating Systems Apr 23, 2014

  3. Pardus

    Pardus Diamond Member

    Joined:
    Jun 29, 2000
    Messages:
    8,157
    Likes Received:
    15
    comment removed
     
    #2 Pardus, Feb 10, 2013
    Last edited: Feb 18, 2013
  4. Rvenger

    Rvenger Elite Member <br> Super Moderator <br> Video Cards
    Super Moderator

    Joined:
    Apr 6, 2004
    Messages:
    6,293
    Likes Received:
    4
    Yeah, I already googled it and many laptops have this issue. I did pull the memory dump file. I think it might have been the AMD 13.2 beta 4 drivers that caused the issue. I just did a clean install so we will see if it comes back. I decided if the issue comes back then I will just load Windows 7 back on my main rig. Windows 8 just seems like it's very sensitive to hardware changes and driver updates.


    FAULTING_MODULE: fffff8021067e000 nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 51082517
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP:
    atikmpag+4615d
    fffff880`04f1b15d 488b9190000000 mov rdx,qword ptr [rcx+90h]
    CONTEXT: fffff8800853c0b0 -- (.cxr 0xfffff8800853c0b0)
    rax=fffff8a00dafe3c0 rbx=0000000100000340 rcx=0000000000340000
    rdx=0000000000000030 rsi=fffffa80247cf5c0 rdi=fffffa80225c6600
    rip=fffff88004f1b15d rsp=fffff8800853cab0 rbp=fffff8800853cab0
    r8=0000000000000035 r9=0000000000340000 r10=0000000000000801
    r11=fffff8800853d3f0 r12=00000000c0001740 r13=fffff8a00d5ca800
    r14=fffffa80225c6640 r15=0000000000000000
    iopl=0 nv up ei pl nz na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
    atikmpag+0x4615d:
    fffff880`04f1b15d 488b9190000000 mov rdx,qword ptr [rcx+90h] ds:002b:00000000`00340090=????????????????
    Resetting default scope
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x3B
    CURRENT_IRQL: 0
    LAST_CONTROL_TRANSFER: from fffff88004f13992 to fffff88004f1b15d
    STACK_TEXT:
    fffff880`0853cab0 fffff880`04f13992 : 00000000`00000000 fffff880`0853cae0 fffffa80`247cf5c0 fffff8a0`0ddd2500 : atikmpag+0x4615d
    fffff880`0853cac0 fffff880`0554d80b : fffffa80`225c6640 fffffa80`225c6640 00000000`0000001c fffff880`0853cd80 : atikmpag+0x3e992
    fffff880`0853caf0 fffff880`05566340 : fffff880`0853cb60 fffff880`0555c89a 00000000`00000000 fffff880`0853cb60 : atikmdag+0x9c80b
    fffff880`0853cb30 fffff880`0555f0db : 00000000`00000000 fffff880`0554d813 fffffa80`0cb2b048 fffffa80`225c4c80 : atikmdag+0xb5340
    fffff880`0853cb60 fffff880`05565305 : fffffa80`247cf5c0 fffff880`0853cce0 00000000`00000001 fffff880`0853cce0 : atikmdag+0xae0db
    fffff880`0853cbb0 fffff880`04ee021f : fffffa80`225c6660 fffff880`00000000 fffff8a0`00000000 00000000`00000370 : atikmdag+0xb4305
    fffff880`0853cc70 fffff880`0433d2b4 : fffffa80`225c4c80 fffff880`0853d750 00000000`00000000 fffff8a0`0295f000 : atikmpag+0xb21f
    fffff880`0853cf50 fffff880`042e835e : fffff880`0853d750 fffff880`0853d7a1 00000000`00000001 00000000`00000000 : dxgkrnl!DpiGetDriverVersion+0xe48
    fffff880`0853cfa0 fffff880`042e6d03 : fffff8a0`0295f000 fffff880`0853d750 fffff880`0853d490 fffff8a0`012d7d90 : dxgkrnl!g_TdrForceTimeout+0x1f776
    fffff880`0853d050 fffff880`042e56f5 : fffff880`00000799 fffff880`0853d7a1 00000000`00000000 00000000`00000701 : dxgkrnl!g_TdrForceTimeout+0x1e11b
    fffff880`0853d6c0 fffff880`042dfac9 : fffff8a0`00000238 fffff8a0`0d47b950 fffff8a0`0d5cd880 00000000`00000000 : dxgkrnl!g_TdrForceTimeout+0x1cb0d
    fffff880`0853d7e0 fffff880`042df737 : 0000002b`6525e2f0 00000000`887a0005 fffff8a0`00000001 fffff8a0`0d5cd800 : dxgkrnl!g_TdrForceTimeout+0x16ee1
    fffff880`0853d9d0 fffff802`106f8053 : 0000002b`6525e2f0 00000000`00000020 0000002b`6525e750 00000000`00000001 : dxgkrnl!g_TdrForceTimeout+0x16b4f
    fffff880`0853db00 000007fb`7ef0233a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSaveStateForHibernate+0x2a33
    0000002b`6525e298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fb`7ef0233a
     
  5. ViRGE

    ViRGE Elite Member, Moderator Emeritus

    Joined:
    Oct 9, 1999
    Messages:
    31,321
    Likes Received:
    79
    "atikmpag" gives it away. That's an AMD driver component.

    BTW, was 13.2 certified for laptops? I thought it was only for desktops?
     
  6. uallas5

    uallas5 Senior member

    Joined:
    Jun 3, 2005
    Messages:
    463
    Likes Received:
    35
    Maybe a stupid question, but wouldn't be easier to just not use BETA drivers vs formatting the drive, installing a different OS, re-installing your games, progs, restoring backup data, etc., etc., etc.?

    And no I haven't gotten that error on either of my Win8 laptops nor my gaming rig.
     
  7. Mushkins

    Mushkins Golden Member

    Joined:
    Feb 11, 2013
    Messages:
    1,635
    Likes Received:
    0
    The 13.2 betas fixed a lot of major issues people were having with DX9c games. You also dont need to reformat to roll back drivers if they give you a problem, just uninstall them and reinstall the old stuff.
     
  8. Rvenger

    Rvenger Elite Member <br> Super Moderator <br> Video Cards
    Super Moderator

    Joined:
    Apr 6, 2004
    Messages:
    6,293
    Likes Received:
    4
    I knew I didn't have to do a clean install, I just did it out of frustration. It seems to be working well now and I just started using the 13.1 drivers as well. Windows 7 works perfectly fine, I just think Windows 8 has some serious driver issues.


    Virge, 13.2 was never installed on my laptop. It was 12.10 that is on the laptop.