Windows 10: PC CRASH MULTIPLE_IRP_COMPLETE_REQUESTS

Hello, I have been struggling this couple weeks figuring it out what's the cause of the BSOD on my computer it does randomly without any warning, I've tried various of method fixing like scanning corrupted files, updating my bios, uninstalling/reinstalling drivers, updating windows and went too far changing pc components. But at the end its still happening.I'm running out of Ideas fixing this anymore, I hope posting my BSOD ISSUE here would help me because this might be my last resort MINIDUMP: 092824-11921-01.dmp* Moved from Community Center

:)

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

BlueScreen - MULTIPLE_IRP_COMPLETE_REQUESTS.

A problem has been detected and windows has been shut down to prevent damage to your computer.

MULTIPLE_IRP_COMPLETE_REQUESTS

If this is the first time you’ve seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed.

If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computador, press F8 to select advanced
startup options, and them select safe mode;

Technical Information:

*** STOP: 0X00000044 (0x874CA368,0x00000E7A,0x00000000,0x00000000)

Collecting data for crash dump …

Initializing disk for crash dump …

Beginning dump of physical memory.

Dumping physical memory to disk: 100

Physical memory dump complete.

Contact your system admin or technical support group for further assistance.

 

MULTIPLE_IRP_COMPLETE_REQUESTS Blue Screen ntoskrnl.exe

I repeatedly have my computer crash (blue screen). I have updated all of my drivers, reset overclocking settings, and performed a memtest. Memtest identified no issues. Looking for how to resolve this issue.

I ran who crashed and received the following analysis of my Dumpfiles:

On Tue 7/2/2019 6:28:19 PM your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\070319-27190-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x93AA0)

Bugcheck code: 0x44 (0xFFFFFA8019796670, 0xEC0, 0x0, 0x0)

Error: MULTIPLE_IRP_COMPLETE_REQUESTS

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 7/2/2019 10:15:20 AM your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\070219-20529-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x93AA0)

Bugcheck code: 0x44 (0xFFFFFA801D79D1C0, 0xEC0, 0x0, 0x0)

Error: MULTIPLE_IRP_COMPLETE_REQUESTS

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.