BSOD UNEXPECTED_KERNEL_MODE_TRAP

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Ben_Davis
    PCHF Member
    • Oct 2017
    • 52

    #1

    BSOD UNEXPECTED_KERNEL_MODE_TRAP

    Happens all the time randomly when i’m playing games, nothing in particular seems to set this off, any help would be greatly appreciated.
    OS: Win 10
  • Rustys
    PCHF Member
    • Jul 2016
    • 7862

    #2
    Follow posting instructions form the following link.

    Comment

    • Ben_Davis
      PCHF Member
      • Oct 2017
      • 52

      #3
      Sorry to take so long, been trying to gather some stuff on my pc crashes, it happenend just moments ago with no BSOD and instead just went to a black screen then rebooted. Also just as a note there is nothing in my minidump folder atm.

      Comment

      • phillpower2
        PCHF Administrator
        • Sep 2016
        • 15206

        #4
        Are crash dmps enabled on your computer.

        What you describe in your reply #3 suggests more of a hardware issue, overheating and/or a flaky PSU coming to mind.

        Please provide information about your computer, is it a custom build or brand name such as Dell or HP, if a brand name, provide the model name or series number (not serial) if a custom build post the brand and model name or number for the MB, the RAM (including the amount) add on video card if one is used and the PSU (power supply unit) providing these details will enable us to better assist you.

        Comment

        • Ben_Davis
          PCHF Member
          • Oct 2017
          • 52

          #5
          Just enabled auto dumping, i’ll reply when it next happens.
          I currently have a RM750X PSU, an msi gaming m3 motherboard, 2x8gb (panther something by apacer) and an asus gtx 1060 6gb

          edit: and an i5 7500

          Comment

          • phillpower2
            PCHF Administrator
            • Sep 2016
            • 15206

            #6
            Are you overclocking at all?

            Corsair are a good brand of PSU but I have seen a few bad reviews of your particular model, one here posts the following;

            Cons: This thing failed after 2 weeks
            It would randomly turn off my whole system without warning, just a mess, and I was so confused Until I read a post about my symptoms and pointed toward a faulty power supply then I use my 10 year warranty from corsair and then they gave me a better power supply instead because they didn’t have an rmx on hand, great customer service though, hopefully it will function

            Comment

            • Ben_Davis
              PCHF Member
              • Oct 2017
              • 52

              #7
              Thanks phill heres a copy of a crash dump i just got, although recently it has begun to do what you have described above, my computer has been randomly starting to freeze where the screen will instantly pause the audio will cut out and ill have to manually restart it, hope you can make some sense of this, and sorry its taken so long for me to get this

              Edit: No i’m not overclocking as far as i know (although asus gpu tweak is set to gaming mode so it may be automatically overclocking?)

              Edit 2: I bought the psu from pccasegear, i’ve found how to claim a warranty etc but if this does turn out to be the issue what would i describe as the fault?

              Comment

              • phillpower2
                PCHF Administrator
                • Sep 2016
                • 15206

                #8
                Nothing specific showing up in your crash dmp as all that is listed is PROCESS_NAME: System and IMAGE_NAME: ntkrnlmp.exe which could just about anything, you can check the latter here

                Lets see if DriverVerifier can flush out any rogue driver/s, see info below but please note that not all options are available in Windows 10.

                To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of jcgriff2 (y)

                1. Create a Windows System Restore Point -

                Vista - START | type rstrui - create a restore point
                Windows 7 - START | type create | select “Create a Restore Point”
                Windows 8/ 8.1 - Using Microsoft System Restore (Windows*8) | HP® Support

                2. Run Driver Verifier -
                • Windows 7 & Vista - START | type verifier
                • Windows 8.1 & 8 - Press WIN +X keys | select “Command Prompt (Admin)” | type verifier

                Make these selections -
                1. Select 2nd option - Create custom settings (for code developers)
                2. Select 2nd option - Select individual settings from a full list
                3. Check these boxes -

                ▪️ Special Pool
                ▪️ Pool Tracking
                ▪️ Force IRQL checking
                ▪️ Deadlock Detection
                ▪️ Security Checks (new as of Windows 7)
                ▪️ Concurrency Stress Test (new as of Windows 8)
                ▪️ DDI compliance checking (new as of Windows 8)
                ▪️ Miscellaneous Checks

                4. Select last option - Select driver names from a list
                5. Click on the Provider heading - sorts list by Provider
                6. Check ALL boxes where “Microsoft” IS NOT the Provider
                7. Click on Finish
                8. Re-boot[/HIDE]
                • If the Driver Verifier (DV) finds a violation, [color=“#FF0000”]it will result in a [color=“#0000FF”]BSOD
                • After re-start, you may not be able to log on to normal Windows

                … • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up

                … • Select “System Restore”

                … • Choose the restore point that you created in step #1
                • For Driver Verifier status

                — select last option, 1st screen -or-

                — type verifier /query (in a cmd/DOS screen)
                • To turn Driver Verifier off - verifier /reset then re-boot
                • The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
                • All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

                If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.

                Please note that Driver Verifier may need to be left running for up to 72hrs, you should use the computer as you normally would and DV will not affect this unless a BSOD occurs.

                Comment

                • Ben_Davis
                  PCHF Member
                  • Oct 2017
                  • 52

                  #9
                  Thanks again for the help, currently running windows 10 but ‘Concurrency Stress Test’ was not an option i was able to select, also i’m unsure as to how I make my BSOD dumps VERIFIER_ENABLED_MINIDUMPs.
                  Under system failure my enabled settings are as follows.
                  Write an event to the system log
                  Auto restart
                  Auto memory dump
                  Dump file: “%SystemRoot%\MEMORY.DMP”
                  Disable automatic deletion of memory dumps when disk space is low

                  Comment

                  • phillpower2
                    PCHF Administrator
                    • Sep 2016
                    • 15206

                    #10
                    Same location Ben, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.
                    Originally posted by Ben Davis
                    currently running windows 10 but ‘Concurrency Stress Test’ was not an option i was able to select,
                    For clarity, it was mentioned in my reply #8 that not all options are available in Windows 10 (y)

                    Comment

                    • Ben_Davis
                      PCHF Member
                      • Oct 2017
                      • 52

                      #11
                      The verifier didnt cause me a BSOD and nothing was generated in the Minidump folder i was just listing out my system failure settings to see if they were okay or not, where do i go from here?

                      Edit: Since the verifier has found no problems should i turn it off?

                      Comment

                      • phillpower2
                        PCHF Administrator
                        • Sep 2016
                        • 15206

                        #12
                        Settings info acknowledged and yes they are as they should be (y)
                        Originally posted by phillpower2
                        [COLOR=rgb(184, 49, 47)]Please note that Driver Verifier may need to be left running for up to 72hrs, you should use the computer as you normally would and DV will not affect this unless a BSOD occurs.
                        [/COLOR]
                        [COLOR=rgb(184, 49, 47)]
                        Please be sure to run DV for a minimum of 72 hrs from when it was first initiated, longer is better and it really does not affect system performance.[/color]

                        Comment

                        • Ben_Davis
                          PCHF Member
                          • Oct 2017
                          • 52

                          #13
                          DV has been running for almost 72hrs now, how do i tell when it’s done? and what do i do when it’s done?

                          Comment

                          • Ben_Davis
                            PCHF Member
                            • Oct 2017
                            • 52

                            #14
                            PC just crashed while running Space Engineers.

                            Edit: (You posted something about wanting the dumps that occured while driver verifier was running, just note this crash error has occurred before.)

                            Comment

                            • Ben_Davis
                              PCHF Member
                              • Oct 2017
                              • 52

                              #15
                              Just crashed again (these posts are being made immediately after crashing btw)

                              Comment

                              Working...