Pc is unusable because of crashes.

Hi , ever since i built my pc myself 3years ago i keep experiencing freezes and crashes to the point where it becomes unusable . Right now i am writing this on my phone because my pc just keeps crashing while im writing. So i have sent my cpu and motherboard to the manufacturer and they told me they were not having any problems , then i unplugged my seagate hdd , and it was still crashing. I ran memtest a few times and it always had no errors and all the passes. I have updated all of my drivers and windows software . Recently i rebuilt my pc and its still crashing. I have clean booted my pc 3 days ago and it was running well (only using league of legends and opera) and today it started crashing again. And its worse than ever it keeps crashing constantly and every time there is a different error : IRQL NOT LESS OR EQUAL notskrnl.exe , APC INDEX MISMATCH , DRIVER OVERRAN STACK BUFFER , KERNEL SECURITY CHECK FAILURE , and others .I have ran multiple pc scans , i have reseted my pc multiple times . I have contacted Microsoft community and a guy tried to help me and told me to sent him minidump files , and i did , and he told me to run memtest86 and i did , and then i told him it ran with no errors and he didnt respond ever since.This problem is unbearable and i need help as soon as possible

Sounds similar to things I've been having IRQL NOT LESS OR EQUAL is a blue screen stop code isn't it? If it's been blue screening there's a separate thread for that.


Have you tried using a different keyboard after resetting?

Did you update to latest BIOS (F65c) & latest Chipset Drivers?

neves said:

Did you update to latest BIOS (F65c) & latest Chipset Drivers?

Click to expand...

I just updated it right now and while i was writing this , it crashed with the error Unexpected kernel mode trap

These are all the same stop codes I've been getting My BSOD thread is on Windows 10 though. Hardware testing found only one issue - faulty keyboard. sfc/scannow found corruption and fixed it but the problem continues. I haven't tried changing the keyboard as yet (laptop) - hence suggesting trying another keyboard (or running hardware diagnostics).

It's either drivers or hardware, is the conclusion I came to from the error warnings.

13A is "Kernel mode heap corruption"
F7 is "Driver overran stack buffer"
7F is "Kernel mode trap" "typically occurs if you install faulty or mismatched hardware, (especially memory) or if installed hardware fails
4E pfn list corrupt - could be anything including drivers, faulty ram or overheating or malware.

If you post on the BSOD thread and run the log they ask for, someone will help you out. Attachment is from my Ten Forums BSOD thread.

Arggg! Kingston ram? You gotta be kidding me!
That's the one brand that goes right into the trash in my shop.
They have the bad reputation for buying second grade chips from major manufacturer and putting them on their own boards. *
If I were trying to repair your PC in my own shop, the first thing I'd do is REMOVE anything with "Kingston" on it.

* For several years, I working with a RAM seller at the Market Pro Computer Shows. I got quite a education in Good RAM, vs. Bad RAM.

I've also fixed many PC's by just changing out the CMOS battery. Some motherboards are very sensitive to low battery voltage. If a CMOS battery is not at 3.0 vdc, or better, out if goes! For many years, every PC that came into my shop for repair, got a new CMOS battery.

I've read many accounts of PC's "Crashing", either a BSOD or just an abrupt shutdown. I've Never experienced that on any of my own PC's. (12) Because, I buy only parts brands that I know and trust. And I believe in and practice Computer Maintenance.

Good Luck,
TM (retired computer tech)

Try changing ram, then keyboard?

5500xt graphics cards are often used for mining cryptocurrency, respectively, are subjected to "overclocking" and modification of firmware in ROM.

.

Hazel123 said:

These are all the same stop codes I've been getting My BSOD thread is on Windows 10 though. Hardware testing found only one issue - faulty keyboard. sfc/scannow found corruption and fixed it but the problem continues. I haven't tried changing the keyboard as yet (laptop) - hence suggesting trying another keyboard (or running hardware diagnostics).

It's either drivers or hardware, is the conclusion I came to from the error warnings.

13A is "Kernel mode heap corruption"
F7 is "Driver overran stack buffer"
7F is "Kernel mode trap" "typically occurs if you install faulty or mismatched hardware, (especially memory) or if installed hardware fails
4E pfn list corrupt - could be anything including drivers, faulty ram or overheating or malware.

