Newly DIY Built PC with BSOD Issues

Page 1 of 2 12 LastLast

  1. Posts : 10
    win 10 home
       #1

    Newly DIY Built PC with BSOD Issues


    My PC was only built about a week ago, and has many different BSODs throughout the week.

    I have managed to solve quite a few of them, and currently these are the ones that are still bugging me, mainly ntoskrnl.exe

    I have tried memtest and windows memory diagnostic tool to check for ram issues but they both passed.
      My Computer


  2. Posts : 654
    windows 10 Pro
       #2

    Could you also run your system in normal mode and make a new zip and upload it, the current one is from safemode.

    Anyway the dumpfiles are
    Code:
      
    BugCheck 1000007E, {ffffffffc0000005, fffff800df98484d, ffff9880ce4e7ef8, ffff9880ce4e7720}
    
    Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpCallDriver+7c )
    This points to HID= Human interface devices.( mouse keyboard, gamecontrollers, etc.)

    In the msinfo32
    Unknown USB Device (Device Descriptor Request Failed) USB\VID_0000&PID_0002\6&A9BF448&0&1 This device is working properly.
    In the WER= windows error report
    +++ WER5 +++:
    Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_0BDA_DEV_5411_RE V_0123, type 0

    Event Name: LiveKernelEvent

    Response: Not available

    Cab Id: 93f16d30-0c2a-4068-bb04-b47586805567
    It looks that a connected HID device( probably usb) could be the cause.

    Use/start your system as bare as possible only with mouse and keyboard and see if this stops the BSOD.
    Then connect one by one the other devices and maybe you can find the guilty one.
      My Computer


  3. Posts : 10
    win 10 home
    Thread Starter
       #3

    Is is this now?
      My Computer


  4. Posts : 10
    win 10 home
    Thread Starter
       #4

    I just got a few more bsods heres an updated one
      My Computer


  5. Posts : 654
    windows 10 Pro
       #5

    All the dumpfiles mention memory corruption.

    Did you test your memory according to this tutorial.
    How to run "Memtest"
    MemTest86+ - Test RAM - Windows 10 Tutorials
    Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory Diagnostic Tool

    You can stop the test even if a single error is found during the test.
    Otherwise continue the test for 8-10 passes and post a screenshot with next reply.
    8 passes is the recommended bare minimum but more passes will give better result.
      My Computer


  6. Posts : 10
    win 10 home
    Thread Starter
       #6

    I tried memtest86 (no +) on 1 of the sticks which i think is the functional one, and it gave me this bsod ONLY when i try to stream to twitch and play overwatch, and that happens about 15mins in.

    I ran it overnight and it got 8 passes, so im not sure if this bsod is still related to memory corruption.

    I am going to try the other stick overnight and see if it is the actual faulty one.

    Here is the latest one.
      My Computer


  7. Posts : 654
    windows 10 Pro
       #7

    The last dumpfile is
    Code:
       Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff801a231ff5e, ffff99013dde0a10, 0}
    
    Probably caused by : hardware ( nt!FsRtlpOplockFsctrlInternal+6 )
    
    Followup: MachineOwner
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff801a231ff5e, Address of the instruction which caused the bugcheck
    Arg3: ffff99013dde0a10, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%p verwijst naar geheugen op 0x%p. Het geheugen kan niet worden %s.
    
    FAULTING_IP: 
    nt!FsRtlpOplockFsctrlInternal+6
    fffff801`a231ff5e 20448940        and     byte ptr [rcx+rcx*4+40h],al
    
    CONTEXT:  ffff99013dde0a10 -- (.cxr 0xffff99013dde0a10;r)
    rax=ffff99013dde1428 rbx=0000000000000000 rcx=ffffd789f3879928
    rdx=ffff880e24008b80 rsi=0000000000090240 rdi=ffffd789f38798d0
    rip=fffff801a231ff5e rsp=ffff99013dde1428 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=ffff99013dde14c8
    r11=ffff99013dde1440 r12=ffffd789f3879790 r13=0000000000090268
    r14=ffff880e2aeb6b58 r15=0000000000000001
    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!FsRtlpOplockFsctrlInternal+0x6:
    fffff801`a231ff5e 20448940        and     byte ptr [rcx+rcx*4+40h],al ds:002b:ffff35b1`c1a5fe08=??
    Last set context:
    rax=ffff99013dde1428 rbx=0000000000000000 rcx=ffffd789f3879928
    rdx=ffff880e24008b80 rsi=0000000000090240 rdi=ffffd789f38798d0
    rip=fffff801a231ff5e rsp=ffff99013dde1428 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=ffff99013dde14c8
    r11=ffff99013dde1440 r12=ffffd789f3879790 r13=0000000000090268
    r14=ffff880e2aeb6b58 r15=0000000000000001
    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!FsRtlpOplockFsctrlInternal+0x6:
    fffff801`a231ff5e 20448940        and     byte ptr [rcx+rcx*4+40h],al ds:002b:ffff35b1`c1a5fe08=??
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  MsMpEng.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
    
    MISALIGNED_IP: 
    nt!FsRtlpOplockFsctrlInternal+6
    fffff801`a231ff5e 20448940        and     byte ptr [rcx+rcx*4+40h],al
    
    LAST_CONTROL_TRANSFER:  from fffff801a231ff51 to fffff801a231ff5e
    
    STACK_TEXT:  
    ffff9901`3dde1428 fffff801`a231ff51 : 00000000`00000000 ffff880e`2b6755f0 00000000`00000001 ffff880e`2aeb6b58 : nt!FsRtlpOplockFsctrlInternal+0x6
    ffff9901`3dde1430 fffff808`0e0bc5d1 : ffff880e`2aeb6b58 ffffd789`f3879790 00000000`00000000 00000000`00090240 : nt!FsRtlOplockFsctrlEx+0x11
    ffff9901`3dde1470 fffff808`0e0f46bb : ffff880e`2aeb6b58 ffff880e`24008b80 ffff880e`00000000 ffff880e`00000000 : NTFS!NtfsOplockRequest+0x20d
    ffff9901`3dde1520 fffff808`0e0f4c37 : ffff880e`2aeb6b58 ffff880e`24008b80 ffff880e`24008b80 00000000`00000000 : NTFS!NtfsUserFsRequest+0x25b
    ffff9901`3dde15a0 fffff808`0d405206 : ffff880e`2c447c00 fffff808`0d403386 ffff880e`24008b80 ffff880e`24008f68 : NTFS!NtfsFsdFileSystemControl+0x117
    ffff9901`3dde16b0 fffff808`0d4335a0 : ffff880e`22ee17c0 00000000`00000040 000000ad`caa7f400 ffff880e`248aec00 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a6
    ffff9901`3dde1740 fffff801`a2318cd0 : ffff880e`2b675650 00000000`00000002 00000000`00000000 ffff880e`00000000 : FLTMGR!FltpFsControl+0x110
    ffff9901`3dde17a0 fffff801`a2317bb4 : ffff9901`00000001 ffff880e`2b675604 00000000`00000000 ffff9901`3dde1b00 : nt!IopSynchronousServiceTail+0x1a0
    ffff9901`3dde1860 fffff801`a232524a : 00000000`00000000 00000000`00000000 00000000`00000000 00007ffc`7bbec668 : nt!IopXxxControlFile+0x674
    ffff9901`3dde19a0 fffff801`a1fdf393 : 00000000`00000102 00000000`00000001 00000000`00000000 ffff880e`00000002 : nt!NtFsControlFile+0x56
    ffff9901`3dde1a10 00007ffc`8e3467f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000ad`caa7f368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`8e3467f4
    Advice also test your Harddisk and SSD.
      My Computer


  8. Posts : 10
    win 10 home
    Thread Starter
       #8

    So now i memtested both sticks and they both got above 8 passes, i have no clue what is actually wrong now.
      My Computer


  9. Posts : 10
    win 10 home
    Thread Starter
       #9

    Ok so im now using both the sticks of ram and they only give me this error time to time, this should be the final error if im right
      My Computer


  10. Posts : 654
    windows 10 Pro
       #10


    So now i memtested both sticks and they both got above 8 passes, i have no clue what is actually wrong now.
    Where there any errors when you tested your memory with Memtest 86+.
    Any red lines in the test.
    Could you make a foto and upload it.
      My Computer


 

  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 19:30.
Find Us




Windows 10 Forums