Windows 10: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2...

Hi.


We have a laptop that has been crashing/rebooting on it's own. Checked in the Event log and found the error below:


The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 0x0000000000000062, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000. A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: de8dfe6c-1dfe-4639-88a9-deace4775300.

We did a memory dump and got the information as below:


Microsoft R Windows Debugger Version 10.0.18362.1 X86
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\amccabe\Downloads\MEMORY\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP 8 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`07600000 PsLoadedModuleList = 0xfffff802`07a48150
Debug session time: Mon Jul 13 16:35:23.721 2020 UTC - 4:00
System Uptime: 0 days 1:02:00.380
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................
Loading User Symbols

Loading unloaded module list
..............
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER c2
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000062, Attempt to free a contiguous memory address where bytes after the end of the allocation have been overwritten
Arg2: 0000000000000000, Starting address
Arg3: 0000000000000000, Address where bits are corrupted
Arg4: 0000000000000000, reserved

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 402

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: Acer

SYSTEM_PRODUCT_NAME: Aspire A515-54

SYSTEM_SKU: 0000000000000000

SYSTEM_VERSION: V1.07

BIOS_VENDOR: Insyde Corp.

BIOS_VERSION: V1.07

BIOS_DATE: 06/28/2019

BASEBOARD_MANUFACTURER: WHL

BASEBOARD_PRODUCT: Doc_WC

BASEBOARD_VERSION: V1.07

DUMP_TYPE: 0

BUGCHECK_P1: 62

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0xc2_62

CPU_COUNT: 8

CPU_MHZ: 708

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 8e

CPU_STEPPING: b

CPU_MICROCODE: 6,8e,b,0 F,M,S,R SIG: B8'00000000 cache B8'00000000 init

BLACKBOXBSD: 1 !blackboxbsd


BLACKBOXNTFS: 1 !blackboxntfs


BLACKBOXPNP: 1 !blackboxpnp


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_TIME: 07-16-2020 17:35:29.0048

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER: from fffff80207840016 to fffff802077c14e0

STACK_TEXT:
ffffc702`1842f458 fffff802`07840016 : 00000000`000000c2 00000000`00000062 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffc702`1842f460 fffff802`07742569 : 00000000`00000000 00000000`546e6f43 00000000`00000000 fffff802`099850a8 : nt!MmFreeContiguousMemory+0x14b1c6
ffffc702`1842f4d0 fffff802`099abe34 : 00000000`00000206 ffffc88a`66fe2d80 00000000`00000000 ffffc88a`6835b080 : nt!HvlpFreeOverlayPages+0x9
ffffc702`1842f500 fffff802`098dfe20 : 00000000`00000000 ffffc88a`5ce23010 00000000`00000000 00000000`00000000 : storport!StorPortExtendedFunction+0x1e2e4
ffffc702`1842f5d0 fffff802`098fa3d3 : ffffc88a`6107b7c0 ffff9b01`50995f10 00000000`00000000 fffff802`099850a8 : iaStorAVC!Wcdl::Allocator::freeContiguous+0x20
ffffc702`1842f610 fffff802`098f1d67 : ffff9b01`53b2b440 fffff802`0987c834 ffffc88a`5cdc90c0 ffffc88a`5ceb9f60 : iaStorAVC!readSmartAttribsCompletion+0x2bf
ffffc702`1842f6c0 fffff802`098ee81c : ffffc88a`5ceb9f60 ffffc702`1842f801 ffff9b01`53b2b440 fffff802`0995c820 : iaStorAVC!NvmRequest::complete+0x1b7
ffffc702`1842f700 fffff802`098ed2ef : ffffc88a`5ceb9f60 ffffc702`1842f8f0 00000000`00000000 00000000`00010001 : iaStorAVC!NvmePort:rocessCompletionQueueForSharedInterrupt+0x144
ffffc702`1842f790 fffff802`0766ae95 : ffff9b01`50992f80 ffffc702`1842f8f0 ffffc88a`5ce689e8 00000000`00000000 : iaStorAVC!NvmePort::dpc+0x47
ffffc702`1842f7f0 fffff802`0766a4ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305
ffffc702`1842f930 fffff802`077c5024 : 00000000`00000000 ffff9b01`50990180 ffff9b01`509a1240 ffffc88a`68d2d080 : nt!KiRetireDpcList+0x1ef
ffffc702`1842fb60 00000000`00000000 : ffffc702`18430000 ffffc702`18429000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84


THREAD_SHA1_HASH_MOD_FUNC: fcf04194b83c95c011259dce8d63236eb0918d1e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e162e29ef8e0816e3d760b27edfacbff67fae16c

THREAD_SHA1_HASH_MOD: 8759373e776f00dad3cd7d0e0a94e69869d94ac9

FOLLOWUP_IP:
iaStorAVC!Wcdl::Allocator::freeContiguous+20
fffff802`098dfe20 4883c438 add rsp,38h

FAULT_INSTR_CODE: 38c48348

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: iaStorAVC!Wcdl::Allocator::freeContiguous+20

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: iaStorAVC

IMAGE_NAME: iaStorAVC.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5a7ae8c0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 20

FAILURE_BUCKET_ID: 0xc2_62_iaStorAVC!Wcdl::Allocator::freeContiguous

BUCKET_ID: 0xc2_62_iaStorAVC!Wcdl::Allocator::freeContiguous

PRIMARY_PROBLEM_CLASS: 0xc2_62_iaStorAVC!Wcdl::Allocator::freeContiguous

TARGET_TIME: 2020-07-13T20:35:23.000Z

OSBUILD: 18362

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: 1972-08-21 20:24:00

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 56fe

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc2_62_iastoravc!wcdl::allocator::freecontiguous

FAILURE_ID_HASH: {db05951a-494c-21d9-59f5-c7c870b2eeba}

Followup: MachineOwner



Not sure what could be the cause of this. Any help would be appreciated. Thanks!



:)

 

The computer has rebooted from a bugcheck

I get the error: The computer has rebooted from a bugcheck. My computer keeps rebooting. What are the steps?

 

The computer has rebooted from a bugcheck

I have setup of windows server 2012 cluster machines.any one of the machine is always rebooting from bugcheck with below error coad.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000094, 0xfffff801dac14256, 0xffffd001d794db30, 0x0000000000000011). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021219-123437-01.

please suggest a solution for this i am frustrated due to this issue now..

 

The computer has rebooted from a bugcheck.

try This

How To Fix ‘The Computer Has Rebooted From a Bugcheck’ Error

1. Check For the memory problems. The computer has rebooted from a bugcheck usually occurs due to memory, CPU, or driver related problem.
2. Perform a clean boot. Well, if you believe that you are getting the error message due to third-party services, then you can try performing a clean boot.
3. Update the drivers. Well, this specific BSOD error sometimes occurs due to outdated or corrupted device drivers