Windows 10: New upgrade to Windows 10 from Windows 7 - frequent BSOD

Attachment 40057

I have attached my crash dump analysis.

I receive frequent BSOD with IRQL_NOT_LESS_OR_EQUAL as the message.

Thanks in advance for help.

:)

 

BSOD after Windows 10 upgrade

I upgraded from Windows 7 Ultimate to Windows 10 Pro. Now I'm getting the error Memory_Mangement with new version BSOD several times a day. I had a BSOD viewer on my list of programs but it disappeared with the upgrade. what the f**k is going on?

 

BSODs since Windows 10 upgrade

My several-year old HP desktop started having BSODs some time after it was upgraded from Windows 7 to Windows 10. These have become a little more frequent in the last 8 weeks. I have posted a number of mini dump files to:

Dump files

No new hardware has been installed.

I ran MemTest86 (all four passes) and Windows Memory diagnostics, no errors were found by either.

Thanks for any analysis and suggestions.

 

Hi maclean,

Welcome to the 10forums.

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.

Or configure Ccleaner to not remove dump files:









Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Hello, assuming it's a driver related issue, try Whocrashed by Resplendence (freeware) recently updated for Win 10.
"This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. "

 

Problem: if a windows driver is the last active driver then it will be blamed and Whocrashed will say that the windows driver is causing it. This happens really a lot.

 

Hi, then beyond the Event viewer or Event log explorer try the more basic (as in more basic than Who crashed)

BlueScreenView v1.55


BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version).
For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.

 

It is the same for all of those program @dalchina.
The main reason why those programs are not recommended to use.

For example:
ntoskrnl.exe is blamed in a 0x9f(driver_power_state_failure), 0x124(whea_uncorrectable_error) and 0x139(kernel_security_check_failure) crash.
A 0x124 crash can be caused by hardware, hardware drivers, overclocking, BIOS problems, dust in the pc and likely more.
For a 0x9f you need to search a little bit in the dump file to find the cause.
I have only seen a 0x139 with a parameter 3, this simply means that it might be hard to determine the cause, no doubt a program like bluescreenviewer and whocrashed cannot find the cause.

ntoskrnl.exe is a file used in the boot process, never the cause because without it or if it is corrupted you cannot boot.

The programs you're mentioning and any other I have seen won't be able to give you the needed information to find the cause.

 

Then I've been fortunate in the few cases I've had to identify a BSOD that these elementary tools have helped me.

One has to start somewhere.. and given a cryptic msg like IRQL_NOT_LESS_OR_EQUAL which one gets used to, albeit reluctantly, assuming it's on the screen long enough to be read, being left with a dmp file that is only capable of expert interpretation when the cause may simply be driver incompatibility is something of a failure by MS.

I respect your evident experience, and it seems you've found nothing better to help users deal with such events. Which leaves forums and experts such as yourself... *Smile

 

I have never allowed CCleaner to remove the dump files.

I will try the stress test on the drivers.

 

Does the dump file I posted indicate anything useful?

 

With driver verifier, not enough.
A windows driver is blamed, but a windows driver is very rare the cause.