Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

BSOD driver irql not less or equal error


  • Please log in to reply

#16
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
Oh crap! XD

drivermax1.jpg
drivermax2.jpg
drivermax3.jpg
drivermax4.jpg
drivermax5.jpg
  • 0

Advertisements


#17
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK interesting but the driver you need to update first is the 3rd page bottom driver which is the smbus driver. This is the main chipset driver for the motherboard. That alone may resolve the issue since the driver is out of date it may not be reading the error driver correctly.
  • 0

#18
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
Alright, done. Is there a way to check, aside from the sfc scan, that everything's fixed?

Also, is it advisable to take some action toward updating some of that load of drivers, or could that get messy?
  • 0

#19
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I would suggest after that driver has been installed that you start at the top of the list and get each of the drivers that need to be updated. Remember with the free version of DriverMax you can only download and install 2 drivers a day.
Update the first driver and then let me know if the BSOD's still happen. This will not be a fast part to do as I said above only 2 a day can be updated.
  • 0

#20
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
All right, I'll go ahead and start updating the other drivers (I think I'm going to go ahead and purchase a short license and do a larger number of updates at once). If I continue having issues, I'll let you know.

Thank you so much for all your help! I really appreciate it. :)


EDIT:

WHOOPS. Like, directly after I finished typing that, I had this BSOD:

==================================================
Dump File : Mini020212-01.dmp
Crash Time : 2/2/2012 2:38:53 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffffa80`098f8000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa60`00e5d1f2
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+521f2
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini020212-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 273,120
==================================================

Edited by Crownflame, 02 February 2012 - 02:45 PM.

  • 0

#21
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK that one is caused by the OS.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article.)
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.


We have checked the memory already so that cannot be the cause. I am more leaning toward all those drivers that are out of date right now. :whistling:
  • 0

#22
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
All right! I shall work on those. XD

Thanks so much!
  • 0

#23
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
All right, I've updated all of the drivers, and I was cool for a couple days, but then I started getting more BSOD.

Even after I updated the drivers, the sfc scan was still saying there were corrupted files.

Here are the BSOD dumps:

==================================================
Dump File : Mini020612-02.dmp
Crash Time : 2/6/2012 12:09:13 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffffa80`0be60000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa60`010541f2
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+521f2
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini020612-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 273,120
==================================================

==================================================
Dump File : Mini020612-01.dmp
Crash Time : 2/6/2012 1:11:43 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffffa80`0b7e8000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa60`010571f2
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini020612-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 273,120
==================================================

==================================================
Dump File : Mini020512-01.dmp
Crash Time : 2/5/2012 12:15:12 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffffa80`0b508000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa60`010521f2
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+521f2
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini020512-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 273,120
==================================================


Just to make sure, I'm going to run memtest again this afternoon. I need to get some actual not-computer stuff done anyhow. XD

Edited by Crownflame, 06 February 2012 - 12:19 PM.

  • 0

#24
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I don't remember if I had you do this but just in case please follow the below instructions,

Tutorial for running chkdsk in Vista\Win 7 located HERE.
  • 0

#25
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
All right, done. I ran both tests ("fix file system errors" and "recovery of bad sectors").
  • 0

Advertisements


#26
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Are you saying chkdsk found and corrected problems?
If so redo the chkdsk again?
  • 0

#27
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
I actually don't know. The results screen whipped on by before I could comprehend it (it scanned at startup). I can try and run it again, though.

Oh wait. Here's what the log in the Event Viewer said about it. I think. XD

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 2/6/2012 11:18:25 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: SarahSchowen-PC
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.
216768 file records processed.

711 large file records processed.

0 bad file records processed.

0 EA records processed.

50 reparse records processed.

272906 index entries processed.

0 unindexed files processed.

216768 security descriptors processed.

Cleaning up 1139 unused index entries from index $SII of file 0x9.
Cleaning up 1139 unused index entries from index $SDH of file 0x9.
Cleaning up 1139 unused security descriptors.
28070 data files processed.

CHKDSK is verifying Usn Journal...
36142320 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
216752 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
48514001 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

297170037 KB total disk space.
102695384 KB in 132770 files.
86688 KB in 28071 indexes.
0 KB in bad sectors.
331957 KB in use by the system.
65536 KB occupied by the log file.
194056008 KB available on disk.

4096 bytes in each allocation unit.
74292509 total allocation units on disk.
48514002 allocation units available on disk.

Internal Info:
c0 4e 03 00 55 74 02 00 21 8f 04 00 00 00 00 00 .N..Ut..!.......
b4 08 00 00 32 00 00 00 00 00 00 00 00 00 00 00 ....2...........
30 c7 98 77 00 00 00 00 50 23 e2 ff 00 00 00 00 0..w....P#......

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.micro.../events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-02-07T05:18:25.000Z" />
<EventRecordID>4026</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>SarahSchowen-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.
216768 file records processed.

711 large file records processed.

0 bad file records processed.

0 EA records processed.

50 reparse records processed.

272906 index entries processed.

0 unindexed files processed.

216768 security descriptors processed.

Cleaning up 1139 unused index entries from index $SII of file 0x9.
Cleaning up 1139 unused index entries from index $SDH of file 0x9.
Cleaning up 1139 unused security descriptors.
28070 data files processed.

CHKDSK is verifying Usn Journal...
36142320 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
216752 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
48514001 free clusters processed.

Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

297170037 KB total disk space.
102695384 KB in 132770 files.
86688 KB in 28071 indexes.
0 KB in bad sectors.
331957 KB in use by the system.
65536 KB occupied by the log file.
194056008 KB available on disk.

4096 bytes in each allocation unit.
74292509 total allocation units on disk.
48514002 allocation units available on disk.

Internal Info:
c0 4e 03 00 55 74 02 00 21 8f 04 00 00 00 00 00 .N..Ut..!.......
b4 08 00 00 32 00 00 00 00 00 00 00 00 00 00 00 ....2...........
30 c7 98 77 00 00 00 00 50 23 e2 ff 00 00 00 00 0..w....P#......

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

Edited by Crownflame, 07 February 2012 - 10:25 AM.

  • 0

#28
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Please redo the steps in post 24
  • 0

#29
jcgriff2

jcgriff2

    Member

  • Expert
  • 92 posts
  • MVP
Also... I noticed tcpip.sys appeared in most recent dumps.

be sure your networking drivers are updated - both Ethernet and wifi (if applicable).

http://www.sysnative.../drivers/table/

Regards. . .

jcgriff2
  • 0

#30
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
After chkdsk /r is run again and results are verified we can work on the drivers. :thumbsup:
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP