AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Irql not less or equal wfplwfs.sys11/4/2023 I'm now really unsure what the issue is here. I'm just hoping the issues don't continue to get worse like before. I was able to boot back up immediately however. I never saw another BSOD or issue up until now. Everything went smoothly and now the only new hardware I have in my PC is the CPU. From that point, I worked backward, putting my old hardware back in and booting. I had all new hardware in my PC before trying the new CPU. However, a new CPU fixed my issue entirely, or so I thought. Motherboard didn't change anything either. I went through switching out various parts beginning with the psu. I went out and bought a new motherboard, new psu, and new cpu. The blue screens themselves sometimes wouldn't even report errors codes, just a frowny face. The amount of times I could get into windows decreased, from sometimes being able to boot, to not at all. Also, at this point, I was three days in and the BSOD errors kept getting worse. This made me believe that it was not a driver error, but a hardware error.Īt this point I figured it had to be a hardware issue. Even though I didn't thing my drives were the issue, I reinstalled Windows. In addition, I still got blue screens with all of my drives unplugged, and only a windows bootable usb plugged in. DISM also didn't report anything was wrong. Initially, there were errors found using sfc, but aside from the first time, I found no other errors. I also scanned all of my drives using sfc /scannow, as well as dism restore health. I did get a BSOD from driver verifier, but at the time I was unable to boot past windows, so I didn't get a chance to do anything with it. Nevertheless, I reinstalled drivers, flashed bios, and ran driver verifier. The only updates I recall installing were a windows update. I then began checking drivers, and uninstalling any new programs. Given that I think its highly unlikely to be sent two brand new sticks that are faulty, I moved onto checking other elements. I also kept getting the same blue screens. I got brand new ram and memtest picked up errors on the new sticks as well. So, one of the first things I did was replace the RAM. I was only able to run each for 4 passes because of the version of memtest I have, but in some cases I would get no errors, and in others I would get plenty. One thing I noticed was that the error messages were pretty inconsistent. One of the first things I did was run memtest86 on my RAM, I've run my ram indiviudally, as well as dual channel. I started troubleshooting on my own to figure out the issue. It would then promptly crash within a few minutes or, if I was lucky, hours. As a side note, sometimes it would let me boot to windows. I would be unable to boot into safe mode or recovery mode. The BSOD would result in boot loops of BSOD, with a variety of other error messages. I've been suffering from IRQL NOT LESS THAN OR EQUAL TO beginning last Friday.
0 Comments
Read More
Leave a Reply. |