Windows 10: BSOD after overclock, was stable for 3 days until it decided it's not, someone help with...

Discus and support BSOD after overclock, was stable for 3 days until it decided it's not, someone help with... in Windows 10 Ask Insider to solve the problem; Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File... Discussion in 'Windows 10 Ask Insider' started by /u/DeadyDeadshot, Nov 22, 2020.

  1. BSOD after overclock, was stable for 3 days until it decided it's not, someone help with...


    Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.





    ************* Path validation summary **************

    Response Time (ms) Location

    Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

    Executable search path is:

    Windows 10 Kernel Version 19041 MP (16 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff804`3d400000 PsLoadedModuleList = 0xfffff804`3e02a3b0

    Debug session time: Mon Nov 23 07:40:25.842 2020 (UTC + 4:00)

    System Uptime: 1 days 9:25:03.469

    Loading Kernel Symbols

    ...............................................................

    .....Page 1052e0 not present in the dump file. Type ".hh dbgerr004" for details

    ...........................................................

    ................................................................

    ......

    Loading User Symbols



    Loading unloaded module list

    ....................................

    For analysis of this file, run !analyze -v

    1: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    IRQL_NOT_LESS_OR_EQUAL (a)

    An attempt was made to access a pageable (or completely invalid) address at an

    interrupt request level (IRQL) that is too high. This is usually

    caused by drivers using improper addresses.

    If a kernel debugger is available get the stack backtrace.

    Arguments:

    Arg1: 0000000000000000, memory referenced

    Arg2: 00000000000000ff, IRQL

    Arg3: 0000000000000075, bitfield :

    bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

    Arg4: fffff8043d72743f, address which referenced memory



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 1



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-UH44RK6



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 1



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 71



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: a



    BUGCHECK_P1: 0



    BUGCHECK_P2: ff



    BUGCHECK_P3: 75



    BUGCHECK_P4: fffff8043d72743f



    WRITE_ADDRESS: 0000000000000000



    PROCESS_NAME: System



    TRAP_FRAME: fffffc07a6c2f460 -- (.trap 0xfffffc07a6c2f460)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000001

    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8043d72743f rsp=fffffc07a6c2f5f0 rbp=0000000000000000

    r8=0000000000000008 r9=0000000000000000 r10=0000000000000000

    r11=47ae147ae147ae15 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up di pl nz na pe nc

    nt!PpmIdleExecuteTransition+0x2bf:

    fffff804`3d72743f 66898c24c8000000 mov word ptr [rsp+0C8h],cx ss:0018:fffffc07`a6c2f6b8=0000

    Resetting default scope



    STACK_TEXT:

    fffffc07`a6c2f318 fffff804`3d807169 : 00000000`0000000a 00000000`00000000 00000000`000000ff 00000000`00000075 : nt!KeBugCheckEx

    fffffc07`a6c2f320 fffff804`3d803469 : 00000118`1aec2324 fffff804`412399f3 ffffdd83`686ab1a0 ffffdd83`789a2970 : nt!KiBugCheckDispatch+0x69

    fffffc07`a6c2f460 fffff804`3d72743f : ffffdd83`6e0d7318 00000000`00000000 00000118`1afc99ea 00000118`1afc99ea : nt!KiPageFault+0x469

    fffffc07`a6c2f5f0 fffff804`3d727004 : 00000000`00000000 00001f80`00000009 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x2bf

    fffffc07`a6c2f9f0 fffff804`3d7f8d34 : ffffffff`00000000 ffffc700`66393440 ffffdd83`75524080 00000000`00000634 : nt!PoIdle+0x374

    fffffc07`a6c2fb60 00000000`00000000 : fffffc07`a6c30000 fffffc07`a6c29000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54





    SYMBOL_NAME: nt!PpmIdleExecuteTransition+2bf



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 2bf



    FAILURE_BUCKET_ID: AV_nt!PpmIdleExecuteTransition



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {0ced0187-972d-f83e-de87-663d75806c32}



    Followup: MachineOwner

    ---------

    submitted by /u/DeadyDeadshot
    [link] [comments]

    :)
     
    /u/DeadyDeadshot, Nov 22, 2020
    #1
  2. Kyle Win User

    Help with overclocking Phenom II X6

    Seems perfectly stable even at the voltage it's at though. lol
     
  3. SumDedGuy Win User
    BSOD Playing Games on Stable Overclock: IRQL_NOT_LESS_OR_EQUAL

    I was just referring to the stress test giving me the feeling that things were stable and I was safe from further issues regarding overclocking. It really just turns out to be a lack of experience and taking the wrong steps due to an unrecognized issue. Had the BSOD been a WATCHDOG_CLOCK_TIMEOUT, I probably would have known what to do from the get go. Though I can say that it's pretty hard to find out what to do when the IRQL error generally indicates very different issue than a lack of voltage to stabilize.

    On the matter of progress, I have now ran some further tests and have managed to get things stable at 1.315V. I'll let a few days pass and see if the issue still arises, though I am sure I've gotten the hang of things now.
     
    SumDedGuy, Nov 22, 2020
    #3
  4. miahallen Win User

    BSOD after overclock, was stable for 3 days until it decided it's not, someone help with...

    miahallen, Nov 22, 2020
    #4
