Blue Screen Crashes

[jonathanb987]

Manufacturer: HP
Operating System: Windows 7, Service Pack 1
Processor: AMD Athlon II x2 245 processor 2.90 GHz
Memory (RAM): 8.00 GB
Hard Drive: 454 GB
System Type: 64-bit operating system
Display Adapters: ATI Radeon HD 5450
Sound: ATI high definition audio device

When starting my computer, it can idle at the desktop with no issues, but when I start to use it, it crashes to a blue screen.

http://i.imgur.com/eSgKjhw.jpg

This is a screenshot of one of the blue screens. They aren't always the same, but they are generally the same message. Sometimes, the computer blinks to this screen and stays at it without turning off. Other times, it shows the blue screen very quickly then attempts a restart.

I have tried restore points, and even resetting the computer back to factory state (this needed done anyway). Windows is up-to-date.

I have recently installed 3 2Gb ram chips. I took them out, started the computer, then shut it down, then put them in and the computer was fine for the rest of the day. Today, it is happening again.

I have been using his newly installed ram for over a month without problems. The computer has been turned off for several days while I was on a three day vacation. The problems showed up when I got back.

If there is any more information you would like to know, please ask.

 

[Chicano]

"STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL" indicates driver issues... that can happen on newly installed Windows or resetting the computer back to factory state. I've found that Windows Vista 7 and 8 are sensitive to outdated drivers.

And changing BSOD errors codes may indicate different drivers are involved. Different google results on 0x000000D1 also point to different device drivers. EG: one mentions a Pentium M CPU driver, another mentions USB drivers, another switching a laptop from AC to battery... so the causes can be different driver errors, and power issues can cause different device errors that the system can interpret as driver errors. So, possible solutions that come to mind are:
1. Updating all outdated drivers with a driver tool,
2. and if that doesn't solve it, see if testing the computer with a different PSU does.

BTW: if the computer worked flawlessly for a month with the new RAM you can safely exclude it as one of the possible causes... the only possible RAM related cause may be if you didn't seat it properly after the last time you removed it...

https://www.slimwareutilities.com/slimdrivers.php

 

[jonathanb987]

"STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL" indicates driver issues... that can happen on newly installed Windows or resetting the computer back to factory state. I've found that Windows Vista 7 and 8 are sensitive to outdated drivers.

And changing BSOD errors codes may indicate different drivers are involved. Different google results on 0x000000D1 also point to different device drivers. EG: one mentions a Pentium M CPU driver, another mentions USB drivers, another switching a laptop from AC to battery... so the causes can be different driver errors, and power issues can cause different device errors that the system can interpret as driver errors. So, possible solutions that come to mind are:
1. Updating all outdated drivers with a driver tool,
2. and if that doesn't solve it, see if testing the computer with a different PSU does.

BTW: if the computer worked flawlessly for a month with the new RAM you can safely exclude it as one of the possible causes... the only possible RAM related cause may be if you didn't seat it properly after the last time you removed it...

https://www.slimwareutilities.com/slimdrivers.php

This sounds like it should help, thanks. Luckily I have several spare PSUs that I can test if updating drivers does not work.

 

[johnbl]

you really need to know the driver name from the memory dump file.
all that DRIVER_IRQL_NOT_LESS_OR_EQUAL means is that the driver broke the rules, it told the system that the code it wanted was already in memory. Then it tried to access code that was not in memory but gave itself higher priority than the winodws memory manager so windows could not fetch the code from disk. This deadlocks the driver and the system shuts down with this bugcheck. Any driver can do this, Hence, you should run bluescreenviewer.exe or whocrashed.exe and see if it will tell you the name of the device driver that had the failure. (then you would update that driver)

you can also put the memory dump on a server and post a link if you want to.

"STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL" indicates driver issues... that can happen on newly installed Windows or resetting the computer back to factory state. I've found that Windows Vista 7 and 8 are sensitive to outdated drivers.

And changing BSOD errors codes may indicate different drivers are involved. Different google results on 0x000000D1 also point to different device drivers. EG: one mentions a Pentium M CPU driver, another mentions USB drivers, another switching a laptop from AC to battery... so the causes can be different driver errors, and power issues can cause different device errors that the system can interpret as driver errors. So, possible solutions that come to mind are:
1. Updating all outdated drivers with a driver tool,
2. and if that doesn't solve it, see if testing the computer with a different PSU does.

BTW: if the computer worked flawlessly for a month with the new RAM you can safely exclude it as one of the possible causes... the only possible RAM related cause may be if you didn't seat it properly after the last time you removed it...

https://www.slimwareutilities.com/slimdrivers.php

This sounds like it should help, thanks. Luckily I have several spare PSUs that I can test if updating drivers does not work.