BSODs 0-2 per day while browsing/gaming, new PC

Page 2 of 6 FirstFirst 1234 ... LastLast

  1. Posts : 27
    Windows 10
    Thread Starter
       #11

    Ztruker said:
    Sorry, I was under the impression you had purchased a complete PC. If it's a self-built then you will have to continue debugging it.

    axe0 is the right guy to help you do this.
    Oh. Yeah could have worded this better, my bad.

    I thought you have seen anything that hints to bad hardware. I really really hope debugging will work, but i guess i could RMA parts of it if its bad hardware.

    - - - Updated - - -

    Just had another one. Uploaded the file, in case it helps.
    I'm not sure what exactly it means, but the Message on the BSOD said "IRQL_NOT_LESS_OR_EQUAL" for the last 3. Had different ones before. But the "ntoskrnl.exe+1c10a0" seems to stay the same.
    By the way: I noticed i seem to only get BSODs when i actively do something. Like fullscreening something, loading up into a game/leaving a game or opening another browser tab. I'm not sure if it helps you, but it might.
    Thanks for your time.
      My Computer


  2. Posts : 14,893
    Windows 10 Pro
       #12

    After looking at the logs I figured it was a custom build pc.

    Currently, we're looking at different crashes, typically implying a hardware problem. Unfortunately, with this kind of issues, logs don't really indicate a specific part of the hardware. As I realized this is a custom build I didn't immediately tell you to just RMA the pc, since the parts are usually bought from different companies and as such it is more helpful to pinpoint the hardware causing the crashes.
    Code:
    2019-09-04T22:15:32.695        The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x00000000ffffb781, 0x0000000000000002, 0x0000000000000000, 0xfffff8066c044086). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 78d34a1b-5433-47cd-bffb-13b6c8a44378.
    2019-09-04T19:25:39.137        The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x00000000ffffc47c, 0x0000000000000002, 0x0000000000000000, 0xfffff80573c433d6). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 3851ad1f-556d-4fd4-84d1-d5839034cbab.
    2019-09-04T18:20:03.129        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffb58888a242fc, 0x0000000000000000, 0xfffff80776a4c837, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 187bb410-86dc-4268-b713-c8cadee6ae14.
    2019-09-03T16:21:38.887        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x000000000000001d, 0xfffff80260e66e70, 0xfffff80260e66dc8, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 1dbac52d-77fa-488e-8a96-783b84198bd2.
    2019-09-03T12:29:37.057        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x000000000000001d, 0xffffef0c99b8bfa0, 0xffffef0c99b8bef8, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: af6d8b54-a28b-45d3-bc96-831f94e94d2b.
    2019-08-30T23:34:11.966        The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x00000000ffffaf79, 0x0000000000000002, 0x0000000000000000, 0xfffff8051fc42b74). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 7b5b5a03-6930-4c6e-8222-519afe31b9a7.
    2019-08-30T22:37:11.765        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x000000000000001d, 0xfffffb0671291f60, 0xfffffb0671291eb8, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: e8091c81-5c6f-4dec-934f-221c0ad6d547.
    2019-08-30T22:16:59.887        The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80549a42cb6, 0xffffcd8013bdf930, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: ed88bcb3-ba0f-4a88-a29b-9035c5aef75b.
    2019-08-30T21:25:13.024        The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff80766641900, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 75b518cf-2a78-460d-a886-7403311ac024.
    2019-08-30T17:55:57.541        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x000000000000001d, 0xffff92885c5dfdb0, 0xffff92885c5dfd08, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: f01a80cd-6c42-4174-81b5-6ae492380662.

    Do you happen to have spare parts, or is it possible for you to borrow hardware from someone else or let someone else test parts in their system? Asking this, because that will speed things up significantly.

    My current thoughts on the matter, although there are different crashes in most of them the graphics drivers seem to be somehow involved. This makes me suspect a faulty graphics card, but since you don't have an integrated GPU in the CPU the best way to test is using the GPU in a different system.
    Furthermore, I would also suggest that you do the same for the RAM, if possible, because of the memory (de)allocations that happen in between the crashes and the GPU's involvement as well.
    Code:
    Bugcheck code 0000000A
    Arguments 00000000`ffffb781 00000000`00000002 00000000`00000000 fffff806`6c044086
    Debug session time: Wed Sep  4 22:14:25.978 2019 (UTC + 2:00)
    System Uptime: 0 days 1:08:49.661
    0: kd> k
     # Child-SP          RetAddr           Call Site
    00 fffff806`72266db8 fffff806`6c1d2ee9 nt!KeBugCheckEx
    01 fffff806`72266dc0 fffff806`6c1cf22b nt!KiBugCheckDispatch+0x69
    02 fffff806`72266f00 fffff806`6c044086 nt!KiPageFault+0x46b
    03 fffff806`72267090 fffff806`6c0460ad nt!RtlpHpVsContextFree+0x3d6
    04 fffff806`72267130 fffff806`6c36e0a9 nt!ExFreeHeapPool+0x56d
    05 fffff806`72267250 fffff806`7ff0777e nt!ExFreePool+0x9
    06 fffff806`72267280 fffff806`7ff070fe dxgmms2!VidSchiProcessCompletedQueuePacketInternal+0x2be
    07 fffff806`72267430 fffff806`7ff0479b dxgmms2!VidSchiProcessDpcCompletedPacket+0x6ee
    08 fffff806`72267590 fffff806`7a856761 dxgmms2!VidSchDdiNotifyDpc+0x22b
    09 fffff806`72267640 fffff806`8012533f dxgkrnl!DxgNotifyDpcCB+0x91
    0a fffff806`722676f0 ffffb789`b6e72340 atikmdag+0xf533f
    0b fffff806`722676f8 ffffb789`b6e69f80 0xffffb789`b6e72340
    0c fffff806`72267700 ffffb789`b6e72340 0xffffb789`b6e69f80
    0d fffff806`72267708 00000000`00000060 0xffffb789`b6e72340
    0e fffff806`72267710 ffffb789`b6ccd000 0x60
    0f fffff806`72267718 fffff806`80127c0f 0xffffb789`b6ccd000
    10 fffff806`72267720 ffffb789`b6e69f80 atikmdag+0xf7c0f
    11 fffff806`72267728 ffffb789`b6cf7958 0xffffb789`b6e69f80
    12 fffff806`72267730 ffffb789`b6e72340 0xffffb789`b6cf7958
    13 fffff806`72267738 ffffb789`b6ccd000 0xffffb789`b6e72340
    14 fffff806`72267740 00000000`00000000 0xffffb789`b6ccd000
    
    Bugcheck code 00000139
    Arguments 00000000`0000001d fffff802`60e66e70 fffff802`60e66dc8 00000000`00000000
    Debug session time: Tue Sep  3 16:14:03.809 2019 (UTC + 2:00)
    System Uptime: 0 days 3:12:30.491
    0: kd> k
     # Child-SP          RetAddr           Call Site
    00 fffff802`60e66b48 fffff802`5c7d2ee9 nt!KeBugCheckEx
    01 fffff802`60e66b50 fffff802`5c7d3310 nt!KiBugCheckDispatch+0x69
    02 fffff802`60e66c90 fffff802`5c7d16a5 nt!KiFastFailDispatch+0xd0
    03 fffff802`60e66e70 fffff802`5c7fa745 nt!KiRaiseSecurityCheckFailure+0x325
    04 fffff802`60e67008 fffff802`5c644453 nt!RtlRbRemoveNode+0x1b6145
    05 fffff802`60e67020 fffff802`5c643e3a nt!RtlpHpVsChunkCoalesce+0x183
    06 fffff802`60e67090 fffff802`5c6460ad nt!RtlpHpVsContextFree+0x18a
    07 fffff802`60e67130 fffff802`5c96e0a9 nt!ExFreeHeapPool+0x56d
    08 fffff802`60e67250 fffff802`6ea1777e nt!ExFreePool+0x9
    09 fffff802`60e67280 fffff802`6ea170fe dxgmms2!VidSchiProcessCompletedQueuePacketInternal+0x2be
    0a fffff802`60e67430 fffff802`6ea1479b dxgmms2!VidSchiProcessDpcCompletedPacket+0x6ee
    0b fffff802`60e67590 fffff802`69406761 dxgmms2!VidSchDdiNotifyDpc+0x22b
    0c fffff802`60e67640 fffff802`6edc533f dxgkrnl!DxgNotifyDpcCB+0x91
    0d fffff802`60e676f0 ffffd58d`b3f96ef0 atikmdag+0xf533f
    0e fffff802`60e676f8 ffffd58d`b3f7b2d0 0xffffd58d`b3f96ef0
    0f fffff802`60e67700 ffffd58d`b3f96ef0 0xffffd58d`b3f7b2d0
    10 fffff802`60e67708 ffffd58d`00000060 0xffffd58d`b3f96ef0
    11 fffff802`60e67710 ffffd58d`b3ee8000 0xffffd58d`00000060
    12 fffff802`60e67718 fffff802`6edc7c0f 0xffffd58d`b3ee8000
    13 fffff802`60e67720 ffffd58d`b3f7b2d0 atikmdag+0xf7c0f
    14 fffff802`60e67728 ffffd58d`b3f5b958 0xffffd58d`b3f7b2d0
    15 fffff802`60e67730 ffffd58d`b3f96ef0 0xffffd58d`b3f5b958
    16 fffff802`60e67738 ffffd58d`b3ee8000 0xffffd58d`b3f96ef0
    17 fffff802`60e67740 00000000`00000000 0xffffd58d`b3ee8000
    
    Bugcheck code 00000139
    Arguments 00000000`0000001d ffffef0c`99b8bfa0 ffffef0c`99b8bef8 00000000`00000000
    Debug session time: Tue Sep  3 12:28:35.926 2019 (UTC + 2:00)
    System Uptime: 0 days 1:08:30.608
    6: kd> k
     # Child-SP          RetAddr           Call Site
    00 ffffef0c`99b8bc78 fffff806`6f1d2ee9 nt!KeBugCheckEx
    01 ffffef0c`99b8bc80 fffff806`6f1d3310 nt!KiBugCheckDispatch+0x69
    02 ffffef0c`99b8bdc0 fffff806`6f1d16a5 nt!KiFastFailDispatch+0xd0
    03 ffffef0c`99b8bfa0 fffff806`6f1fa745 nt!KiRaiseSecurityCheckFailure+0x325
    04 ffffef0c`99b8c138 fffff806`6f042e78 nt!RtlRbRemoveNode+0x1b6145
    05 ffffef0c`99b8c150 fffff806`6f042d39 nt!RtlpHpVsChunkSplit+0x48
    06 ffffef0c`99b8c220 fffff806`6f11030d nt!RtlpHpVsContextAllocateInternal+0x3c9
    07 ffffef0c`99b8c290 fffff806`6f03301b nt!RtlpHpVsContextMultiAlloc+0x69
    08 ffffef0c`99b8c310 fffff806`6f36e06d nt!ExAllocateHeapPool+0x95b
    09 ffffef0c`99b8c450 fffff806`6f11e7af nt!ExAllocatePoolWithTag+0x5d
    0a ffffef0c`99b8c4a0 fffff806`8284a534 nt!MmCreateMdl+0x6f
    0b ffffef0c`99b8c4d0 fffff806`8284a272 dxgmms2!VidMmiAllocateMdl+0x24
    0c ffffef0c`99b8c500 fffff806`8286482d dxgmms2!VidMmiProbeAndLockAllocation+0xa6
    0d ffffef0c`99b8c5a0 fffff806`8284c99f dxgmms2!VIDMM_APERTURE_SEGMENT::CommitResource+0x11d
    0e ffffef0c`99b8c660 fffff806`82857eb2 dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x1ef
    0f ffffef0c`99b8c770 fffff806`82867da4 dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0x862
    10 ffffef0c`99b8c9e0 fffff806`82866ee9 dxgmms2!VIDMM_WORKER_THREAD::Run+0xea4
    11 ffffef0c`99b8cbe0 fffff806`6f12a715 dxgmms2!VidMmWorkerThreadProc+0x9
    12 ffffef0c`99b8cc10 fffff806`6f1c86ea nt!PspSystemThreadStartup+0x55
    13 ffffef0c`99b8cc60 00000000`00000000 nt!KiStartSystemThread+0x2a
    
    Bugcheck code 00000050
    Arguments ffffb588`88a242fc 00000000`00000000 fffff807`76a4c837 00000000`00000002
    Debug session time: Wed Sep  4 18:17:43.756 2019 (UTC + 2:00)
    System Uptime: 0 days 5:27:36.433
    11: kd> k
     # Child-SP          RetAddr           Call Site
    00 fffff901`9d421bd8 fffff807`623e31d6 nt!KeBugCheckEx
    01 fffff901`9d421be0 fffff807`622730bf nt!MiSystemFault+0x1d64a6
    02 fffff901`9d421ce0 fffff807`623cf120 nt!MmAccessFault+0x34f
    03 fffff901`9d421e80 fffff807`76a4c837 nt!KiPageFault+0x360
    04 fffff901`9d422010 ffffb588`18d029e4 atikmdag+0x12bc837
    05 fffff901`9d422018 ffffb588`1f6d6601 0xffffb588`18d029e4
    06 fffff901`9d422020 00000000`00000000 0xffffb588`1f6d6601
    
    Bugcheck code 0000000A
    Arguments 00000000`ffffc47c 00000000`00000002 00000000`00000000 fffff805`73c433d6
    Debug session time: Wed Sep  4 19:24:25.934 2019 (UTC + 2:00)
    System Uptime: 0 days 0:38:06.614
    9: kd> k
     # Child-SP          RetAddr           Call Site
    00 ffff860e`a0d16de8 fffff805`73dd2ee9 nt!KeBugCheckEx
    01 ffff860e`a0d16df0 fffff805`73dcf22b nt!KiBugCheckDispatch+0x69
    02 ffff860e`a0d16f30 fffff805`73c433d6 nt!KiPageFault+0x46b
    03 ffff860e`a0d170c0 fffff805`73c42d39 nt!RtlpHpVsChunkSplit+0x5a6
    04 ffff860e`a0d17190 fffff805`73c332ce nt!RtlpHpVsContextAllocateInternal+0x3c9
    05 ffff860e`a0d17200 fffff805`73f6e06d nt!ExAllocateHeapPool+0xc0e
    06 ffff860e`a0d17340 fffff805`73c29c90 nt!ExAllocatePoolWithTag+0x5d
    07 ffff860e`a0d17390 fffff805`82dd3532 nt!ExAllocatePoolWithQuotaTag+0x60
    08 ffff860e`a0d17410 fffff805`82dd2042 nsiproxy!NsippProbeAndAllocateParameters+0x7a2
    09 ffff860e`a0d175e0 fffff805`82dd26f7 nsiproxy!NsippGetAllParameters+0x1a2
    0a ffff860e`a0d177d0 fffff805`73c31f39 nsiproxy!NsippDispatch+0xd7
    0b ffff860e`a0d17820 fffff805`741e8275 nt!IofCallDriver+0x59
    0c ffff860e`a0d17860 fffff805`741e8080 nt!IopSynchronousServiceTail+0x1a5
    0d ffff860e`a0d17900 fffff805`741e7456 nt!IopXxxControlFile+0xc10
    0e ffff860e`a0d17a20 fffff805`73dd2918 nt!NtDeviceIoControlFile+0x56
    0f ffff860e`a0d17a90 00007ffa`e6f3c1b4 nt!KiSystemServiceCopyEnd+0x28
    10 0000004e`d867ee18 00000000`00000000 0x00007ffa`e6f3c1b4
      My Computers


  3. Posts : 27
    Windows 10
    Thread Starter
       #13

    Thank you so much for your time already.
    Sadly I have already sold my old setup, so there is no way for me to test out different Setups right now.
    But since i life in Berlin i might be able to find a fitting shop that could test my GPU & RAM? What would i be looking for here?
    But then again i might as well just RMA the GPU and RAM directly? Or are we not sure if it's the RAM & GPU? (Update: I'm to dumb to read, and we are not sure. Might RMA everything? But that doesn't sound too good)

    Thanks again for your help already.
      My Computer


  4. Posts : 14,893
    Windows 10 Pro
       #14

    What I know of the warranty requirements of my pc, a part has to be actually faulty to be applicable. If during their tests no issue is found, you're charged for the cost.

    Don't know if that's different for you.
      My Computers


  5. Posts : 27
    Windows 10
    Thread Starter
       #15

    Yeah, i just called them and they said i should make sure to find out which parts are faulty.

    He also told me to change the PCIExpress Gen in the BIOS because the Mainboard and the GPU might have problems if i don't do so. I've done that now, let's see if it changes anything.

    Should i try using only 1 of the RAM Sticks at a time and see if i still get BSODs?
    What are the next steps that i should do now?
      My Computer


  6. Posts : 14,893
    Windows 10 Pro
       #16

    Try with the sticks seated in different slots and see if you still get BSODs.
      My Computers


  7. Posts : 27
    Windows 10
    Thread Starter
       #17

    axe0 said:
    Try with the sticks seated in different slots and see if you still get BSODs.
    Swapped them already on monday. And when i try to put them in the 2 unused slots, my pc won't even start and will tell me that i should swap them into the other slots.
    Do i just swap them again?
      My Computer


  8. Posts : 14,893
    Windows 10 Pro
       #18

    nomic96 said:
    Swapped them already on monday. And when i try to put them in the 2 unused slots, my pc won't even start and will tell me that i should swap them into the other slots.
    Do i just swap them again?
    That's a bit unexpected and is unfortunately almost confirming a worse case scenario I had in mind, the motherboard may need to be replaced.
      My Computers


  9. Posts : 27
    Windows 10
    Thread Starter
       #19

    axe0 said:
    That's a bit unexpected and is unfortunately almost confirming a worse case scenario I had in mind, the motherboard may need to be replaced.
    Eh. I may have worded that poorly. I get a BIOS Message when i put them in the other 2 Slots saying that i should swap them and restart. Isn't that normal because the Motherboard has prefered slots to put them in?
    I can test that again and make a photo of the message if you want me to.
      My Computer


  10. Posts : 14,893
    Windows 10 Pro
       #20

    Please make a photo of it.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 00:35.
Find Us




Windows 10 Forums