Windows 10: BSOD after switching into performance mode.

Discus and support BSOD after switching into performance mode. in Windows 10 BSOD Crashes and Debugging to solve the problem; I started getting BSODs after I switched into performance mode in bios. I have since switched back to normal mode, and have been using instant online... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by jaredsutphin, Jul 13, 2018.

  1. JAREDSUTPHIN
    jaredsutphin Win User

    BSOD after switching into performance mode.


    I started getting BSODs after I switched into performance mode in bios. I have since switched back to normal mode, and have been using instant online crash analysis to try and decipher the mini dumps, but I don't know what i'm looking for/ at. I have spent around 5 plus hours trying to figure this out on my own with no success. Any help is greatly appreciated.


    If you need the actual mini dump files I can figure out how to get them to u somehow. These are just copy and pasted from http://www.osronline.com/page.cfm?name=Analyze


    mini dump 1:


    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff802c1e9e8a2, Address of the instruction which caused the bugcheck
    Arg3: fffffc048f4f3fd0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    Debugging Details:
    ------------------

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    nt!KxWaitForLockOwnerShipWithIrql+12
    fffff802`c1e9e8a2 48890a mov qword ptr [rdx],rcx

    CONTEXT: fffffc048f4f3fd0 -- (.cxr 0xfffffc048f4f3fd0)
    rax=0000000000000000 rbx=ffffc98cdb095830 rcx=fffffc048f4f4a20
    rdx=0200000000000000 rsi=ffffc98cdc639080 rdi=fffffc048f4f4a20
    rip=fffff802c1e9e8a2 rsp=fffffc048f4f49c0 rbp=fffffc048f4f4b80
    r8=fffffc048f4f4a58 r9=0000000000000005 r10=ffffc98cdb095890
    r11=0000000000000000 r12=00000000039bf000 r13=0000000005cdfda0
    r14=0000000000000055 r15=0000000000000001
    iopl=0 nv up di ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010082
    nt!KxWaitForLockOwnerShipWithIrql+0x12:
    fffff802`c1e9e8a2 48890a mov qword ptr [rdx],rcx ds:002b:02000000`00000000=????????????????
    Resetting default scope

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: Discord.exe

    CURRENT_IRQL: 0

    BAD_PAGES_DETECTED: a02a

    LAST_CONTROL_TRANSFER: from fffff802c1f1fa39 to fffff802c1e9e8a2

    STACK_TEXT:
    fffffc04`8f4f49c0 fffff802`c1f1fa39 : ffffc98c`db095830 00000000`00000000 fffffc04`8f4f4b80 00000000`00000000 : nt!KxWaitForLockOwnerShipWithIrql+0x12
    fffffc04`8f4f49f0 ffffda41`845f125a : 00000000`00000000 ffffda41`845e9f02 00000000`00000000 00000000`00000000 : nt!ExReleaseResourceAndLeaveCriticalRegion+0x109
    fffffc04`8f4f4a50 ffffda41`845baf28 : 00000000`00000000 fffffc04`8f4f4b80 00000000`00000000 ffffda00`82f62a20 : win32kbase!UserSessionSwitchLeaveCrit+0x4a
    fffffc04`8f4f4a90 fffff802`c2040a43 : ffffc98c`dc639080 00000000`7435a2a0 00000000`00000020 00000000`0872fb90 : win32kbase!NtUserGetAsyncKeyState+0x188
    fffffc04`8f4f4b00 00000000`77301e4c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`05cdf1d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77301e4c


    SYMBOL_NAME: PAGE_NOT_ZERO

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    STACK_COMMAND: .cxr 0xfffffc048f4f3fd0 ; kb

    BUCKET_ID: PAGE_NOT_ZERO

    Followup: MachineOwner






    Mini Dump 2:


    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80250c68cc4, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception

    Debugging Details:
    ------------------

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    OVERLAPPED_MODULE: Address regions for 'peauth' and 'dump_storpor' overlap

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    nt!KxWaitForLockOwnerShip+14
    fffff802`50c68cc4 48890a mov qword ptr [rdx],rcx

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: ffffffffffffffff

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPagedPoolEnd
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
    ffffffffffffffff

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    BUGCHECK_STR: 0x1e_c0000005

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    BAD_PAGES_DETECTED: 78be

    EXCEPTION_RECORD: ffffbc87e364f030 -- (.exr 0xffffbc87e364f030)
    Cannot read Exception record @ ffffbc87e364f030

    TRAP_FRAME: 0000000000000002 -- (.trap 0x2)
    Unable to read trap frame at 00000000`00000002

    LAST_CONTROL_TRANSFER: from fffff80250e67a8a to fffff80250db4430

    CONTEXT: 1d85c3ff00000000 -- (.cxr 0x1d85c3ff00000000)
    Unable to read context, Win32 error 0n30

    STACK_TEXT:
    ffff9289`60052338 fffff802`50e67a8a : 00000000`0000001e ffffffff`c0000005 fffff802`50c68cc4 00000000`00000000 : nt!KeBugCheckEx
    ffff9289`60052340 fffff802`50dbcd0d : fffff802`51019000 fffff802`50c1c000 0005961c`00961000 ffffbc87`e7a95dd0 : nt!KiFatalExceptionHandler+0x22
    ffff9289`60052380 fffff802`50c73b06 : ffff9289`600524b0 ffff9289`60052970 00000000`00000000 ffff9289`60053288 : nt!RtlpExecuteHandlerForException+0xd
    ffff9289`600523b0 fffff802`50c74f23 : ffff9289`60053288 ffff9289`60052fd0 ffff9289`60053288 ffff9289`60053560 : nt!RtlDispatchException+0x416
    ffff9289`60052aa0 fffff802`50dc5042 : ffffbc87`e364f030 ffffbc87`e4a8e323 00000000`00000002 fffff802`50d924f1 : nt!KiDispatchException+0x1f3
    ffff9289`60053150 fffff802`50dc179c : ffff9289`60053320 fffff802`50cb789a 00000000`00000001 00000000`00000002 : nt!KiExceptionDispatch+0xc2
    ffff9289`60053330 fffff802`50c68cc4 : 00000000`00000001 ffff9289`600537b0 00000000`000000fc ffff9289`60050000 : nt!KiGeneralProtectionFault+0x2dc
    ffff9289`600534c0 fffff802`50d18623 : ffffbc87`e563bcc0 00000000`00000003 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x14
    ffff9289`600534f0 fffff802`f5a23d59 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x53
    ffff9289`60053520 fffff802`f5a227f8 : 00000026`cf7b4a0d fffff802`f5512ca2 00000000`00409690 fffff802`50cbbea0 : tcpip!TcpProcessExpiredTcbTimers+0x39
    ffff9289`60053620 fffff802`50cb6017 : ffffdf00`90bcaf80 ffff9289`60053a10 ffffbc87`e57b8728 ffffdf00`90bc8180 : tcpip!TcpPeriodicTimeoutHandler+0x3a8
    ffff9289`60053910 fffff802`50cb566b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x2e7
    ffff9289`60053a50 fffff802`50db7b8a : ffffffff`00000000 ffffdf00`90bc8180 00000000`00000000 ffffdf00`90bd8200 : nt!KiRetireDpcList+0x1db
    ffff9289`60053c60 00000000`00000000 : ffff9289`60054000 ffff9289`6004e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


    SYMBOL_NAME: PAGE_NOT_ZERO

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    STACK_COMMAND: .cxr 0x1d85c3ff00000000 ; kb

    BUCKET_ID: PAGE_NOT_ZERO

    Followup: MachineOwner





    Mini Dump 3:

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff8013480c8a2, Address of the instruction which caused the bugcheck
    Arg3: ffffb60a95db7c90, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    Debugging Details:
    ------------------

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    nt!KxWaitForLockOwnerShipWithIrql+12
    fffff801`3480c8a2 48890a mov qword ptr [rdx],rcx

    CONTEXT: ffffb60a95db7c90 -- (.cxr 0xffffb60a95db7c90)
    rax=0000000000000000 rbx=ffffa105e0b81d70 rcx=ffffb60a95db86e8
    rdx=0200000000000000 rsi=ffffa105e0d75080 rdi=ffffb60a95db86e8
    rip=fffff8013480c8a2 rsp=ffffb60a95db8680 rbp=ffffb60a95db8718
    r8=ffffb60a95db8740 r9=0000000000000006 r10=ffffa105e0b81dd0
    r11=ffffb60a95db84f0 r12=0000000000000002 r13=0000000000000000
    r14=000000000000ff00 r15=ffffa105e0b81dd0
    iopl=0 nv up di ng nz na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010086
    nt!KxWaitForLockOwnerShipWithIrql+0x12:
    fffff801`3480c8a2 48890a mov qword ptr [rdx],rcx ds:002b:02000000`00000000=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: csrss.exe

    CURRENT_IRQL: 0

    BAD_PAGES_DETECTED: 6419

    LAST_CONTROL_TRANSFER: from fffff80134879e93 to fffff8013480c8a2

    STACK_TEXT:
    ffffb60a`95db8680 fffff801`34879e93 : ffffa105`e0b81d70 00000000`00000003 00000000`0025d625 00000000`00000001 : nt!KxWaitForLockOwnerShipWithIrql+0x12
    ffffb60a`95db86b0 fffff801`3488bbd2 : ffffa105`e2cbc802 00000000`00000004 ffffc781`849c8180 00000000`00000000 : nt!ExpApplyPriorityBoost+0x533
    ffffb60a`95db8740 fffff801`3488af1f : 00000000`00000202 00000000`00000000 00000000`00000000 ffffec85`c286d250 : nt!ExpAcquireResourceExclusiveLite+0x332
    ffffb60a`95db87d0 ffffecc7`7cbe644c : ffffa105`e0d1a8e0 ffffecc7`7cbf125a 00000000`0040968f ffffec85`c016e002 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x3f
    ffffb60a`95db8810 ffffecc7`7c85886d : 00000000`00000001 ffffb60a`95db8960 ffffecc7`7cb247d0 00000000`00000004 : win32kbase!LegacyInputDispatcher::WaitAndDispatch+0x4c
    ffffb60a`95db8860 ffffecc7`7cc4b31b : ffffa105`e0d75080 ffffa105`e0d75080 00000000`00000000 00000000`00000005 : win32kfull!RawInputThread+0x67d
    ffffb60a`95db8a90 ffffecc7`7c84f4fe : ffffa105`00000002 ffffb60a`95a60dd0 ffffa105`e0d75080 00000000`00000000 : win32kbase!xxxCreateSystemThreads+0x9b
    ffffb60a`95db8ad0 fffff801`349aea43 : ffffa105`e0d75080 00000000`00000005 000001b2`03604310 00000000`00000008 : win32kfull!NtUserCallNoParam+0x5e
    ffffb60a`95db8b00 00007ffc`fc001124 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    0000008e`0007fa88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffc`fc001124


    SYMBOL_NAME: PAGE_NOT_ZERO

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    STACK_COMMAND: .cxr 0xffffb60a95db7c90 ; kb

    BUCKET_ID: PAGE_NOT_ZERO

    Followup: MachineOwner
    ---------

    :)
     
    jaredsutphin, Jul 13, 2018
    #1
  2. MARILOU SER
    Marilou Ser Win User

    Airplane mode switch not working

    Since the troubleshooting steps that were provided did not resolve the issue, we suggest switching on the Radio Management Service. To do that, please follow the steps below:

    • Press Windows key + R.
    • Type services.msc, then hit Enter.
    • Search for Radio Management Service.
    • Right-click, then choose Start.

    Note: Never ever set this service to "Disabled".

    Get back to us if the steps won't work.
     
    Marilou Ser, Jul 13, 2018
    #2
  3. ALEXSUBRI
    alexsubri Win User
    BSOD- atikmpag.sys

    This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:
    • Drivesweeper all drivers & in Safe Mode
    • Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
    • After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers
    BSOD after switching into performance mode. [​IMG]


    Once your done, restart the PC and then try installing the latest drivers.


    I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

    Best of luck! *Toast :toast:
     
    alexsubri, Jul 13, 2018
    #3
  4. ALDEN REY
    Alden Rey Win User

    BSOD after switching into performance mode.

    switching from tablet mode to laptop mode

    Hi,

    The concern you have encountered may be due to a corrupted file or a misconfigured setting. Windows 10's Tablet Mode provides a more touch-friendly experience by making all applications run at full screen and giving you a Start screen instead of a Start Menu.
    If you have a 2-in-1 device, Windows 10 asks you if you want to enter tablet mode every time you convert your notebook into a slate. Kindly follow the steps below to sort out the concern:

    • Click Settings from the Start menu
    • Click System, then select Tablet Mode in the left panel. A tablet mode submenu appear
    • Toggle "Make Windows more touch-friendly . . ." to on to enable Tablet mode. Or off to go to desktop mode
    • Configure the "When this device automatically switches" menu to let Windows 10 to switch modes on your 2-in-1 prompt or not prompt you.

    Should you have further concerns, feel free to post.

    Regards.
     
    Alden Rey, Jul 13, 2018
    #4
Thema:

BSOD after switching into performance mode.

Loading...

  1. BSOD after switching into performance mode. - Similar Threads - BSOD switching performance

  2. S mode performance

    in Windows 10 Gaming
    S mode performance: I have recently been gifted a HP pavillion laptop with windows 11 S mode preloaded and Have and intel Pentium Silver processor and want to no if S mode switching is a bad idea because it is a 1 way street and I dont know if this will have any impact on my performance...

  3. S mode performance

    in Windows 10 Software and Apps
    S mode performance: I have recently been gifted a HP pavillion laptop with windows 11 S mode preloaded and Have and intel Pentium Silver processor and want to no if S mode switching is a bad idea because it is a 1 way street and I dont know if this will have any impact on my performance...

  4. Performance mode

    in Windows 10 Gaming
    Performance mode: Hello everyone. I would like to ask whether performance mode in Windows 11 improves the performance of a laptop regarding system animations, Edge browsing or Office 365 use. I am not referring to demanding tasks like gaming or video editing, but to the aforementioned ones -...

  5. Performance mode

    in Windows 10 Software and Apps
    Performance mode: Hello everyone. I would like to ask whether performance mode in Windows 11 improves the performance of a laptop regarding system animations, Edge browsing or Office 365 use. I am not referring to demanding tasks like gaming or video editing, but to the aforementioned ones -...

  6. Ultra Performance Mode

    in Windows 10 Performance & Maintenance
    Ultra Performance Mode: I had to reinstall Windows to put it on my NVME. Before when it was on my SSD, I had the option for Ultra Performance Mode for the power options. Now with windows reinstalled and etc. The option is no longer there. All I see is Balanced, High and Power Saver. How come? Where...

  7. Significantly reduced performance after switching to windows 10

    in Windows 10 BSOD Crashes and Debugging
    Significantly reduced performance after switching to windows 10: I recently switched the OS on my acer laptop from Linux to windows due to server issues on my linux machine. Since switching I have noticed a dramatic reduction in the performance of my laptop. My laptop now runs much hotter than before, my fan is running at max speed...

  8. BSoD after motherboard switch

    in Windows 10 BSOD Crashes and Debugging
    BSoD after motherboard switch: Hello ! So today I changed my motherboard from a MSI B450M-A PRO MAX to an AORUS B550 Elite. When I booted up my PC, everything seemed normal, but a few seconds after I sign in I get a BSoD with error code SYSTEM_SERVICE_EXCEPTION. My theory was and still is that old drivers...

  9. Laptop not switching to "High Performance" mode while plugged in

    in Windows 10 Performance & Maintenance
    Laptop not switching to "High Performance" mode while plugged in: Before when I used to plug in my laptop, the laptop used to go into "performance mode". This was visible because the screen colors looked more vivid and gave better fps while playing games. But now, after plugging in, the laptop stays in the same state, no color change or...

  10. Laptop's not switching to "high performance mode" when plugged in

    in Windows 10 Ask Insider
    Laptop's not switching to "high performance mode" when plugged in: Before when I used to plug in my laptop, the laptop used to go into "performance mode". This was visible because the screen colors looked more vivid and gave better fps while playing games. But now, after plugging in, the laptop stays in the same state, no color change or...

Users found this page by searching for:

  1. nt!ExEnterCriticalRegionAndAcquireResourceExclusive 0x3f