BDSOD - Driver IRQL not less or equal

thelunz1

New member
Local time
9:13 AM
Messages
1
Hi guys,

I just bougth a new computer, fired it up and started installing new programs. While I was browsing, the BSOD popped up.

It said 'DRIVER IRQL NOT LESS OR EQUAL' and NETIO.SYS

I don't know much about computers, so I hope you guys can help me resolving this problem!
I'll upload the files that windows made to report the problem.

Kind regards,
Ward
 

My Computer

OS
Windows 7 Home Premium x64
Hello Ward and welcome to Sevenforums.

I'm not sure what you could have done wrong here, but I only received the dump file itself. When you open up our utility, press every button expect the dump, and have a look at your desktop. There you should see the folder, containing the rest of the files we'll need!

I will diagnose and analyse the dump either way. :)

BSOD Analyse

First off, as it's new - do you have it under warranty?
As you have a few 3rd party drivers, I'd suggest you to run Driver Verifier within these circumstances.

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) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD

Then, here's the procedure to run Driver Verifier:
- 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 "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- 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 locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

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:
Code:
Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Best Regards,
Frederik.
 

My Computer

Computer Manufacturer/Model Number
Brewed
OS
Microsoft Windows 7 Ultimate: x64 (SP1)
CPU
Intel® Core™ i5-2500K Processor
Motherboard
ASUS P8Z68-V PRO
Memory
Kingston DDR3 HyperX 1600MHz 8GB
Graphics Card(s)
ASUS GTX 560 TI DirectCU II 900MHz
Sound Card
Realtek® ALC892 8-Channel High Definition Audio CODEC
Monitor(s) Displays
ACER LCD P246HBD 1920x1080 (24") - Dell 1280x800
Screen Resolution
ACER LCD P246HBD ~ [1920X1080] - DELL ~ [1280x800]
Hard Drives
500 GB WD Caviar SE116 7200rpm SATA2
PSU
Corsair 750W Power Supply
Case
Coolermaster CM Scout
Cooling
Zalman FS-C77 Fatal1ty CPU Cooler
Keyboard
Logitech G15
Mouse
Coolermaster Sentinel Advanced
Internet Speed
[↓ 10 MB/s DL] [↑ 1 MB/s UL]
Other Info
- ROCCAT™ Kave – Solid 5.1 Surround Sound Gaming Headset
- Not overclocking
Back
Top