Windows 10: BSOD HOW CAN I FIX THIS

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: 00000001c0009338, memory referenced​

Arg2: 0000000000000002, IRQL​

Arg3: 0000000000000000, 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: fffff80343c4afc8, 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-RR9SNN0​

​

Key : Analysis.DebugData​

Value: CreateObject​

​

Key : Analysis.DebugModel​

Value: CreateObject​

​

Key : Analysis.Elapsed.Sec​

Value: 1​

​

Key : Analysis.Memory.CommitPeak.Mb​

Value: 81​

​

Key : Analysis.System​

Value: CreateObject​

​

​

DUMP_FILE_ATTRIBUTES: 0x8​

Kernel Generated Triage Dump​

​

BUGCHECK_CODE: a​

​

BUGCHECK_P1: 1c0009338​

​

BUGCHECK_P2: 2​

​

BUGCHECK_P3: 0​

​

BUGCHECK_P4: fffff80343c4afc8​

​

READ_ADDRESS: fffff803446fa390: Unable to get MiVisibleState​

Unable to get NonPagedPoolStart​

Unable to get NonPagedPoolEnd​

Unable to get PagedPoolStart​

Unable to get PagedPoolEnd​

fffff8034460f330: Unable to get Flags value from nt!KdVersionBlock​

fffff8034460f330: Unable to get Flags value from nt!KdVersionBlock​

unable to get nt!MmSpecialPagesInUse​

00000001c0009338​

​

BLACKBOXBSD: 1 !blackboxbsd​

​

​

BLACKBOXNTFS: 1 !blackboxntfs​

​

​

BLACKBOXPNP: 1 !blackboxpnp​

​

​

BLACKBOXWINLOGON: 1​

​

CUSTOMER_CRASH_COUNT: 1​

​

PROCESS_NAME: System​

​

TRAP_FRAME: ffffc80356cb5530 -- .trap 0xffffc80356cb5530​

NOTE: The trap frame does not contain all registers.​

Some register values may be zeroed or incorrect.​

rax=00000001c0009320 rbx=0000000000000000 rcx=0000000000000003​

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000​

rip=fffff80343c4afc8 rsp=ffffc80356cb56c0 rbp=0000000000000001​

r8=0000000000000008 r9=0000000000000000 r10=000000000000ffff​

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000​

r14=0000000000000000 r15=0000000000000000​

iopl=0 nv up ei pl nz na pe nc​

nt!KiDeferredReadySingleThread+0x478:​

fffff803`43c4afc8 0f1004c8 movups xmm0,xmmword ptr [rax+rcx*8] ds:00000001`c0009338=????????????????????????????????​

Resetting default scope​

​

STACK_TEXT: ​

ffffc803`56cb53e8 fffff803`43e07769 : 00000000`0000000a 00000001`c0009338 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx​

ffffc803`56cb53f0 fffff803`43e03a69 : 00000000`00000000 00000000`00000000 00000000`00000002 00000096`db271a09 : nt!KiBugCheckDispatch+0x69​

ffffc803`56cb5530 fffff803`43c4afc8 : ffffa300`b9600180 ffffca0c`276df000 00000000`00000004 ffffc803`56cb56fc : nt!KiPageFault+0x469​

ffffc803`56cb56c0 fffff803`43c44c4d : 00000000`0025b6e1 ffffc803`56cb5b10 00000000`00000080 ffffa300`b9600180 : nt!KiDeferredReadySingleThread+0x478​

ffffc803`56cb58b0 fffff803`43c45030 : ffffa300`b9600180 00000000`00000000 ffffca0c`2628c1f0 00000000`00000000 : nt!KiReadyThread+0x4d​

ffffc803`56cb58e0 fffff803`43c06eed : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`0025b6e1 : nt!KiProcessExpiredTimerList+0x290​

ffffc803`56cb59d0 fffff803`43df92ee : ffffffff`00000000 ffffa300`b9600180 ffffa300`b960b440 ffffca0c`27e94580 : nt!KiRetireDpcList+0x5dd​

ffffc803`56cb5c60 00000000`00000000 : ffffc803`56cb6000 ffffc803`56cb0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e​

​

​

SYMBOL_NAME: nt!KiDeferredReadySingleThread+478​

​

MODULE_NAME: nt​

​

IMAGE_NAME: ntkrnlmp.exe​

​

IMAGE_VERSION: 10.0.19041.685​

​

STACK_COMMAND: .thread ; .cxr ; kb​

​

BUCKET_ID_FUNC_OFFSET: 478​

​

FAILURE_BUCKET_ID: AV_nt!KiDeferredReadySingleThread​

​

OSPLATFORM_TYPE: x64​

​

OSNAME: Windows 10​

​

FAILURE_ID_HASH: {626f59d5-90cc-ab48-85f0-60e170096c96}​

​

Followup: MachineOwner​

---------​

​

:)

 

BSOD issue after fixing another BSOD error

Hi Williams,

There are several reasons why BSOD occur, which has different resolution. To check for any corruption or the integrity of your computer's Windows, we suggest that you perform a
Check Disk by following these steps:

• Type cmd in the search bar.
• Right-click on the Command Prompt, then Run as administrator.
  
• Type chkdsk x: /r, the /r command will fix errors found on the disk.

Let us know if you need further assistance.

 

Programs not working

In post 26 there were steps listed to fix the operating system corruption.
Are you able to follow them?
In post 29 was the suggested dism repair command.

 

Bsod

Wow, I took too long to type, so I didn't see the other suggestions.
But for one thing, I just rememnber that there was a thread about 8800 BSODs and a fix.
IIRC thread by d44ve, I'll have a look.