Windows 10: 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]

:)

 

Help with overclocking Phenom II X6

Seems perfectly stable even at the voltage it's at though. lol

 

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.

 

Overclocking the X58, a practical guide

Just added a new version of the guide for Sandy Bridge *Toast :toast:

3 Step Overclocking Guide- Sandy Bridge