Windows 10 Blue Screen DRIVER_IRQL_NOT_LESS_OR_EQUAL

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Brandon_Byrnes
    PCHF Member
    • Jan 2017
    • 626

    #1

    Windows 10 Blue Screen DRIVER_IRQL_NOT_LESS_OR_EQUAL

    I keep getting this blue screen and Iโ€™d like to know what it is and how to remedy it. I looked at all of my drivers and they are all functioning and up to date. Under the error message it says What Failed: SynTP.sys, so iโ€™m assuming that has to be fixed. Iโ€™ve goten this error message atleast 10 or 15 times within the last couple of months. It seems to always happen when I am just about to shut down my laptop. Can someone help me? I try scanning the QR code that goes with the screen but the page never loads. Ive attached a picture of the screen to this post.
  • veeg
    PCHF Director
    • Jul 2016
    • 8977

    #2
    Hello

    Hopefully some of our members will chime in soon.
    jmarket @phillpower2

    Comment

    • jmarket
      PCHF Owner
      • Jan 2015
      • 7636

      #3
      The SysTP.sys file is related to the Synaptics Touchpad.

      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

        #4
        Originally posted by jmarket
        The SysTP.sys file is related to the Synaptics Touchpad.

        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

          #5
          Well it just happened again about 2 mins ago, can someone plaee help, this BSOD is getting very annoying

          Comment

          • jmarket
            PCHF Owner
            • Jan 2015
            • 7636

            #6
            Sorry for the delay @Brandon Byrnes

            Your zip file does not contain any BSOD files. Is your system setup to automatically save BSOD dump files?

            Please follow the instructions here and please wait until another BSOD appears and then follow the below instructions again to collect the necessary files:

            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

              #7
              Does the location where I open the file have to be the Documents folder? Because all of my downloads go to my Downloads folder, and I opened and ran the program from there.

              Comment

              • jmarket
                PCHF Owner
                • Jan 2015
                • 7636

                #8
                It doesnโ€™t matter where you download it to. The program automatically pulls the necessary files from the correct locations

                Comment

                • Brandon_Byrnes
                  PCHF Member
                  • Jan 2017
                  • 626

                  #9
                  I reran the program. I just had a BSOD on Thursaday after I posted the initial results so hopefully this time it will show the dump files.

                  Comment

                  • jmarket
                    PCHF Owner
                    • Jan 2015
                    • 7636

                    #10
                    Thereโ€™s still no BSOD file.

                    It looks like you didnโ€™t follow the BSOD instructions. The
                    [ICODE]DebugInfoType[/ICODE]
                    is showing a value of 7 instead of 3, which means that when the computer reboots it wonโ€™t save dump files.

                    If you go to %SystemRoot%\Minidump, are there files there?

                    Comment

                    • Brandon_Byrnes
                      PCHF Member
                      • Jan 2017
                      • 626

                      #11
                      Originally posted by jmarket
                      Thereโ€™s still no BSOD file.

                      It looks like you didnโ€™t follow the BSOD instructions. The
                      [ICODE]DebugInfoType[/ICODE]
                      is showing a value of 7 instead of 3, which means that when the computer reboots it wonโ€™t save dump files.

                      If you go to %SystemRoot%\Minidump, are there files there?
                      Nope, the folder is empty. What should I do to enable it so that it saves dump files?

                      Comment

                      • Brandon_Byrnes
                        PCHF Member
                        • Jan 2017
                        • 626

                        #12
                        Iโ€™m not sure if it will help but I have a Reliability Monitor report, but its in xml format so I canโ€™t upload it.

                        Comment

                        • jmarket
                          PCHF Owner
                          • Jan 2015
                          • 7636

                          #13
                          Let me post the instructions here. Please make sure to follow them

                          How to collect log files for PCHF

                          Please Note: As long as you have any P2P/cracked/warez program(s) installed, as per the PCHF Rules, we will not be able to offer you assistance. Please remove any and all P2P Clients and wait for further BSODโ€™s before posting them. Also, ensure you only have one Firewall and one Anti-Virus installed at any one time. Any of the above mentioned software can produce false readings in these logs.

                          [ul]
                          [li]Navigate to your dump directory (in most cases itโ€™ll be in C:\Windows\Minidump or C:\Minidump.[/li][li]Gather all the logs and either put them into a ZIP or RAR archive or attach them to your post.[/li][/ul]
                          Troubleshooting

                          Minidumps are normally enabled by default. However there may be several reasons why they do not appear in this folder.

                          Make sure minidumps are enabled:
                          [ul]
                          [li]Go to My Computer, Control Panel, System, then click the Advanced tab.[/li][li]Under โ€œStartup and Recoveryโ€, click Settings.[/li][li]Under โ€œSystem failureโ€, make sure Write and event to the system log is ticked.[/li][li]Under โ€œWrite debugging informationโ€, make sure Small Memory Dump is selected.[/li][/ul]
                          You can also do this at the command prompt should you wish to do so:
                          [ul]
                          [li]Go to Start, All Programs, Accessories, and click on Command Promptโ€ฆ Note: if your running Vista or newer, please right click on Command Prompt and select Run as Administrator.[/li][li]Enter the following in the Command Prompt, pressing enter after each:[/li][li][ICODE][/li]wmic recoveros set DebugInfoType = 3 wmic recoveros set MiniDumpDirectory = %SystemRoot%\minidump [/ICODE]
                          [/ul]
                          You must also make sure your Paging File is set to same drive the OS is installed on:
                          [ul]
                          [li]Go to My Computer, Control Panel, System followed by Advanced tab.[/li][li]Under โ€œPerformanceโ€, click Settings, followed by the Advanced tab.[/li][li]Click Change towards the bottom of the screen, and then click on the drive letter that contains your Operating System.[/li][li]For that drive, if โ€œNo paging fileโ€ has been selected, click System managed size, and finally restart your PC.[/li][/ul]

                          Note: If you have performed a disk cleanup since the you received a BSOD, it would have been deleted.

                          You must now wait or reproduce your blue screen so that further log files can be generated.

                          If you find that a log file is still not being generated, this could be an indication of a more serious hardware problem.
                          In this case weโ€™ll need to further troubleshoot the problem hardware.

                          Comment

                          • jmarket
                            PCHF Owner
                            • Jan 2015
                            • 7636

                            #14
                            Any updates for us @Brandon Byrnes?

                            Comment

                            • Brandon_Byrnes
                              PCHF Member
                              • Jan 2017
                              • 626

                              #15
                              Originally posted by jmarket
                              Any updates for us @Brandon Byrnes?
                              Sorry, Iโ€™m going to follow your instructions and then update you later today.

                              Comment

                              Working...