Windows 10: windows blue screen happened frequently (70368744177664),(2)

Discus and support windows blue screen happened frequently (70368744177664),(2) in Windows 10 Network and Sharing to solve the problem; everytime when iplaying some games the computer will be shut down and show the blue screen, error key word :(70368744177664),(2) source:... Discussion in 'Windows 10 Network and Sharing' started by WILLIAM TIUTIU, Aug 13, 2019.

  1. WILLIAM TIUTIU
    WILLIAM TIUTIU Win User

    windows blue screen happened frequently (70368744177664),(2)


    everytime when iplaying some games the computer will be shut down and show the blue screen,



    error key word windows blue screen happened frequently (70368744177664),(2) :(70368744177664),(2)


    source: kernel-power




    i have done the debug checking, here is the result, but i cant read the program, so can you tell me where the problem is?




    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 17763 MP (6 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 17763.1.amd64fre.rs5_release.180914-1434

    Machine Name:

    Kernel base = 0xfffff806`6281d000 PsLoadedModuleList = 0xfffff806`62c38670

    Debug session time: Tue Aug 13 17:26:40.823 2019 (UTC + 8:00)

    System Uptime: 3 days 5:34:01.745

    Loading Kernel Symbols

    ...............................................................

    ..............................................................Page 2001a10c0 too large to be in the dump file.

    ..

    ..............................................

    Loading User Symbols

    PEB is paged out (Peb.Ldr = 00000000`04115018). Type ".hh dbgerr001" for details

    Loading unloaded module list

    .....................................

    For analysis of this file, run !analyze -v

    1: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    KMODE_EXCEPTION_NOT_HANDLED (1e)

    This is a very common bugcheck. Usually the exception address pinpoints

    the driver/function that caused the problem. Always note this address

    as well as the link date of the driver/image that contains this address.

    Arguments:

    Arg1: ffffffffc0000005, The exception code that was not handled

    Arg2: fffff8067919148f, The address that the exception occurred at

    Arg3: ffff8c09c5036cf8, Parameter 0 of the exception

    Arg4: ffff8c09c5036540, Parameter 1 of the exception



    Debugging Details:

    ------------------



    Page 2001a10c0 too large to be in the dump file.

    Page 2001a10c0 too large to be in the dump file.



    KEY_VALUES_STRING: 1





    PROCESSES_ANALYSIS: 1



    SERVICE_ANALYSIS: 1



    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 401



    BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434



    SYSTEM_MANUFACTURER: System manufacturer



    SYSTEM_PRODUCT_NAME: System Product Name



    SYSTEM_SKU: ASUS_MB_CNL



    SYSTEM_VERSION: System Version



    BIOS_VENDOR: American Megatrends Inc.



    BIOS_VERSION: 0402



    BIOS_DATE: 04/18/2018



    BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.



    BASEBOARD_PRODUCT: PRIME H310M-E



    BASEBOARD_VERSION: Rev X.0x



    DUMP_TYPE: 1



    BUGCHECK_P1: ffffffffc0000005



    BUGCHECK_P2: fffff8067919148f



    BUGCHECK_P3: ffff8c09c5036cf8



    BUGCHECK_P4: ffff8c09c5036540



    WRITE_ADDRESS: ffff8c09c5036540



    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>



    FAULTING_IP:

    tcpip!IpFlcReceivePreValidatedPackets+60f

    fffff806`7919148f 488b4120 mov rax,qword ptr [rcx+20h]



    EXCEPTION_PARAMETER1: ffff8c09c5036cf8



    EXCEPTION_PARAMETER2: ffff8c09c5036540



    BUGCHECK_STR: 0x1E_c0000005



    CPU_COUNT: 6



    CPU_MHZ: bb8



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 9e



    CPU_STEPPING: a



    CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 96'00000000 (cache) 96'00000000 (init)



    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    PROCESS_NAME: League of Legends.exe



    CURRENT_IRQL: 2



    ANALYSIS_SESSION_HOST: DESKTOP-F4NE8M1



    ANALYSIS_SESSION_TIME: 08-13-2019 18:12:57.0359



    ANALYSIS_VERSION: 10.0.18362.1 x86fre



    DPC_STACK_BASE: FFFF8C09C5037FB0



    LAST_CONTROL_TRANSFER: from fffff80662aaafa7 to fffff806629d0f50



    STACK_TEXT:

    ffff8c09`c5035c98 fffff806`62aaafa7 : 00000000`0000001e ffffffff`c0000005 fffff806`7919148f ffff8c09`c5036cf8 : nt!KeBugCheckEx

    ffff8c09`c5035ca0 fffff806`629ea0b6 : fffff806`7919148f fffff806`6284c1a8 ffff8c09`c5036f30 ffff8c09`c5036540 : nt!KiFatalFilter+0x1f

    ffff8c09`c5035ce0 fffff806`629ab48f : 00000000`00000001 ffff8c09`c5037290 ffff8c09`c5031000 ffff8c09`c5038000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16

    ffff8c09`c5035d20 fffff806`629d9a5f : ffff8c09`c5037290 ffff8c09`c5036300 ffff8c09`c50363e0 00000000`0010001f : nt!_C_specific_handler+0x9f

    ffff8c09`c5035d90 fffff806`629323a0 : ffff8c09`c50363e0 00000000`00000000 ffff8c09`c5036300 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xf

    ffff8c09`c5035dc0 fffff806`6283fbb4 : ffff8c09`c5036cf8 ffff8c09`c5036a40 ffff8c09`c5036cf8 ffffb188`864c1420 : nt!RtlDispatchException+0x430

    ffff8c09`c5036510 fffff806`629e28c2 : 00000000`00000000 ffffb188`963fedc0 00000000`00000000 fffff806`78f0381a : nt!KiDispatchException+0x144

    ffff8c09`c5036bc0 fffff806`629de74b : ffff3f84`9ceade2b 00000000`10a515e8 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2

    ffff8c09`c5036da0 fffff806`7919148f : 00000000`00000000 00000000`00000000 ffffb188`8c5a8900 fffff806`791a97c5 : nt!KiGeneralProtectionFault+0x30b

    ffff8c09`c5036f30 fffff806`79****f

    ffff8c09`c5037150 fffff806`628fd9c8 : ffff8c09`c5037440 00000000`00000002 ffffb188`928eb080 ffff8c09`c50373c0 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x127

    ffff8c09`c5037290 fffff806`628fd93d : fffff806`791ac1f0 ffff8c09`c50373c0 ffffb188`84ffa020 ffffb188`84402280 : nt!KeExpandKernelStackAndCalloutInternal+0x78

    ffff8c09`c5037300 fffff806`791904d3 : ffff8c09`c5037440 00000000`00000000 ffffb188`8c8d4010 ffff8c09`c5037400 : nt!KeExpandKernelStackAndCalloutEx+0x1d

    ffff8c09`c5037340 fffff806`78f02781 : 00000000`00000000 ffff8c09`c5037640 00000000`00000001 ffffb188`8c8d5010 : tcpip!FlReceiveNetBufferListChain+0x2c3

    ffff8c09`c5037540 fffff806`78f0239d : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000002 : ndis!ndisMIndicateNetBufferListsToOpen+0x221

    ffff8c09`c5037610 fffff806`78f078d8 : 00000000`00000001 fffff806`00000000 fffff806`00000000 00000000`00000002 : ndis!ndisMTopReceiveNetBufferLists+0x23d

    ffff8c09`c50376a0 fffff806`78f05087 : 00000000`0110b26f ffff8c09`c50377f0 fffff806`78f02160 00000000`00989680 : ndis!ndisCallReceiveHandler+0xc8

    ffff8c09`c50376f0 fffff806`7eaa187e : fffff806`78ac2570 ffffb188`8cea0bc0 00000000`00000002 ffffb188`8c564db0 : ndis!NdisMIndicateReceiveNetBufferLists+0x5b7

    ffff8c09`c5037870 fffff806`7ea827cc : fffff806`78ac24c0 fffff806`78ac2401 00000000`00000000 00000000`00000001 : rt640x64+0x2187e

    ffff8c09`c5037990 fffff806`7ea825f6 : 00000000`00000000 00000000`00000001 ffffb188`00000000 00000000`00000000 : rt640x64+0x27cc

    ffff8c09`c50379f0 fffff806`7ea828f6 : 00000000`00000000 ffff8c09`c5037b59 ffffb188`8d0d91a0 00000000`00000001 : rt640x64+0x25f6

    ffff8c09`c5037a40 fffff806`78f112b3 : ffffb188`8c8ce760 00000000`00000000 ffffb188`8d0d91a0 ffffb188`8c8ce760 : rt640x64+0x28f6

    ffff8c09`c5037ab0 fffff806`78f1230b : ffffb188`84af5220 ffffb188`8c8cebd8 ffffb188`865c5990 00000000`00020000 : ndis!ndisQueuedMiniportDpcWorkItem+0x193

    ffff8c09`c5037bc0 fffff806`62896677 : ffff8d81`71fd0f80 ffffb188`865c5990 ffff8d81`71fce180 ffff8d81`71fce180 : ndis!ndisPeriodicReceivesTimer+0xeb

    ffff8c09`c5037c60 fffff806`62895cbe : ffff8d81`71fce180 00000000`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x2e7

    ffff8c09`c5037da0 fffff806`629d7dd5 : 00016198`000d0d78 ffff8d81`71fce180 ffff8c09`c5857a80 00000000`00000000 : nt!KiRetireDpcList+0x1ae

    ffff8c09`c5037fb0 fffff806`629d7bc0 : 00000000`00000000 ffffb188`9298d2e0 00000000`77e53600 00000000`0427f6e4 : nt!KxRetireDpcList+0x5

    ffff8c09`c58579d0 fffff806`629d72b2 : ffffb188`928eb080 00000000`15784100 00000000`00000000 ffffb188`93fe2301 : nt!KiDispatchInterruptContinue

    ffff8c09`c5857a00 00000000`00c17ccc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2e2

    00000000`0427f620 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xc17ccc





    THREAD_SHA1_HASH_MOD_FUNC: 659208d9a808feffde2d378be774ac107c46392e



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: dae71fa48455e8db64f3c516340db0e6947b5e9f



    THREAD_SHA1_HASH_MOD: ae00d1398996368f80b4f84b635dd884c603bdce



    FOLLOWUP_IP:

    rt640x64+2187e

    fffff806`7eaa187e 488b442470 mov rax,qword ptr [rsp+70h]



    FAULT_INSTR_CODE: 24448b48



    SYMBOL_STACK_INDEX: 12



    SYMBOL_NAME: rt640x64+2187e



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: rt640x64



    IMAGE_NAME: rt640x64.sys



    DEBUG_FLR_IMAGE_TIMESTAMP: 5abb41ae



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 2187e



    FAILURE_BUCKET_ID: 0x1E_c0000005_rt640x64!unknown_function



    BUCKET_ID: 0x1E_c0000005_rt640x64!unknown_function



    PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_rt640x64!unknown_function



    TARGET_TIME: 2019-08-13T09:26:40.000Z



    OSBUILD: 17763



    OSSERVICEPACK: 0



    SERVICEPACK_NUMBER: 0



    OS_REVISION: 0



    SUITE_MASK: 272



    PRODUCT_TYPE: 1



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



    OS_LOCALE:



    USER_LCID: 0



    OSBUILD_TIMESTAMP: 2020-05-16 00:13:35



    BUILDDATESTAMP_STR: 180914-1434



    BUILDLAB_STR: rs5_release



    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434



    ANALYSIS_SESSION_ELAPSED_TIME: e46b



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x1e_c0000005_rt640x64!unknown_function



    FAILURE_ID_HASH: {b7435bde-2431-9c06-d345-66e14cad4c5d}



    Followup: MachineOwner

    :)
     
    WILLIAM TIUTIU, Aug 13, 2019
    #1
  2. MAYRA AQU
    Mayra Aqu Win User

    Blue Screen Of Death - Why does this one happen?

    Hi,

    A blue screen error or stop error usually means that the computer encountered some corruption. For us to isolate the issue, we need additional information:

    • Did you perform any changes prior to the issue?
    • Is the computer still able to go to the login screen or is it already stuck on the blue screen?

    In the meantime, we suggest checking and following the steps on this article:
    Troubleshoot blue screen errors    . It has information on why you've encounter this issue and it provide appropriate
    steps on how to fix it. Kindly choose the option based on when you've received the error.

    We'll wait for your response.
     
    Mayra Aqu, Aug 13, 2019
    #2
  3. FRANZKERSTEN
    FranzKersten Win User
    (70368744177664),(2)

    Hi, my PC restarts by it self with out any warning, Sometimes it is more than once a day and other times it could take up to two weeks before restarting by it self.

    In the event viewer I found the following code:

    (70368744177664),(2).

    I tired to Google it, but none of the search results offered a real solution.

    This is not a gaming PC, it is used for regular home office applications and internet browsing.

    Any suggestions please?
     
    FranzKersten, Aug 13, 2019
    #3
  4. ROAN T
    Roan T Win User

    windows blue screen happened frequently (70368744177664),(2)

    Blue Screen

    Hi,





    Blue screens could be caused by problems with your computer’s hardware or with its driver. Still, we
    would like to know more about the issue. Please clarify the following:

    • Did you get a STOP code?
    • Did you install any hardware or driver recently?



    For basic troubleshooting steps to resolve blue screen errors, we suggest checking out this
    article and simply follow the steps.



    Feel free to contact us if you need further help.
     
    Roan T, Aug 13, 2019
    #4
Thema:

windows blue screen happened frequently (70368744177664),(2)

Loading...

  1. windows blue screen happened frequently (70368744177664),(2) - Similar Threads - blue screen happened

  2. Frequent blue screens

    in Windows 10 Gaming
    Frequent blue screens: Hi,I am seeing frequent blue screens on my Win 11 device.Here are the minidumps for last 5 of them:012924-11984-01.dmp012624-13312-01.dmp011924-10531-01.dmp122823-10687-01.dmp122623-31171-01.dmpCan anyone have a look and see if there is an obvious issue like a faulty driver...

  3. Frequent Blue Screens

    in Windows 10 BSOD Crashes and Debugging
    Frequent Blue Screens: I've had a small uprade to my PC recently, I've added 16GB of RAM to the previous 16, bought a new SSD drive and new case fans. I've also changed my drives setup and reinstalled windows. After a few days I've started having frequent blue screens with ntoskrnl.exe crashing and...

  4. Frequent Blue Screen happening on Windows 10 v 2004

    in Windows 10 BSOD Crashes and Debugging
    Frequent Blue Screen happening on Windows 10 v 2004: Since installing the ver. 2004 update, I've been having a lot of BSoD errors, usually with the stop code MEMORY MANAGEMENT, can someone read the info from the minidump files and see what's going on?...

  5. Windows Blue Screens CLOCK WATCHDOG TIMEOUT Happens Frequently

    in Windows 10 BSOD Crashes and Debugging
    Windows Blue Screens CLOCK WATCHDOG TIMEOUT Happens Frequently: Hi, I get a bluescreen with error code CLOCK WATCHDOG TIMEOUT very frequently, often multiple times a day. I've had this since I first got my laptop, and it's been many months now. It's usually when I'm in the middle of working, not immediately after booting my PC. I've had...

  6. (70368744177664),(2) Crashes randomly happening

    in Windows 10 BSOD Crashes and Debugging
    (70368744177664),(2) Crashes randomly happening: Installed Norton antivirus and began experiencing these crashes. Have gone thru the process and believe I wiped it off my device but think that some of the changes it made to the system are still in place and continuing to cause my device to crash. I have attached a...

  7. Frequent Blue Screens

    in Windows 10 BSOD Crashes and Debugging
    Frequent Blue Screens: One of my Windows 10 (1803) systems recently starting having a spate of BSOD's. I didn't see the code for the first. The second showed a Stop Error of KERNEL_SECURITY_CHECK_FAILURE. I searched around and found some advice. I ran a file scan (sfc), which reported no...

  8. Frequent blue screen

    in AntiVirus, Firewalls and System Security
    Frequent blue screen: * Original title: 电脑频繁蓝屏 不知道原因，求解答 Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\46371\Desktop\elfinderTest\12.23\122318-12417-01.dmp] Mini Kernel Dump File: Only...

  9. (70368744177664),(2) Unexpected Restart

    in Windows 10 BSOD Crashes and Debugging
    (70368744177664),(2) Unexpected Restart: i left my laptop unattended for a few minutes and suddenly it shut down. i checked the event viewer and found out about the critical event. its an INSPIRON 7577 gaming laptoop and ive had it for several months and this is the first time that it has happened ever. im hoping it...

  10. Kernel-Power (70368744177664),(2)

    in Windows 10 Performance & Maintenance
    Kernel-Power (70368744177664),(2): Good Day, My computer is rebooting randomly. I have searched the web for solutions, but I have failed to fix the problem. Please help. I uploaded my system logs: https://1drv.ms/u/s!AgOA5CRz9rwKjECnWWKaeKUudd8a Below is the error message for the power failure:...

Users found this page by searching for:

  1. (70368744177664) (2)