BSOD on new acer predator g3 first time only less than two week old


  1. Posts : 7
    windows 10
       #1

    BSOD on new acer predator g3 first time only less than two week old


    have a new acer pc only two weeks old. when using outlook it froze then crashed and rebooted. attached is zip file with info. Any advice would be appreciated
      My Computers

  2. FreeBooter's Avatar
    Posts : 3,995
    Windows 10 Pro 64-bit
       #2

    Test RAM modules for errors using Memtest86+ software make sure to run the test at least five times more is better.
      My Computer


  3. Posts : 7
    windows 10
    Thread Starter
       #3

    Ran Memtest86 7 times no errors reported
      My Computers

  4. FreeBooter's Avatar
    Posts : 3,995
    Windows 10 Pro 64-bit
       #4

    I think the fastest way to track this on is to use a testing tool called Driver Verifier.

    If this tool finds a problem, your machine will crash again. Hopefully with it enabled, it will allow you to easily identify the bad driver.

    Enable driver verifier
    1) Open an elevated command prompt
    2) Type "verifier /standard /all" (no quotes)
    3) Reboot your machine
    4) Use machine again until it crashes (hopefully this will be fast :)


    After the crash & reboot, go into safe mode.

    Disable driver verifier
    1) Open an elevated command prompt
    2) Type "verifier /reset" (no quotes)
    3) Reboot your machine


    Please upload any minidumps from subsequent crashes for analysis.
      My Computer

  5. Spectrum's Avatar
    Posts : 546
    seL4
       #5

    Here are the 3rd party drivers I see in the stack.

    rt640x64.sys is your ethernet driver, here is a link the latest release.

    For reference you have version 10.10.714.2016 installed, and the latest release is verison 10.021.0811.2017.

    kneps.sys, klflt.sys, klids.sys, and klim6.sys are all part of Kaspersky anti-virus, please ensure it is fully up to date, further troubleshooting may call for it to be removed or temporarily disabled.

    Code:
    Start memory scan  : 0xffffae8086c66d28 ($csp)
    End memory scan    : 0xffffae8086c68000 (Kernel Stack Base)
    
                   rsp : 0xffffae8086c66d28 : 0xfffff8032358d8a9 : nt!KiBugCheckDispatch+0x69
    *** WARNING: Unable to verify timestamp for kneps.sys
    *** ERROR: Module load completed but symbols could not be loaded for kneps.sys
    0xffffae8086c66d28 : 0xfffff8032358d8a9 : nt!KiBugCheckDispatch+0x69
    *** WARNING: Unable to verify timestamp for klflt.sys
    *** ERROR: Module load completed but symbols could not be loaded for klflt.sys
    0xffffae8086c66e68 : 0xfffff8032358be7d : nt!KiPageFault+0x23d
    0xffffae8086c66e70 : 0x0000000000000000 :  Trap @ ffffae8086c66e70
    *** WARNING: Unable to verify timestamp for klids.sys
    *** ERROR: Module load completed but symbols could not be loaded for klids.sys
    0xffffae8086c66f78 : 0xfffff803236955a7 : nt!ExAllocatePoolWithTag+0x207
    *** WARNING: Unable to verify timestamp for klim6.sys
    *** ERROR: Module load completed but symbols could not be loaded for klim6.sys
    0xffffae8086c67408 : 0xfffff80d76243317 : ndis!ndisCallReceiveHandler+0x47
    0xffffae8086c67450 : 0xfffff80d78ab20e8 :  Trap @ ffffae8086c67450
    0xffffae8086c67458 : 0xfffff80d762425c8 : ndis!NdisMIndicateReceiveNetBufferLists+0x658
    0xffffae8086c674b8 : 0xfffff80323584074 : nt!KiInterruptDispatchNoLockNoEtw+0x44
    0xffffae8086c67578 : 0xfffff803235876ef : nt!SwapContext+0x7f
    0xffffae8086c675b8 : 0xfffff80323516aa1 : nt!KeFlushIoBuffers+0x51
    *** WARNING: Unable to verify timestamp for rt640x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
    0xffffae8086c676f0 : 0xfffff80d79fc7470 :  !da ""<--- MpHandleRecvInterrupt.""
    0xffffae8086c67898 : 0xfffff80323449f96 : nt!KiSwapThread+0x1b6
    0xffffae8086c67960 : 0xffffae8086c4fb00 : 0xfffff80323416000 : "nt!TmInitSystemPhase2 <PERF> (nt+0x0)"
    0xffffae8086c67988 : 0xfffff80d7624dc74 : ndis!ndisQueuedMiniportDpcWorkItem+0x194
    0xffffae8086c67a40 : 0xfffff80d7625cd00 : ndis!ndisIfUpdateInterfaceOnAddDevice+0x19c
    0xffffae8086c67a50 : 0xfffff80d7625cd00 : ndis!ndisIfUpdateInterfaceOnAddDevice+0x19c
    0xffffae8086c67ab8 : 0xfffff80d7625ceac : ndis!ndisReceiveWorkerThread+0x15c
    0xffffae8086c67ad8 : 0xfffff80d7625cd00 : ndis!ndisIfUpdateInterfaceOnAddDevice+0x19c
    0xffffae8086c67b00 : 0xfffff80323416000 : "nt!TmInitSystemPhase2 <PERF> (nt+0x0)"
    0xffffae8086c67b18 : 0xfffff8032343490c : nt!EtwTraceContextSwap+0xec
    0xffffae8086c67b88 : 0xfffff803234f2f77 : nt!PspSystemThreadStartup+0x47
    0xffffae8086c67ba0 : 0xfffff80d7625cd50 : ndis!ndisReceiveWorkerThread
    0xffffae8086c67bb0 : 0xfffff8032380fa40 : nt!KiInitialThread
    0xffffae8086c67bd0 : 0xfffff8032380fa40 : nt!KiInitialThread
    0xffffae8086c67bd8 : 0xfffff80323587a06 : nt!KiStartSystemThread+0x16
    0xffffae8086c67bf0 : 0xfffff803234f2f30 : nt!PspSystemThreadStartup
      My Computer

  6. Ztruker's Avatar
    Posts : 13,512
    Windows 10 Pro X64 20H4 19042.746
       #6

    Since this is a two week old PC I would return it for a replacement.A new PC should not have BSOD problems.
      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 13:17.
Find Us




Windows 10 Forums