Windows 10: MANUALLY_INITIATED_CRASH

Discus and support MANUALLY_INITIATED_CRASH in Windows 10 BSOD Crashes and Debugging to solve the problem; I pressed CTRL+SCROLL LOCK to see what happens and it crashed on Windows 10... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Britec Your Computer, Apr 27, 2020.

  1. MANUALLY_INITIATED_CRASH


    I pressed CTRL+SCROLL LOCK to see what happens and it crashed on Windows 10

    :)
     
    Britec Your Computer, Apr 27, 2020
    #1
  2. zbook Win User

    windows freeze DELL XPS15

    The whocrashed results displayed that you created a manual crash on 8/30/2017.
    What were the keyboard steps that you made to create the crash?


    On Wed 8/30/2017 7:41:41 PM your computer crashed
    crash dump file: C:\Windows\Minidump\083017-8234-01.dmp
    This was probably caused by the following module: i8042prt.sys (i8042prt+0x9E7A)
    Bugcheck code: 0xE2 (0x0, 0x0, 0x0, 0x0)
    Error: MANUALLY_INITIATED_CRASH
    file path: C:\Windows\system32\drivers\i8042prt.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: i8042 Port Driver
    Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
     
    zbook, Apr 27, 2020
    #2
  3. windows freeze DELL XPS15

    See post #26
     
    carl pilkington, Apr 27, 2020
    #3
  4. MANUALLY_INITIATED_CRASH

    Windows 10 Random Freezes

    Hi,

    I am experiencing frequent random freezes.

    Characteristics are:

    • in around 4 out of 5 system boots, the system freezes during the first 10 minutes
    • if it runs longer, a freeze will probably not happen for this session
    • no BSOD
    • ~10 seconds before the freeze, the mouse pointer starts lagging behind
    • after freeze, no Ctrl+Alt+Del possible
    I have removed or changed all external peripherals (headset, mouse, keyboard, gamepad...).
    I have checked the system RAM multiple times using memtest86, with no results.

    I am usually running my CPU overclocked (4 GHz instead of 3.4 GHz on an i5-4670K). For testing, I removed OC. Things did not change. Furthermore, when having a stable session, even burn in tests while being OC'ed don't freeze.

    This morning, I forced system crashes using the
    Ctrl+ScrlLk+ScrlLk key combination
    .

    Here are the minidumps and output of MSInfo:

    Private Seafile

    Because the crash reason is of course MANUALLY_INITIATED_CRASH, all automatic tools and most guides are not able to help me with this.

    I tried fiddling around with WinDbg, but that's obviously where my knowledge comes to a screeching halt MANUALLY_INITIATED_CRASH :)

    Would anybody be able to help me with this issue? I already thought about ripping all my hardware short of the GPU out and replacing it, but I really want to understand the cause of this...
     
    OliverRahner, Apr 27, 2020
    #4
Thema:

MANUALLY_INITIATED_CRASH