Frequent BSoDs

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • jmarket
    PCHF Owner
    • Jan 2015
    • 7635

    #16
    Most of your logs are indicating an IRQL_NOT_LESS_OR_EQUAL or is referring to a fault in dxgmms1.sys, which indicates a hardware conflict. Can you post a log of Speccy for me so I can analyze your hardware configuration?

    Comment

    • ZephyrCorsair
      PCHF Member
      • Sep 2016
      • 25

      #17
      Didn’t I already do that?

      Comment

      • Malnutrition
        PCHF Moderator
        • Jul 2016
        • 7041

        #18
        Speccy Scan.

        [ul]
        [li]Please go here and download Speccy.[/li][li]Install and run the program.[/li][li]Upon Completion:[/li][li]Hit File[/li][li]Publish Snap Shot[/li][li]A link will appear, post that link.[/li][/ul]

        Comment

        • Malnutrition
          PCHF Moderator
          • Jul 2016
          • 7041

          #19
          Code:
          [HR][/HR][LIST][*][CODE]                                                                        *
          [*]
          Code:
                             Bugcheck Analysis                                    *
          [*]
          Code:
                                                                                  *
          [/LIST]


          SYSTEM_SERVICE_EXCEPTION (3b)
          An exception happened while executing a system service routine.
          Arguments:
          Arg1: 00000000c0000005, Exception code that caused the bugcheck
          Arg2: fffff800100ae1f8, Address of the instruction which caused the bugcheck
          Arg3: ffffd00024015780, Address of the context record for the exception that caused the bugcheck
          Arg4: 0000000000000000, zero.
          [HEADING=1]Debugging Details:[/HEADING]
          TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

          EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at β€œ0x%08lx” referenced memory at β€œ0x%08lx”. The memory could not be β€œ%s”.

          FAULTING_IP:
          nt!ExAllocatePoolWithTag+518
          fffff800`100ae1f8 c9 leave

          CONTEXT: ffffd00024015780 – (.cxr 0xffffd00024015780)
          rax=0000000000000040 rbx=ffffc0017a2f9000 rcx=0000000000000000
          rdx=ffffc0017a2f9c00 rsi=000000004b677844 rdi=0000000000000001
          rip=fffff800100ae1f8 rsp=ffffd000240161a0 rbp=00000000000000c0
          r8=0000000000000001 r9=0000000000000001 r10=7ffff80010178668
          r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
          r14=0000000000000000 r15=ffffd00024016720
          iopl=0 nv up ei pl nz na pe nc
          cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
          nt!ExAllocatePoolWithTag+0x518:
          fffff800`100ae1f8 c9 leave
          Resetting default scope

          CUSTOMER_CRASH_COUNT: 1

          DEFAULT_BUCKET_ID: CODE_CORRUPTION

          BUGCHECK_STR: 0x3B

          PROCESS_NAME: Battle.net Hel

          CURRENT_IRQL: 0

          LAST_CONTROL_TRANSFER: from fffff80114c90974 to fffff800100ae1f8

          STACK_TEXT:
          ffffd000[ICODE]240161a0 fffff801[/ICODE]14c90974 : 00000000[ICODE]00000000 00000000[/ICODE]00001000 ffffd000[ICODE]240169e0 ffffc001[/ICODE]7a2f9c00 : nt!ExAllocatePoolWithTag+0x518
          ffffd000[ICODE]24016280 fffff801[/ICODE]14cb5957 : ffffe001[ICODE]5a96e520 ffffd000[/ICODE]24016b80 00000000[ICODE]00000000 ffffc001[/ICODE]6edaa400 : dxgkrnl!DXGDEVICE::CreateAllocation+0x854
          ffffd000[ICODE]24016950 fffff800[/ICODE]0ffca1a3 : ffffe001[ICODE]5e1a9080 00000000[/ICODE]00fbe001 00000000[ICODE]00000000 ffffc001[/ICODE]6edaa4c0 : dxgkrnl!DxgkCreateAllocation+0x697
          ffffd000[ICODE]24016b00 00000000[/ICODE]70f36d04 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : nt!KiSystemServiceCopyEnd+0x13
          00000000[ICODE]00fbdfd8 00000000[/ICODE]00000000 : 00000000[ICODE]00000000 00000000[/ICODE]00000000 00000000[ICODE]00000000 00000000[/ICODE]00000000 : 0x70f36d04

          MODULE_NAME: memory_corruption

          IMAGE_NAME: memory_corruption

          FOLLOWUP_NAME: memory_corruption

          DEBUG_FLR_IMAGE_TIMESTAMP: 0

          MEMORY_CORRUPTOR: ONE_BIT

          STACK_COMMAND: .cxr 0xffffd00024015780 ; kb

          FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

          BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

          Followup: memory_corruption
          ---------[/code]

          Comment

          • ZephyrCorsair
            PCHF Member
            • Sep 2016
            • 25

            #20

            Comment

            • ZephyrCorsair
              PCHF Member
              • Sep 2016
              • 25

              #21
              I’m guessing the screenshot i provided in the original post of the thread wasn’t enough then?

              Comment

              • Malnutrition
                PCHF Moderator
                • Jul 2016
                • 7041

                #22
                jmarket Speccy log posted per your request.

                Comment

                • Malnutrition
                  PCHF Moderator
                  • Jul 2016
                  • 7041

                  #23
                  Sorry about the delay, at this point while you await someone to respond to this thread, you could create a new thread in the malware area to check if there is any infection. I have sent out a message to the BSOD people to have a look at your thread.

                  Comment

                  • ZephyrCorsair
                    PCHF Member
                    • Sep 2016
                    • 25

                    #24
                    It’s not malware, I reinstalled windows and everything and I’ve run a million malware checks before that. It’s got to be something in the hard ware or maybe drive related. I’m not that good with computers but it cant be malware if even a clean slate computer still crashes.

                    Comment

                    • Malnutrition
                      PCHF Moderator
                      • Jul 2016
                      • 7041

                      #25
                      I think it best to test your Ram Modules. Here is a Full Tutorial video I was able to grab from Youtube. Let us know the outcome…

                      [MEDIA=youtube]NaHL9usaM4Q[/MEDIA]

                      Comment

                      • ZephyrCorsair
                        PCHF Member
                        • Sep 2016
                        • 25

                        #26
                        A friend of mine talked about the watt of my PSU or something, that maybe the problem was my PSU. But sure, I’ll try that.

                        Comment

                        • Rustys
                          PCHF Member
                          • Jul 2016
                          • 7862

                          #27
                          Since you brought it up what is the Watts for the PSU including the Make, Model and age?

                          Comment

                          • jmarket
                            PCHF Owner
                            • Jan 2015
                            • 7635

                            #28
                            Sorry about the delay. Had a real busy few days.

                            Your graphics card is drawing 200W. What PSU do you have? Brand, wattage?

                            Faulty RAM sticks will cause an excessive amount of BSODs as the data collides and can’t be written properly. I would test the RAM sticks with MemTest86+ before anything else.

                            Comment

                            • ZephyrCorsair
                              PCHF Member
                              • Sep 2016
                              • 25

                              #29
                              Originally posted by Malnutrition
                              I think it best to test your Ram Modules. Here is a Full Tutorial video I was able to grab from Youtube. Let us know the outcome…

                              [MEDIA=youtube]NaHL9usaM4Q[/MEDIA]
                              I seem to get to a different BIOS screen, I assume it’s because I use win10. What do I do?

                              Comment

                              • Rustys
                                PCHF Member
                                • Jul 2016
                                • 7862

                                #30
                                Not all BIOS screens will display the same.

                                How are you attempting to run Memtest86 USB or DVD?

                                All that you need to do is set that to boot first. Then insert the software and allow it to boot and test the RAM.

                                Let it test it several times just once may give you a false reading.

                                Comment

                                Working...