BSOD

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Slytod
    PCHF Member
    • Jan 2017
    • 269

    #1

    BSOD


    I appreciate that the above thread is done; but …

    Went back to the game that I had grown bored of this morning, loaded the save, played for a short while, and sure enough another crash. First one since we last looked at it; but in fairness the first time it’s been pushed to that graphic demand/temperature again. I was just hoping someone could be kind enough to analyse the dump file for me, and confirm what the issue is. Is it the same thing as last time, in which case it’s not really fixed, or is it something new ? Any advice ?

    Thanks in advance.
  • veeg
    PCHF Director
    • Jul 2016
    • 8977

    #2
    Hello

    Hopefully some of our members will chime in soon.
    jmarket

    Comment

    • phillpower2
      PCHF Administrator
      • Sep 2016
      • 15205

      #3
      Originally posted by Slytod
      Is it the same thing as last time, in which case it’s not really fixed, or is it something new ? Any advice ?
      The following is kind of a clue and was something that was mentioned in your previous thread;
      Originally posted by Slytod
      Went back to the game that I had grown bored of this morning, loaded the save, played for a short while, and sure enough another crash.
      If the computer has not been crashing for the past three weeks while you have not been playing that particular game or subjecting the hardware to high temps it suggests that the video card drivers and Windows drivers are ok and that in the case of software it is a problem with the game itself and hardware possibilities include overheating and a weak GPU, a GPU that may have become weak over time by running too hot.

      Have you updated any drivers since May 6th when you told us that things were running stable.

      Your single crash dmp does not tell us anything specific, only that the system crashed.

      PROCESS_NAME: System

      CURRENT_IRQL: 5

      LAST_CONTROL_TRANSFER: from fffff805294034ae to fffff8024f9c8c00

      STACK_TEXT:
      fffff802[ICODE]51cf5578 fffff805[/ICODE]294034ae : 00000000[ICODE]00000119 00000000[/ICODE]0000000e ffffbb8d[ICODE]7805f000 00000000[/ICODE]827d8b5f : nt!KeBugCheckEx
      fffff802[ICODE]51cf5580 fffff805[/ICODE]2b21184c : ffffbb8d[ICODE]7805f000 00000000[/ICODE]00000000 fffff802[ICODE]51cf5d29 00000000[/ICODE]01778349 : watchdog!WdLogEvent5_WdCriticalError+0xce
      fffff802[ICODE]51cf55c0 fffff805[/ICODE]2b1fcb8a : ffffbb8d[ICODE]780b33d0 00000000[/ICODE]00000001 ffffbb8d[ICODE]780a8000 00000000[/ICODE]01778349 : dxgmms2!VidSchiProcessIsrVSyncMultiPlaneOverlay2+0 x114
      fffff802[ICODE]51cf55f0 fffff805[/ICODE]2b1fc176 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]01778349 00000000[/ICODE]00000000 : dxgmms2!VidSchiProcessIsrVSync+0x26a
      fffff802[ICODE]51cf56a0 fffff805[/ICODE]2b1fc0ad : fffff802[ICODE]51cf5829 fffff802[/ICODE]51cf5920 ffffbb8d[ICODE]77de9180 00000000[/ICODE]00000000 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x76
      fffff802[ICODE]51cf56f0 fffff805[/ICODE]2942c2c4 : ffffbb8d[ICODE]75a64030 00000000[/ICODE]00000000 00000000[ICODE]00000001 00000000[/ICODE]00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0x8d
      fffff802[ICODE]51cf5720 fffff805[/ICODE]2be83a23 : ffffbb8d[ICODE]75a64030 fffff802[/ICODE]51cf5829 fffff802[ICODE]51cf5920 ffffbb8d[/ICODE]75b6b000 : dxgkrnl!DxgNotifyInterruptCB+0x74
      fffff802[ICODE]51cf5750 ffffbb8d[/ICODE]75a64030 : fffff802[ICODE]51cf5829 fffff802[/ICODE]51cf5920 ffffbb8d[ICODE]75b6b000 fffff805[/ICODE]2be839b3 : nvlddmkm+0xd3a23
      fffff802[ICODE]51cf5758 fffff802[/ICODE]51cf5829 : fffff802[ICODE]51cf5920 ffffbb8d[/ICODE]75b6b000 fffff805[ICODE]2be839b3 ffffbb8d[/ICODE]75b6b000 : 0xffffbb8d[ICODE]75a64030 fffff802[/ICODE]51cf5760 fffff802[ICODE]51cf5920 : ffffbb8d[/ICODE]75b6b000 fffff805[ICODE]2be839b3 ffffbb8d[/ICODE]75b6b000 00000000[ICODE]00000000 : 0xfffff802[/ICODE]51cf5829
      fffff802[ICODE]51cf5768 ffffbb8d[/ICODE]75b6b000 : fffff805[ICODE]2be839b3 ffffbb8d[/ICODE]75b6b000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : 0xfffff802[ICODE]51cf5920 fffff802[/ICODE]51cf5770 fffff805[ICODE]2be839b3 : ffffbb8d[/ICODE]75b6b000 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 : 0xffffbb8d[/ICODE]75b6b000
      fffff802[ICODE]51cf5778 ffffbb8d[/ICODE]75b6b000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nvlddmkm+0xd39b3
      fffff802[ICODE]51cf5780 00000000[/ICODE]00000000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 ffffbb8d[/ICODE]75a64030 : 0xffffbb8d`75b6b000

      STACK_COMMAND: kb

      FOLLOWUP_IP:
      dxgmms2!VidSchiProcessIsrVSyncMultiPlaneOverlay2+1 14
      fffff805`2b21184c cc int 3

      SYMBOL_STACK_INDEX: 2

      SYMBOL_NAME: dxgmms2!VidSchiProcessIsrVSyncMultiPlaneOverlay2+1 14

      FOLLOWUP_NAME: MachineOwner

      MODULE_NAME: dxgmms2

      IMAGE_NAME: dxgmms2.sys

      DEBUG_FLR_IMAGE_TIMESTAMP: 58ba5e7e

      FAILURE_BUCKET_ID: X64_0x119_VRF_dxgmms2!VidSchiProcessIsrVSyncMultiP laneOverlay2+114

      BUCKET_ID: X64_0x119_VRF_dxgmms2!VidSchiProcessIsrVSyncMultiP laneOverlay2+114

      Comment

      • Slytod
        PCHF Member
        • Jan 2017
        • 269

        #4
        Hi Phil, thanks for having a gander. Pity that the file wasn’t more informative. There have been updates but as far as I could see nothing related to drivers. As is often the case I’m no longer home until late Monday so I can’t specifically test. But all seems identical to before as far as I can tell. In fact I tried again later, and it crashed a second time.

        I guess it’s looking more and more like a new graphics card is required. I’m unsure how one can affect the GPU temperature since it comes with it’s own cooling fans. That expense will need to be later in the year when the finances seem more balanced.

        Cheers.

        Comment

        • georgeks
          PCHF Member
          • May 2017
          • 335

          #5
          Have you tested ALL your system’s memory?

          Do MemTest, but then press C (configuration) and select Whole Memory Range.

          This solved a few RMA cases at work.

          Comment

          • Slytod
            PCHF Member
            • Jan 2017
            • 269

            #6
            Thanks for the suggestion. I’ll give it a try when I get back.

            Comment

            • phillpower2
              PCHF Administrator
              • Sep 2016
              • 15205

              #7
              Hello Slytod,

              Thanks for the additional assistance georgeks (y)

              May not be around myself on Monday Slytod so will leave you with my canned info below for how to properly test the RAM, we can pick up with other checks on Tuesday if you are available.

              How to physically test your RAM with or without also running Memtest 86, this may take some time to complete but is a more accurate test than running any software while all memory is in the board, please note that you should run at least 7 or 8 passes of Memtest on each stick so best left to run overnight.

              The following checks require the computer case to be opened so take the following safety precautions 1st, disconnect any attached hardware such as the keyboard and printer etc, disconnect the power cord from the wall socket, press the case power button for 10 seconds or so to get rid of any residual charge in the system, remove the side of the case, be sure to take anti static precautions before touching anything inside, you can do this by touching a bare metal part of the case or the PSU.

              Have a pencil and notepad to hand.

              Remove each stick of RAM and blow out the memory slots.

              Insert the first stick of RAM in memory slot one, reconnect the power and in the case of a desktop computer the video to screen cable.

              Power up the computer and see how it goes.

              Make a note of the results.

              Repeat the procedure until the first stick of RAM has been tested in each memory slot and the results written down.

              Remove the first stick of RAM and put it to one side on top of a piece of paper with the number one on it for identification purposes.

              Repeat the procedure with all RAM until each stick has been tested in all slots, the results written down and the sticks identified numerically.

              Please note that some MBs (motherboards) will not boot unless there is RAM in slot one, in this instance check each stick in slot one and then leave a stick in slot one while the sticks are tested in the other slots, be sure to replace the stick in slot one with another so that can also be tested in the other slots.

              Download Memtest 86 (free) from here

              Comment

              • Slytod
                PCHF Member
                • Jan 2017
                • 269

                #8
                It was a longer weekend away than anticipated. As an update, I downloaded what I thought was version 7.3, but when it came to run it claimed to be 4.3.7. Not sure how that happened. Anyway, I’ve not done the memory pulling thing so far but did allow it to run on the full amount and it passed without error. Have to see when I can fit in the more labour intensive option.

                I know. Really really must do the RAM pulling thing soon. Sorry for the delay.

                Comment

                • phillpower2
                  PCHF Administrator
                  • Sep 2016
                  • 15205

                  #9
                  No problem and thanks for letting us know (y)

                  Comment

                  • veeg
                    PCHF Director
                    • Jul 2016
                    • 8977

                    #10
                    Any updates for us?

                    Comment

                    • Slytod
                      PCHF Member
                      • Jan 2017
                      • 269

                      #11
                      Apologies but no. It’s a massive task (not even sure how long each individual test runs for) and what with long weekends away; it’s been on the To Do list every day so far, but at the end of each day I’ve not got around to it. Really must do soon. Maybe today.

                      Comment

                      • veeg
                        PCHF Director
                        • Jul 2016
                        • 8977

                        #12
                        Thanks for the update.

                        Comment

                        • jmarket
                          PCHF Owner
                          • Jan 2015
                          • 7636

                          #13
                          I have marked your thread as Pending until we hear back

                          Comment

                          • Slytod
                            PCHF Member
                            • Jan 2017
                            • 269

                            #14
                            Just starting now. Couple of things. Memtest asks for type of boot. Chose β€˜2’ one pass.
                            Had to connect lead for keyboard to answer options on screen.
                            P6X58D-E indicates only certain configs are acceptable.
                            1 ram has to be in one slot of A1, B1, or C1 only.
                            2 ram in A1 and B1
                            3 ram in A1, B1 and C1
                            4 ram in A1, A2, B1, and C1
                            6 ram in all slots i.e. A1, A2, B1, B2, C1 and C2
                            So I can’t see being able to check everything everywhere. I’ll see what I can do, it’ll probably be wrong. I can check each ram in A1, B1, and C1. We already know it all tested out ok when all was fitted. Unsure the value of the rest.

                            Unsure how long this takes before it stops but it’s 14 minutes into the first test alone so far !
                            Darn. Amused myself surfing on the tablet, and after 55 minutes realised it had done the first test. Hope it ended ages ago and I failed to notice as the single ram tests alone will take 3 x 6 x 55mins = 16.5 hours !

                            Comment

                            • Slytod
                              PCHF Member
                              • Jan 2017
                              • 269

                              #15
                              Weird. That second test suddenly rebooted the PC and started again ?!?!
                              Was about 25 minutes in.

                              Hmmm… 23 mins a pass, then it seems to continue but puts the press escape option on the screen. Even at 23 minutes this is going to be an age.

                              Well, that’s taken all day, and since I could only use a single RAM in 3 of the slots all I’ve achieved is each in turn in each of A1, B1, and C1. Since I couldn’t watch it every moment, and since Memtest doesn’t stop properly for examination at the end, there were 2 or 3 I missed the end of. However at no time did I see the error count be anything other than 0. What I’m unsure of is why Memtest quickly rebooted at the end of the test most of the time, but on 2 or 3 occasions simply stated it had ended but carried on as if it were allowed a second pass. Weird.

                              I don’t think I can face other RAM testing. That was already a marathon session, which found nothing. Previously I’d already tested with all 6 RAM in. It’s presently testing that again. Unsure what next now.

                              BTW ran overnight, 2 passes, with all 6 RAM in place. No errors.

                              Comment

                              Working...