Win 7/Irql_less_than_not_equal
-
Win 7/Irql_less_than_not_equal
Hey, just joined the forums. Have had intermittant crashing with IRQL_LESS_THAN_NOT_EQUAL as the most common error message, even went so far as to reformat to fix. My best guess is it was a driver problem, even installed new drivers for the wireless card.
Mostly happens with utorrent active, but can happen mostly anytime.
Attached is the data dump, thanks for any help you can give~
Last edited by Skion; 02 May 2011 at 22:42.
-
-
Your only BSOD was caused by your Intel WiFi driver. Download the newest driver from here http://downloadcenter.intel.com/Deta...20Applications
If the BSOD continues then enable driver verifier - Driver Verifier - Enable and Disable
BSOD BUGCHECK SUMMARY
Code:
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 26 23:32:33.563 2011 (UTC - 4:00)
System Uptime: 0 days 18:07:17.155
*** WARNING: Unable to verify timestamp for NETw1v64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw1v64.sys
Probably caused by : NETw1v64.sys ( NETw1v64+54ed )
BUGCHECK_STR: 0xA
PROCESS_NAME: uTorrent.exe
FAILURE_BUCKET_ID: X64_0xA_NETw1v64+54ed
BiosReleaseDate = 12/25/2009
SystemManufacturer = ASUSTek Computer Inc.
SystemProductName = G60JX
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
-
Most recent crash didn't produce a minidump which was a problem I had before the reformat as well. Not sure if that's a symptom for something else but running the verifier anyways.
-
-
Your logs are only showing one BSOD happening since april 13th (that's as far back as the log goes)
Did you update the driver?
-
>mgorman87
Yeah, which is why I was surprised It crashed again. No minidump, but event viewer showed a critical power event.
"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
At least the crashing is fairly rare, it still bugs me that I don't know what the problem is.
-
>mgorman87
Yeah, which is why I was surprised It crashed again. No minidump, but event viewer showed a critical power event.
"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
At least the crashing is fairly rare, it still bugs me that I don't know what the problem is.
That doesn't mean it was a bluescreen. It just means your computer was reset abruptly. Update the drivers and let me know if the problem continues.
-