Thema:

BSOD after overclock, was stable for 3 days until it decided it's not, someone help with...

Loading...
  1. BSOD after overclock, was stable for 3 days until it decided it's not, someone help with... - Similar Threads - BSOD overclock was

  2. 3 different BSODs in 9 days

    in Windows 10 BSOD Crashes and Debugging
    3 different BSODs in 9 days: Hi, Starting in 21/12 and ending in 30/12 I had 3 different blue screens of death. Blue Screen view said this about them: 1.ntoskrnl.exe ntoskrnl.exe+595ec2 fffff805`4d600000fffff805`4e646000 0x01046000 0xc129b808 9/10/2072 2:39:36 PM 0x0000012b 2.ntoskrnl.exe...
  3. Sudden BSODs Win10 in past 3 days Need help troubleshooting

    in Windows 10 BSOD Crashes and Debugging
    Sudden BSODs Win10 in past 3 days Need help troubleshooting: Hi Microsoft Team, On the past 3 days, I have 3 BSODs. Attached is the minidump & MSINFO of my computer: https://1drv.ms/u/s!AqAhNMuZyKrSiCyw3z3Bn0Gex3Mz?e=kVkDP1 Regards, Michael...
  4. 3 BSODS in 4 days please help

    in Windows 10 BSOD Crashes and Debugging
    3 BSODS in 4 days please help: IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe - May 4th PAGE_FAULT_IN_NONPAGED_AREA ntoskrnl.exe May 1st DRIVER_IRQL_NOT_LESS_OR_EQUAL ndis.sys May 1st This is not the first time i come here for help on my recent BSODs. Last time it was a video driver problem. I uninstalled my...
  5. BSOD after overclocking and then returning to stock settings

    in Windows 10 BSOD Crashes and Debugging
    BSOD after overclocking and then returning to stock settings: Windows version 1909. I overclocked by 2600k a while back, then it started blue screening so I revert all the changes but bluescreens are very common now, though only when I'm not present at the machine it seems. Best Craig DESKTOP-LAERGN0-(2020-03-11_11-09-42).zip...
  6. Same Exact Score after Overclocking RTX 2060 (HELP Overclocking RTX 2060)

    in Windows 10 Graphic Cards
    Same Exact Score after Overclocking RTX 2060 (HELP Overclocking RTX 2060): I am getting the same identical score on Heaven Benchmark running Stock and Overclock no idea why. This is my Overclock Core at +170 memory at +800. I was hoping the score and FPS would go up at least by 5% or even 10% but they are identical on both instances stock and...
  7. Fast ring until stable build

    in Windows 10 Installation and Upgrade
    Fast ring until stable build: Is it possible to stay in the fast ring until the next stable build then go back to stable when the new build is released becase the slow ring has barely any builds...
  8. 3 BSOD's in the last 3 days

    in Windows 10 BSOD Crashes and Debugging
    3 BSOD's in the last 3 days: Hello, I've been getting BSOD's every day since 3 days ago. The first one had the "MEMORY_MANAGEMENT" error, as well as the third one. The second one was the "IRQL_unexpected_variable" error. According to BlueScreenView, the 1st and 3rd BSOD's were caused by Ntoskrnl.exe, and...
  9. BSOD Playing Games on Stable Overclock: IRQL_NOT_LESS_OR_EQUAL

    in Windows 10 BSOD Crashes and Debugging
    BSOD Playing Games on Stable Overclock: IRQL_NOT_LESS_OR_EQUAL: Hi, I am having some issues with a BSOD when playing games on an overclocked 6600k. The processor itself is be completely stable with a 4.5GHz overlock at 1.296V when stress tested for ~7 hours and through normal use. The BSOD occurs within 30 minutes to 2 hours of gameplay....
  10. 3 BSOD after installing a new mouse. 1 BSOD the day before.

    in Windows 10 BSOD Crashes and Debugging
    3 BSOD after installing a new mouse. 1 BSOD the day before.: After installing a mouse ( GX800 | Keyboards & Mice | ASUS Global ). I got 3 BSOD and 1 bsod before i installed the new mouse. Attachment 65800 41753