[SOLVED] Inconsistent BSOD - Windows 8.1 x64

SpaceMonkey · May 21, 2015

Hi, I've been crashing with my computer for a month or so and I'm starting to run out of ideas.
Some of them are DRIVER_IRQ_NOT_LESS_OR_EQUAL (usbohci.sys), but searching from Google gives no answers.
But recently I've gotten a wide variety of crashes, BAD_POOL_HEADER, MEMORY_MANAGEMENT, KMODE_EXCEPTION_NOT_HANDED, REFERENCE_BY_POINTER and NTFS_FILE_SYSTEM. These crashes are so inconsistent that It's nearly impossible for me to find a reliable source to these problems. I'm starting to lean towards a hardware failure, but I'm still not sure whenever this is true or not.
I have ran MemTest86+ 8 passes and it found nothing, I've ran Driver Verifier to the point It didn't crash me on startup, removed all faulty programs it found, but still Blue Screen are happening.

I'll now include my recent MiniDumps and the files you otherwise want me to supply.

· OS - Windows 8.1 Pro
· 64-bit
· Windows 8 Pro
· I bought from retailer.
· CPU = 1 year, Video Card = 2-3 years, Motherboard = 1 year, Power Supply = 1 year
· Recently re-installed Windows 8by installing a new hard disk.
· 4-5 times

· ADM FX(tm)-6300-Six-core-processor
· GeForce 550 Ti
· Gigabyte 990XA-UD3
· Power Supply CoolerMaster 600w

· System Manufacturer - Self-built
· Exact model number - Self-built

Note: PERFMON test states: "the operator or administrator has refused the request" and doesn't do anything. But I have heard that it actually generates this file, even tough this error occurs, but I can't remember where it generates it. Provide me with this information, if you specially need the PERFMON file.

Patrick · May 21, 2015

This looks like easy hardware failure to me after just 2 dumps.

Start with memtest for 8 passes:

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works (you don't need to read, it's only for those interested in the specifics):

Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.

The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.

The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.

Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

SpaceMonkey · May 21, 2015

I have already done 8 passes of MemTest86+, but it never hurts to do it again I guess?
Last time I had no errors (3 weeks back) so I doubt it will be any different, but I'll still do it.

Patrick · May 21, 2015

If you get no errors again, do two things.

1. Enable kernel dump generation if not already:

https://msdn.microsoft.com/en-us/library/windows/hardware/ff542953(v=vs.85).aspx

2. After #1, enable Driver Verifier:

Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (only on Windows 7 & 8/8.1)
- DDI compliance checking (only on Windows 8/8.1)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues.

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

- Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

Any other questions can most likely be answered by this article:

Using Driver Verifier to identify issues with Windows drivers for advanced users

When you crash, upload the MEMORY.DMP to a cloud storage of your choice and paste the link in your reply.

SpaceMonkey · May 21, 2015

Odd! This time it detected 2 errors. These did not appear last time I used this. Interesting, I'll upload a picture of it, because I'm not sure where is the "error report", if there is one.
I'll also put on the Verifier and Kernel Dumps, just in case.

Patrick · May 21, 2015

Eh, no real use in running anything software-related now. You have bad RAM.

SpaceMonkey · May 21, 2015

So should I get new pair of RAM, or can I remove the faulty ones or are they all broken?

Patrick · May 21, 2015

Well, to find that out, you should test one stick at a time.

SpaceMonkey · May 21, 2015

OK, i'll get to it and test 1 stick at a time.

SpaceMonkey · May 21, 2015

8 passes without errors using 2 memory sticks.
I'll see now, if I get any crashes and report back if I do.

SpaceMonkey · May 21, 2015

Well, I just experienced a couple of crashes.
First time when I started to play LoL, my screen just went black, said it can't find a source, and then my computer just shut down without blue screen.
Second one was after this event, after I had restarted LoL and the crash said: "PAGE_FAULT_IN_NONPAGED_AREA". I have never seen this crash before.
EDIT: As I went back into the game again, my desktop just broke. My mouse disappeared, game disappeared and all my shortcuts disappeared. And when I tried to use CTRL+ALT+DELETE, there was nothing there. I had to restart my computer for this effect to go away. Weird...

Patrick · May 21, 2015

To be honest I'd just replace the entire kit of RAM with a new kit.

SpaceMonkey · May 26, 2015

So I have gotten myself a working set of 4x2GB memory sticks. I have experienced 0 Blue Screens, so it indeed seems the problem was in the RAM!
But on sidenote, my GPU seems to shut and relaunch in occasions, but it never crashes my computer, sometimes games shut down and I have to relaunch them. The Message is always on the bottom right corner: Display driver stopped responding and has recovered.

But my crashes are now gone so thanks a lot!

Patrick · May 26, 2015

Probably a video driver issue, just update to the latest or experiment with versions.

SpaceMonkey · May 27, 2015

So I was playing Civ: BE, when suddenly I got a blue screen out of nowhere!
It said: "DRIVER_IRQ_NOT_LESS_OR_EQUAL (amdppm.sys)"
Looks like a AMD Driver to me, not sure what to do.
I'll include the Minidump.

SpaceMonkey · May 27, 2015

Also, my computer has shut itself down a couple of times. Screen goes black, and it shuts downs and restarts. No Blue Screen. It just restarts. Probably related to display adapter shutting down.

Patrick · May 27, 2015

Nah, you'd be getting 0x116/7/8/9. Given it's 0xD1 with the processor driver again, and just shut downs, tells me it's actually probably your processor.

Jared · May 27, 2015

From what I've seen, 0xD1s can even start to show errors with the processor handling of queues. The title of DRIVER_IRQL_NOT_LESS_OR_EQUAL can be misleading, which can keep you believing it must be driver related.

SpaceMonkey · May 28, 2015

Can I test my processor in anyway?

Jared · May 28, 2015

The type of bugchecks, and subsequently, the dump files.
Have you looked at your temperatures?
Hwmonitor is good.

[SOLVED] Inconsistent BSOD - Windows 8.1 x64

Active member

Attachments

Sysnative Staff

Active member

Sysnative Staff

Active member

Attachments

Sysnative Staff

Active member

Sysnative Staff

Active member

Active member

Active member

Sysnative Staff

Active member

Sysnative Staff

Active member

Attachments

Active member

Sysnative Staff

Sysnative Staff, BSOD Kernel Dump Expert

Active member

Sysnative Staff, BSOD Kernel Dump Expert