If you post on the BSOD thread and run the log they ask for, someone will help you out. Attachment is from my Ten Forums BSOD thread.

View attachment 84982

Click to expand...

What exactly are these codes? And also what does my keyboard have anything to do with this ?

abactuon said:

5500xt graphics cards are often used for mining cryptocurrency, respectively, are subjected to "overclocking" and modification of firmware in ROM.

Click to expand...

What am i supposed to do then ? i didnt mine on it , i received it brand new .

All of your bugchecks seem to be consistently crashing in the same area which suggests to me that this is a driver issue. For now, please run Driver Verifier using the following instructions: BSOD - Driver Verifier Instructions [Official]

Please read the entire tutorial carefully especially the last part about disabling Driver Verifier outside of Windows. If it crashes, then please upload all the new dump files.

petros2 said:

What exactly are these codes? And also what does my keyboard have anything to do with this ?

Click to expand...

Just saying to maybe do a hardware testing - mine found the keyboard was the issue. It may be other hardware with yours. Or drivers, or incompatible hardware.

Those codes are what come up when you run the log asked for on the BSOD thread - and if you google them they are blue screen codes. You mentioned Driver overran stacker as one.

I had most of the similar blue screen stop codes (eg driver overran stacker) and so far have only found faulty keyboard. Thought it might be worth looking at.

x BlueRobot said:

All of your bugchecks seem to be consistently crashing in the same area which suggests to me that this is a driver issue. For now, please run Driver Verifier using the following instructions: BSOD - Driver Verifier Instructions [Official]

Please read the entire tutorial carefully especially the last part about disabling Driver Verifier outside of Windows. If it crashes, then please upload all the new dump files.

Click to expand...

I am now using driver verifier ( ive checked cmd) what am i supposed to do once it crashes?

petros2 said:

what am i supposed to do once it crashes?

Click to expand...

You'll need to disable Driver and then upload the resulting dump files.

x BlueRobot said:

You'll need to disable Driver and then upload the resulting dump files.

Click to expand...

Very budget PSU and has been used for three years.

Please see rule #4:

If you remove the piracy (Volume KMS) > legally activate Windows > then help can be provided.


The computer is extremely unlikely to have a driver problem.

Running WDV is unlikely to be of any use.

Again if you activate Windows legally (without piracy) > then help can be provided.

petros2 said:

What am i supposed to do then ? i didnt mine on it , i received it brand new .

Click to expand...

There are a number of things you could try if you can't keep the OS up and running long enough to do those other things.

1) Try booting your PC with one stick of RAM at a time. Make certain you have the memory in the right slot for only one stick of RAM.

2) If you have a spare SSD disconnect the other hard drives with system turned off and connect spare. Install the desired OS on the spare and see if your system stabilizes. Keep all your hardware at a bare minimum when you do this and then gradually start adding it back each time you turn off your PC. Make a note of what you did last the minute you encounter an issue, if and when you encounter one.

3) Try a system reset. Remove CMOS battery with PC turned off and unplugged. Wait at least ten minutes. Replace battery, plug in the PC and turn it on. (See: #2)

4) Try running your computer without the graphics card if you have onboard graphics or, try a different graphics card if you have one. Sometimes you can inadvertently acquire the wrong driver for your graphics card. Best to rule this out if at all possible.

5) Try disconnecting all other drives except the one with the OS and rebooting the system.

You have enough errors to warrant trying out a fresh operating system. Using this approach might be of some help in locating any problematic hardware. If your system won't stay up long enough to run any analytics then it might well be worth a try. Make certain that your BIOS is in order (secure boot, AHCI, boot order etc.) and that you have the latest BIOS.

Even if there is nothing wrong with your memory sometimes re-seating the RAM will help. Might as well do a check on each stick of RAM before re-seating it all. These are only a few of the things I do when my system won't stay up long enough to run any data checks.

I'm running HyperX Fury on three PCs here without issue. I'm thinking your RAM is fine, but stuff happens. I hope this helps.