Page 2 of 3 FirstFirst 123 LastLast
  1.    26 Apr 2017 #11
    Join Date : Nov 2015
    Posts : 2,867
    64bit Win 10 Pro ver 1709 Build 16299.64

    Let us know how you get on, I'll pick up the thread while @axe0 is away.
      My ComputersSystem Spec
  2.    26 Apr 2017 #12
    Join Date : Apr 2017
    Posts : 14
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    Ran MemTest86+ overnight. No errors after 13 passes (see image).

    I've tried swapping both GPUs, using one at a time, testing against 3DMark. They both result in 3DMark errors and then BSOD with Memory_Management at ntoskrnl.
      My ComputerSystem Spec
  3.    26 Apr 2017 #13
    Join Date : Nov 2015
    Posts : 2,867
    64bit Win 10 Pro ver 1709 Build 16299.64

    Please post a new set of log files as you have had some new BSOD events. Thanks
      My ComputersSystem Spec
  4.    26 Apr 2017 #14
    Join Date : Apr 2017
    Posts : 14
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    I'll have to do that this evening.
      My ComputerSystem Spec
  5.    26 Apr 2017 #15
    Join Date : Apr 2017
    Posts : 14
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    Attached minidumps collect from this latest install of Windows.
      My ComputerSystem Spec
  6.    26 Apr 2017 #16
    Join Date : Nov 2015
    Posts : 2,867
    64bit Win 10 Pro ver 1709 Build 16299.64

    The dumps continue to show memory corruption but as you have tested your RAM I am inclined to think there must be a driver which is causing this. There is a method below which might reveal if there are any faulty drivers on your system. Perform this at your own risk and make sure you follow all the warnings in case you have trouble getting out of the driver verifier mode.




    BSOD on Windows 10 with various errors at random times Diagnostic Test BSOD on Windows 10 with various errors at random times
     DRIVER VERIFIER

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please read and run driver verifier.

    If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My ComputersSystem Spec
  7.    27 Apr 2017 #17
    Join Date : Apr 2017
    Posts : 14
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    Verifier has been running for almost 24 hours and no BSOD. I even double checked to make sure it was in fact running.

    I started an RMA process for the GPUs. I'm going to try swapping RAM sticks and running 3DMark with each GPU individually. All I can think is that this is hardware now. I wish there was a way to know for sure.
      My ComputerSystem Spec
  8.    27 Apr 2017 #18
    Join Date : Nov 2015
    Posts : 2,867
    64bit Win 10 Pro ver 1709 Build 16299.64

    You can run the test for up to 48 hours. Test using 3DMark without GPUs if you have on-board graphics.
      My ComputersSystem Spec
  9.    28 Apr 2017 #19
    Join Date : Apr 2017
    Posts : 14
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    Completed Driver Verifier with no errors.

    Tonight I retested each GPU individually with 3DMark and only one stick of RAM installed.

    GPU #1 passed all of the tests. I ran 3DMark three times as I couldn't believe it.

    GPU #2 on the first pass, made it to the final CPU test and then the machine froze up. I rebooted and ran 3DMark again. The card failed during loading of the second test and I received a MEMORY_MANAGEMENT BSOD. One final time to confirm and again the card failed at the second test with the same BSOD.

    I'm RMA'ing the card with EVGA.
      My ComputerSystem Spec
  10.    07 May 2017 #20
    Join Date : Apr 2017
    Posts : 14
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    Well I'm not out of the woods yet. System is more stable than its been, but I'm still wondering if this one GPU is bad or something else. I'm still waiting on the RMA'd GPU to return. Once that does, I can swap them and see if I'm still getting BSODs.

    Just received several BSODs during a game. And now 3DMark is failing at the CPU test. It doesn't BSOD, but the test freezes up at about 10 seconds or so in. The CPU test occurs after 3 GPU tests.


    These are the last two BSODs:

    ==================================================
    Dump File : 050717-4937-01.dmp
    Crash Time : 5/7/2017 11:28:45 AM
    Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x1000007e
    Parameter 1 : ffffffff`c0000005
    Parameter 2 : fffff802`0f2fcc9e
    Parameter 3 : ffffb381`2c435cd8
    Parameter 4 : ffffb381`2c435510
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+63c9e
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 10.0.15063.250 (WinBuild.160101.0800)
    Processor : x64
    Crash Address : ntoskrnl.exe+63c9e
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\050717-4937-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 15063
    Dump File Size : 309,217
    Dump File Time : 5/7/2017 11:29:45 AM
    ==================================================

    ==================================================
    Dump File : 050717-4734-01.dmp
    Crash Time : 5/7/2017 11:15:17 AM
    Bug Check String : SYSTEM_SERVICE_EXCEPTION
    Bug Check Code : 0x0000003b
    Parameter 1 : 00000000`c0000005
    Parameter 2 : fffff801`ce04f91f
    Parameter 3 : ffffe780`93525c30
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+16bfd0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 10.0.15063.250 (WinBuild.160101.0800)
    Processor : x64
    Crash Address : ntoskrnl.exe+16bfd0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\050717-4734-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 15063
    Dump File Size : 312,105
    Dump File Time : 5/7/2017 11:15:57 AM
    ==================================================
      My ComputerSystem Spec

 
Page 2 of 3 FirstFirst 123 LastLast


Similar Threads
Thread Forum
BSOD at random times after Windows refresh
Refreshed windows about close to a week ago after my system seemed to be running slow. have gotten 3 BSOD in about a week and wanted to see if anyone could give me an idea of what is happening. The BSOD has happened seemingly randomly, I monitor...
BSOD Crashes and Debugging
Windows 10: BSOD at random times, SYSTEM_SERVICE_EXCEPTION (Netio.SYS)
Hi everyone, I have been getting random BSOD lately especially yesterday which was crazy every few minutes and also BSOD during the login screen. Attached is my log files. it suddenly happened starting yesterday or day before and no clue what...
BSOD Crashes and Debugging
BSOD at very random times, no specific times.
Hi guys, I keep on getting BSOD screens when using my laptop. It is very random, sometimes it happens whilst I am working in Adobe Photoshop or Illustrator or even just when I am browsing the web. At first I thought it might be the display...
BSOD Crashes and Debugging
Solved Random BSOD in random times
Hi, I'm really hoping to solve the problem since it's starting to distract seriously. I think since early summer BSODs been flashing now and then and now more and more often. Naturally I've tried memory solutions found online for memory related...
BSOD Crashes and Debugging
BSOD at random times doing random things.
Hi, I am getting BSODs at random times, while doing different things each time. Been getting them for 5 days trying to narrow down what could be causing it. Searching lead me here. I did the posting instructions. Also did sfc/scannow 2 times that...
BSOD Crashes and Debugging
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 08:20.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums