Windows 7 Forums
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: Bsod Driver_irql_not_less_or_equal

17 May 2012   #1
illegaltender

Windows 7 64 bit
 
 
Bsod Driver_irql_not_less_or_equal

Hi guys, I have this problem which i posted earlier which i accidentally clicked that it was solved and as it was my first post i was unaware of the rules. I have now followed the rules and done as told.

I was told by my computer tech that this is a problem with regards to the devices which are plugged in to my usb port but I have tested each device and all of them individually crashed.

Is there anyway to solve this issue?

Thanks in advance!


My System SpecsSystem Spec
17 May 2012   #2
illegaltender

Windows 7 64 bit
 
 

Oh yes some specs on my pc.

s Windows 7 . . .
- x86 (32-bit) or x64 ?
x64
- the original installed OS on the system?
Windows 7 is the only one that's been installed on the system
- an OEM or full retail version?
OEM


- What is the age of system (hardware)?
1.5 year old
- What is the age of OS installation (have you re-installed the OS?)
1.5 year old

System Specs:
intel i5 520m
nvidia gefore gt335m
4gb ram


If included the DMPs of the last few crashes, if I have done anything wrong or you need more information please tell me, and thank you for taking your time to help.
My System SpecsSystem Spec
17 May 2012   #3
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

This smells like a driver causing it, but I cannot ascertain on exact cause from just these minidumps.

Your best option is to turn on Driver Verifier. Do not select the following checks: IRP Logging, Force Pending I/O Requests, and Low Resource Sim. Follow all other instructions. Keep DV on and let your system crash a few times while it's on. Send us the new crashdumps.
My System SpecsSystem Spec
17 May 2012   #4
illegaltender

Windows 7 64 bit
 
 

Hi! Thanks for your help!

I can cauze it to crash now through the movement of files in my D drive however when it crashes, I am not sure if the logs are stored as it just hangs on the BSOD instead of the normal automatic reboot. Is it supposed to be this way?
My System SpecsSystem Spec
17 May 2012   #5
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

That probably has to do with events like this filling up the first half of the syslog:

Code:
Event[4242]:
  Log Name: System
  Source: Ntfs
  Date: 2012-05-15T20:19:11.647
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: User-PC
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume DATA.
Same is said for volume D:, which I presume is the same thing? Either way, it needs fixin. Do a chkdsk on all your drives. If you don't know how, right click the drive, then go to Properties, then go to the Tools tab, then "Check now..." button under Error-checking. Select both options, and click to attempt to check. It most likely ask you to schedule one at next boot up. Do so for each drive, then restart PC. This will take a while to run.
My System SpecsSystem Spec
17 May 2012   #6
illegaltender

Windows 7 64 bit
 
 

Hi! I did just that and it says its fine though. Should I upload the new crash dumps after the verifier? I am not sure if the new dumps are recorded as it does not auto reboot after it crashes and just hangs on the blue screen
My System SpecsSystem Spec
17 May 2012   #7
writhziden

Windows 7 Home Premium 64 Bit
 
 

You may need to run Verifier in chunks. Run 5 non-Microsoft drivers at a time using the same settings as before. Sometimes, having all non-Microsoft drivers Verifier enabled can prevent .dmp files from being created. In these situations, I suggest running 5 non-Microsoft drivers at a time for 36 hours on each set of 5, or until a crash occurs, whichever comes first. Then start the next 5 and do the same 36 hours/crash occurs test. Once you have completed all sets, upload the crash reports again.

Vir Gnarus may have a different method used in these situations that may take less time and testing, but I thought I would pass along my experience in the meantime.
My System SpecsSystem Spec
18 May 2012   #8
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

In the meantime, as you're doing that, you'll also want to runSeatools on your drives. While the chkdsk may not show any file system corruption, the drives themselves (or the drive controller) may be bugging out. Run all tests including self tests except the Advanced tests.
My System SpecsSystem Spec
Reply

 Bsod Driver_irql_not_less_or_equal




Thread Tools



Similar help and support threads for2: Bsod Driver_irql_not_less_or_equal
Thread Forum
BSOD driver_irql_not_less_or_equal BSOD Help and Support
BSOD Win 7 --- Driver_IRQL_Not_Less_Or_EQUAL BSOD Help and Support
BSOD driver_irql_not_less_or_equal BSOD Help and Support
Bsod: Driver_irql_not_less_or_equal BSOD Help and Support
Bsod driver_irql_not_less_or_equal BSOD Help and Support
bsod: driver_irql_not_less_or_equal BSOD Help and Support
Bsod driver_irql_not_less_or_equal BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:53 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App