• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Solved Windows 10 Blue Screen DRIVER_IRQL_NOT_LESS_OR_EQUAL

Status
Not open for further replies.
Much appreciated for the dump file :)

The BSODs you are experiencing are indeed caused by one driver, the touchpad driver.

Before we go futher, what make and model is the laptop in question? Every laptop uses a different driver for their hardware
 
I tried it but the link that was on the website to the website with the driver was broken, so I went to hp's website and downloaded the latest driver, and in the description it actually says it fixes the problem of intermittent bsods during Windows updates, so hopefully that fixed it, thanks for the help and the patience. I'll update you within the next week and tell you if I've gotten any more bsods.
 
  • Like
Reactions: jmarket
Okay, now i'm getting pissed, I just had another BSOD this time its related to TCPIP, here is the dump file, please help. I don't know whats going on with this D*** laptop. Is there a utility you could recommend that I can run that would give you an idea of whats going on with this thing? Also isn't Windows supposed to save all minidump files, This was the only one in the folder, the other one isn't there anymore.
 

Attachments

  • 040418-7312-01.dmp
    1.8 MB · Views: 5
Hmm that is very weird indeed.

This may be a bigger problem than we think. Let me have you run a tool to check your hard disk.

  • Click on the Start button and in the search box, type Command Prompt
  • When you see Command Prompt on the list, right-click on it and select Run as administrator
  • When command prompt opens, copy and paste the following command into it, press Enter.

    Code:
    sfc /scannow
  • Wait for this to finish before you continue
  • Copy and paste the following command, press Enter.

    Code:
    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > %userprofile%\Desktop\sfc.txt
That will create sfc.txt on your Desktop. Please attach sfc.txt to your next post:
  • Open Reply window. Click 'More Reply Options'.
  • Go to the end of your text (if any).
  • Under 'Attach Files' click 'Choose Files..'
  • For 'File name' paste this: %userprofile%\Desktop\sfc.txt
  • Click the 'Add to Post' link which will appear on the right when the file has been uploaded.
  • Click 'Add Reply'.
After the above instructions are complete, please do the below again for me. I will have to do deeper digging into this.

Please download the Sysnative BSOD Dump + System File Collection App - save to Documents folder.

Run the app - Double-click on the downloaded EXE file
Output = new folder created in Documents + a zipped version -- SysnativeFileCollectionApp folder + SysnativeFileCollectionApp.zip.

Please note that the app averages ~3 minutes to run on most systems; other systems - it my take as long as 10-15 minutes to run. Please be patient.

Also note: The app auto-zips the SysnativeFileCollectionApp output folder. It is located in your Documents folder.
Windows Explorer should open and highlight the zipped folder

Please attach the SysnativeFileCollectionApp.zip to your post and await further instructions :)
 
Hmm that is very weird indeed.

This may be a bigger problem than we think. Let me have you run a tool to check your hard disk.

  • Click on the Start button and in the search box, type Command Prompt
  • When you see Command Prompt on the list, right-click on it and select Run as administrator
  • When command prompt opens, copy and paste the following command into it, press Enter.

    Code:
    sfc /scannow
  • Wait for this to finish before you continue
  • Copy and paste the following command, press Enter.

    Code:
    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > %userprofile%\Desktop\sfc.txt
That will create sfc.txt on your Desktop. Please attach sfc.txt to your next post:
  • Open Reply window. Click 'More Reply Options'.
  • Go to the end of your text (if any).
  • Under 'Attach Files' click 'Choose Files..'
  • For 'File name' paste this: %userprofile%\Desktop\sfc.txt
  • Click the 'Add to Post' link which will appear on the right when the file has been uploaded.
  • Click 'Add Reply'.
After the above instructions are complete, please do the below again for me. I will have to do deeper digging into this.

Please download the Sysnative BSOD Dump + System File Collection App - save to Documents folder.

Run the app - Double-click on the downloaded EXE file
Output = new folder created in Documents + a zipped version -- SysnativeFileCollectionApp folder + SysnativeFileCollectionApp.zip.

Please note that the app averages ~3 minutes to run on most systems; other systems - it my take as long as 10-15 minutes to run. Please be patient.

Also note: The app auto-zips the SysnativeFileCollectionApp output folder. It is located in your Documents folder.
Windows Explorer should open and highlight the zipped folder

Please attach the SysnativeFileCollectionApp.zip to your post and await further instructions :)

I culdn't find the option more reply options, so I just uploaded the txt file to this reply, also the SFC app file.
 

Attachments

  • sfc.txt
    53.6 KB · Views: 5
  • SysnativeFileCollectionApp.zip
    1.4 MB · Views: 4
I got yet another BSOD last night, this one was agin related to the touchpad, so I'll attach the minidump file. I'm wondering if the issue is my SSD, becuase I wasn't getting all of these BSODs until after I installed my SSD. I ordered one off of Amazon it is a WD Blue NAND SATA SSD M.2 2280. It's 250 GB.


Okay so I tried to find the minidump file but it's not there, I'm assuming that's because Windows said it was collecting information but it was stuck on 0% for about 10 minutes, so I just did a hard restart so I'm assuming since it didn't collect any info, it didn't create a minidump file. But it was the same BSOD that I was getting before related to the touchpad.
 
Last edited:
You can run

Code:
chkdsk /f

and it'll be fine. Just do not run chdsk /r or defrag it.

As to your question about what caused it, a chkdsk scan might likely repair it for you. We already replaced a problem driver and it seems to be ok :)
 
You can run

Code:
chkdsk /f

and it'll be fine. Just do not run chdsk /r or defrag it.

As to your question about what caused it, a chkdsk scan might likely repair it for you. We already replaced a problem driver and it seems to be ok :)
Speaking of defragging. I just checked defrag and disk optimization and Windows had it automatically set to defrag my C drive weekly, my C Drive is my SSD though, and from wat I understand SSD's don't need to be defragged and shouldn't be defragged becuase of unneccessary wear and tear on them from the defrag process. So I just took that drive off the list.

I ran or am running chkdsk right now, I'm not sure which, I went to run and put in chkdsk /f and prssed enter but nothing happened. Shouldn't I get a progress window or something if it's running?
 
Last edited:
Status
Not open for further replies.