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.

Windows 7: BSODs all the times (During Boot, during Windows, IRQL, Driver IRQL)

Yesterday night I had an idea. A weeks ago I changed my power supply unit to a smaller one because my normal one did break.
I thought that perhaps I have to less power to use my PC propperly so I borrowed me another big PSU. My Windows ran the whole night, without problems. Prime did not find any error.
BUT: this morning I wanted to use my PC as normal and now again. BSOD over BSOD.
No chance to get the verifier working.

Now I am trying to do another virus scan. This time I use a Knoppix Live OS. This should be able to find everything.

Run Driver Verifier according to these instructions for a minimum of 36 hours (computer operating time):

Quote:

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.

So, 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).

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 "Special Pool" and "Low Resource Simulation" 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.

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 (an estimate on my part).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Check to make sure that nothing is overheating. Wait for it to freeze with the Knoppix, unplug from the wall and open the case. Hold onto metal of case while feeling around inside the case. DO NOT TOUCH anything - only get near it - it can burn you!

Also, plug in the system and make sure that the fans are all working and that the coolers are free of dust bunnies. Check the caps on the mobo to ensure that none of them have burst.

Check to make sure that nothing is overheating. Wait for it to freeze with the Knoppix, unplug from the wall and open the case. Hold onto metal of case while feeling around inside the case. DO NOT TOUCH anything - only get near it - it can burn you!

Also, plug in the system and make sure that the fans are all working and that the coolers are free of dust bunnies. Check the caps on the mobo to ensure that none of them have burst.

Did you run malware scans as I suggested earlier? If so, and if they came out clean, then there's nothing else evident.
As such I'd have to suggest that you do the following:

Quote:

For testing purposes, it's best to install Windows "clean".
This is, basically, installing it the way that Microsoft intended (using drivers from Windows Update).
This procedure is for Windows 7, Vista is similar (but has 2 service packs)

You will need your installation/recovery DVD(s) before you start. Once you wipe the hard drive there's no going back!!!

1. Backup all your data.
This will wipe everything off of your hard drive, so anything that you want to keep will need to be saved elsewhere.

2. Connect the system to the internet (if the system says disconnect from the Internet, then do so).
3. Use DBAN ( DBAN Download | Darik's Boot And Nuke ) or KillDisk ( Freeware Download Active@ KillDisk ) to wipe the entire hard drive (both are free). This will also delete any recovery partitions on the system - so the intallation/recovery DVD's are essential!!!
4. Install Windows by booting from the installation/recovery DVD - DO NOT tweak any settings!!!
5. Visit Windows Update and get all updates
6. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center
7. Visit Windows Update and get any other available updates
8. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
9. Download, install, and update a free antivirus so you don't get infected while testing ( Free AntiVirus ).

If the problems persist, then the problem is most likely with your hardware.

CAVEAT: If you have an Asus motherboard, check the date on the C:\Windows\System32\driver\ASACPI.sys file. 2004/2005 is a problem, 2009,2010 is OK. Updates are available at the Asus support website.

My system allways did crash before complete scan.
I did wipe the HDD = no malware atm.
My suggestion is that my mobo is broken. I got another one and now I am trying to install a system image from earlier this month. Perhaps the whole problem is solved now. I am going to inform you of the results later this day.

BSODs all the times (During Boot, during Windows, IRQL, Driver IRQL)

Driver IRQL NOT LESS OR EQUAL and unnamed BSODsHi All! In the past 4 days I have been experiencing some BSOD. So far my computer has BSOD five times. However, only once has bluescreenview presented a name for the bsod which was the driver irql not less or equal.
Computer Parts:
Motherboard: MSI Z77A-G45 Gaming
Processor: i5-3570k @ 3.40...

Drivers

BSOD at random times: DRIVER IRQL NOT LESS OR EQUALHello everyone,
The BSOD appears at random times, at random intervals even when not doing anything. I updated my sound driver since my computer often makes a very disturbing sound before starting memory dump. This did not help however. I bought the computer in its entirety less than 2 years ago...

BSOD Help and Support

BSOD at random times: Driver IRQL Not Less Or EqualHello,
I built this desktop approximately 2 years ago, but only just recently started experiencing BSOD at seemingly random times. The system hangs for a couple seconds, then goes blue and tells me "Driver IRQL Not Less Or Equal". I re-installed OEM Windows 7 Home Premium x64 about a week ago...

Plenty of BSODs, driver irql not less or equal.In the past week I've had 11 BSODs with the message DRIVER_IRQL_NOT_LESS_OR_EQUAL. After some google-fu I updated all my drivers to the latest from their respective manufacturer but still had problems.
I formatted my OS harddrive and didn't install any drivers but still got several bluescreens...