• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

BSOD crashes

Chryso

Diamond Member
I have had no problems with my computer for about a year or so.
Suddenly, in the last month I have begun getting a BSOD with the message IRQ_NOT_LESS_THAN_OR_EQUAL_TO. The only hardware change in that time was the addition of a card reader. I have removed the card reader in the hope that it was causing the problem but it still occurs. It happens about once a week and there really doesn't seem to be anything consistently going on when it occurs.
Any ideas?
 
probably a faulty driver for the card reader, try updating it. are the BSOD random? also use windows debugger to narrow it down.

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Most of the time installed Windows Debugger, and using it to check the dump file will tell why windows crashed. after installing run !analyze -v and lmv commands to find out what did it.
**** after dbg_x86_6.6.07.5.exe installed, open windbg, set FILE|symbol file path to click "reload" box, then ok.
SRV*c:\local cache*http://msdl.microsoft.com/download/symbols

**** then file|open crash dump and run the commands

!analyze -v will tell you the error, click the link on the drive
under Debugging Details:
DEFAULT_BUCKET_ID -tells the general category of the failure
IMAGE_NAME -tells what driver is at fault, like if DRIVER_FAULT
click on the driver highlighted under MODULE_NAME it tells info like path to that module

lmv -tells loaded modules in detail, then click edit|find for that driver listed under IMAGE_NAME


****IF
*if driver at fault is ntoskrl.exe (windows core) or win32.sys (driver most responsible for the GUI layer on windows),it is PROBABLY NOT WINDOWS needing to be reinstalled, it is PROBABLY some third-party device driver that called it.
*if the driver at fault is an antivirus driver, it is PROBABLY NOT the anti virus needing to be reinstalled.
*


 
Back
Top