Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Hi. I've been having this problem for about one year now and I decided it's time I sought online help. My PC is about 2 and a half years old and the current windows installation is roughly 2 years old (windows 7 professional x64 from microsoft academic alliance...).
Crashes/freezes happen at random times (I had gone about a month with none) and not when a particular program is running. I've attached minidump files and system health report.

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.
* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.

Memtest.

Quote:

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Run memtest and my sticks passed the test twice with no errors. I will run the test on each stick individually though sometime in the weekend. I have started the driver verifier thing and so far i have one bsod from 000.fcl. I attached minidumps for this and a couple of other bsods i had while playing League of Legends.
(I tried to upload the memory.dmp file too but it was too big...)

BSOD - driver irql not less or equalRecently my computer has been restarting with a BSOD saying DRIVER_IRQL_NOT_LESS_OR_EQUAL.
I have completed my system spec details on my profile and I've attached the DM Log as outlined in the BSOD post guide.
I hope someone can help. Thanks

BSOD Help and Support

BSOD DRIVER IRQL NOT LESS OR EQUAL, unexpected restart and freezehi guys! this is my first post on this forum. yesterday while i was playing mount and blade pc freezed a bit this didnt happen before. today i played cs go and pc restarted itself without any warning. then i started to search it on the internet and it freezed while i was using only google chrome....

BSOD Help and Support

Freezes, BSOD IRQL Not less or Equal 0x0aHi,
Approx. a month and a half ago my computer started randomly stalling when idle, at first 1-2 times a week and then daily. After some time, it started only stalling 1-15 minutes after boot, and then would run perfectly fine for hours if it got past that first period, even if idled.
In the...

BSOD Help and Support

BSOD Driver IRQL Not Less or EqualHello! I am having BSOD issues. It happens most often when I'm playing games (specifically during Rift), but it is still happening occasionally when the computer idles. For example, I'll leave for work in the morning and come home to find the computer reset itself.
Here are some specs:
...