Windows 10 Blue Screen DRIVER_IRQL_NOT_LESS_OR_EQUAL

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jmarket
    PCHF Owner
    • Jan 2015
    • 7636

    #16
    Any updates for us @Brandon Byrnes? After 72 hours I will assume your issue is solved unless I hear back from you

    Comment

    • Brandon_Byrnes
      PCHF Member
      • Jan 2017
      • 626

      #17
      Originally posted by jmarket
      Any updates for us @Brandon Byrnes? After 72 hours I will assume your issue is solved unless I hear back from you
      I changed all the setting that you told me to change, it had my memory dump set to my D drive which I only use for storage, so I changed it to my C drive which contains my OS. I went to the minidump folder but it is empty, which Iโ€™m assuming is becuase it appears that there wasnโ€™t a minidump folder until I just created it today by following your instructions. I tried navigating to the path of the dump folder on my D drive but anytime I put the patth in it says it canโ€™t find that file, so Iโ€™m not sure why that is happening. So for now it appears that I canโ€™t get a copy of the minidump files, I tried going to its properties and seeing previous versions but there are no previous versions to go back to. So I think I will probably just have to wait until I get another BSOD and then get the minidump info for you then, am I right?

      Comment

      • jmarket
        PCHF Owner
        • Jan 2015
        • 7636

        #18
        That is correct. Have you had more BSODโ€™s since my last message?

        Comment

        • Brandon_Byrnes
          PCHF Member
          • Jan 2017
          • 626

          #19
          Originally posted by jmarket
          That is correct. Have you had more BSODโ€™s since my last message?
          No, it seems to happen about once a month.

          Comment

          • Brandon_Byrnes
            PCHF Member
            • Jan 2017
            • 626

            #20
            Originally posted by jmarket
            That is correct. Have you had more BSODโ€™s since my last message?
            Okay well I think you jinzed me because it just happened now. I was in Firefox on Google and looking at some pictures, I then closed Firefox and immediately got a BSOD, here is the minidump file.

            Comment

            • jmarket
              PCHF Owner
              • Jan 2015
              • 7636

              #21
              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

              Comment

              • Brandon_Byrnes
                PCHF Member
                • Jan 2017
                • 626

                #22
                Originally posted by jmarket
                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
                Itโ€™s an HP ProBook 450 G3

                Comment

                • jmarket
                  PCHF Owner
                  • Jan 2015
                  • 7636

                  #23
                  Try the driver listed here

                  Comment

                  • Brandon_Byrnes
                    PCHF Member
                    • Jan 2017
                    • 626

                    #24
                    Originally posted by jmarket
                    Try the driver listed here
                    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.

                    Comment

                    • Brandon_Byrnes
                      PCHF Member
                      • Jan 2017
                      • 626

                      #25
                      Okay, now iโ€™m getting ******, 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.

                      Comment

                      • jmarket
                        PCHF Owner
                        • Jan 2015
                        • 7636

                        #26
                        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.

                        [ul]
                        [li]Click on the Start button and in the search box, type Command Prompt[/li][li]When you see Command Prompt on the list, right-click on it and select Run as administrator[/li][li]When command prompt opens, copy and paste the following command into it, press Enter.[/li]
                        [ICODE]sfc /scannow[/ICODE]
                        [li]Wait for this to finish before you continue[/li][li]Copy and paste the following command, press Enter.[/li]
                        [ICODE]findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > %userprofile%\Desktop\sfc.txt[/ICODE]
                        [/ul]
                        That will create sfc.txt on your Desktop. Please attach sfc.txt to your next post:
                        [ul]
                        [li]Open Reply window. Click โ€˜More Reply Optionsโ€™.[/li][li]Go to the end of your text (if any).[/li][li]Under โ€˜Attach Filesโ€™ click โ€˜Choose Files..โ€™[/li][li]For โ€˜File nameโ€™ paste this: %userprofile%\Desktop\sfc.txt[/li][li]Click the โ€˜Add to Postโ€™ link which will appear on the right when the file has been uploaded.[/li][li]Click โ€˜Add Replyโ€™.[/li][/ul]
                        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

                        Comment

                        • Brandon_Byrnes
                          PCHF Member
                          • Jan 2017
                          • 626

                          #27
                          Originally posted by jmarket
                          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.

                          [ul]
                          [li]Click on the Start button and in the search box, type Command Prompt[/li][li]When you see Command Prompt on the list, right-click on it and select Run as administrator[/li][li]When command prompt opens, copy and paste the following command into it, press Enter.[/li]
                          [ICODE]sfc /scannow[/ICODE]
                          [li]Wait for this to finish before you continue[/li][li]Copy and paste the following command, press Enter.[/li]
                          [ICODE]findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > %userprofile%\Desktop\sfc.txt[/ICODE]
                          [/ul]
                          That will create sfc.txt on your Desktop. Please attach sfc.txt to your next post:
                          [ul]
                          [li]Open Reply window. Click โ€˜More Reply Optionsโ€™.[/li][li]Go to the end of your text (if any).[/li][li]Under โ€˜Attach Filesโ€™ click โ€˜Choose Files..โ€™[/li][li]For โ€˜File nameโ€™ paste this: %userprofile%\Desktop\sfc.txt[/li][li]Click the โ€˜Add to Postโ€™ link which will appear on the right when the file has been uploaded.[/li][li]Click โ€˜Add Replyโ€™.[/li][/ul]
                          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.

                          Comment

                          • Brandon_Byrnes
                            PCHF Member
                            • Jan 2017
                            • 626

                            #28
                            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.

                            Comment

                            • Brandon_Byrnes
                              PCHF Member
                              • Jan 2017
                              • 626

                              #29
                              Should I maybe run chkdsk on my SSD, and will it work with an SSD?

                              Comment

                              • veeg
                                PCHF Director
                                • Jul 2016
                                • 8977

                                #30
                                Any updates for us? Also you probably shouldnโ€™t run chkdsk on a SSD.

                                jmarket

                                Comment

                                Working...