Sign in with
Sign up | Sign in
Your question

BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL, Already Tried a Few Things

Tags:
  • Windows 8
  • Blue Screen
  • Computers
September 25, 2014 1:15:43 PM

I've been having issues with my computer since I got it in August. It's a custom made PC that I got from one of my dad's friends who is a computer expert. It has Windows 8.1 Enterprise 64-bit installed on it with an AMD FX(tm)-8320 Eight-Core Processor with 3.50 GHz, 8 GB of installed RAM and an AMD Radeon HD 6800 series. When I first got it, it was working fine until I downloaded and installed the Windows updates and iTunes. When the Windows update prompted me to restart the computer, I did and I saw a blue screen which just stood there. It said Your PC ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart for you. (0% complete) If you'd like to know more, you can search online later for this error:D RIVER_IRQL_NOT_LESS_OR_EQUAL. I called my dad's friend and he suggested doing a system restore. That helped, but after a few days, that same blue screen came back. I've been getting it often, and 1 time it said memory_management. I ran the Windows Memory Diagnostic and it created a minidump file. I used the WhoCrashed program and this is what the report says:

On Mon 8/18/2014 6:02:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081714-8015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x1A (0x8887, 0xFFFFFA80066C8070, 0xFFFFFA800070C440, 0x500)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

That's the only minidump file it could find. I also tried the SlimCleaner program. It only fixed 21 file association errors. I did a full virus scan with Windows Defender but it didn't find anything. What do you think I should do?

More about : bsod driver irql equal things

!