Windows 10: IRQL_NOT_LESS_OR_EQUAL windbg Pool_Corruption
IRQL_NOT_LESS_OR_EQUAL windbg Pool_Corruption
Ok so these are the steps I have taken so far, since last week I have been getting BSOD's out the rear end, basically for the last week I have been getting BSOD's originally it was clock_watchdog_timeout which I assumed was to do with overheating, turns out after watching my temps and logging them during a crash it wasn't.
So my obvious reaction then was to check my memory for 48 hours, again, no problem with that, all my hard drives are in good working order and everything else, so I ran driver verifier, which brings me to now.
I left a benchmark running as I slept and I would say about 30-40 mins after I fell asleep I got IRQL_NOT_LESS_OR_EQUAL BSOD, after looking at windbg no driver is being pointed to it's just saying Pool_Corruption ( nt!ExDeferredFreePool+3af )
What am I missing here? I can't figure out why I am getting these BSOD's and it's literally driving me up the wall now, at first I thought it was my second HDD as it failed last week but I have since replaced it and it's in good working order and showing perfect compared to my old one so it's not that.
I don't know, anyway I have left the information you requested attached to this post so hopefully someone else can finally figure this out and save my sanity lol.
Apologies for the delay.
Are you still in need of help?
No worries Axe, no need to apologise, yes I am still in need of help if that's ok?
Please check ASUS for BIOS updates if you haven't yet.
If a BIOS update doesn't help then you are certainly dealing with a hardware problem provided that no driver was flagged with pretty much all settings enabled.
Unfortunately I can't get my fingers on what exactly happened, because some functions are undocumented.
I think I have figured out the issue, one of the pipes on my h100i cooler has faulted and whilst the temperatures on the chip are stable, the ambient case temp and pump temp was getting rather high so that was contributing to one of the BSOD's I believe.
The other contribution was that I needed to reset the CMOS after removing a hard drive, I think my PC was still trying to read for the hard drive and after so many chances it would BSOD, also I removed quite a few known drivers that cause BSOD's and just had a general clean out because after upgrading to Anniversary was when these Bluescreen's started occurring and I know windows update has a tendency now to just update things that you don't want but they are always really hidden away and hard to figure out what has been updated, sometimes it's something as silly as chipset drivers.
I have had the PC running now for over 69 hours with driver verifier and stressed it in multiple benches and not had one BSOD so far so I think it may have been fixed at this point.
Glad to hear
How to Install and Configure WinDBG for BSOD Analysis
WinDBG (Windows DeBuGger) is a Microsoft software tool that is needed to load and analyse the .dmp files that are created when a system BSOD's. The latest version of WinDBG allows debugging of...
Getting Blue screen pretty much right after a Windows 10 clean install. If I power down and wait a bit, then power up, I will get a blue screen. Then I wait for it to create a dump and it will load Windows 10 normally. It's pretty...
I'm quite active on the BSOD subforum of Sevenforums and recently I've been having a small issue with WinDbg and I tried to fix it but it didn't work. It has something to do with symbols and its path has somehow gotten a bit messy.
I seem to be suffering from a severe lack of knowledge and experience in this area. I am trying to read dump file created by Windows 10 but keep seeing errors about ntoskrnl.exe and symbol errors.
I have gone through the tutorial by Golden. I...