New
#1
BSODs when resuming from Sleep mode
Hello,
Ever since I upgraded to W10 Pro (from W8.1 Pro) my PC has started bluescreening when resuming from Sleep. MEMORY_MANAGEMENT is the most common one, and the only one that has occured so far after upgrade to Build 10586 (upgraded 2015-11-13).
BSODs KMODE_EXCEPTION_NOT_HANDLED (NTFS.sys), SYSTEM_SERVICE_EXCEPTION, KERNEL_SECURITY_CHECK_FAILURE occured before upgrade to Build 10586, and might happen again. Minidumps for these disappeared during upgrade to latest W10 build
BIOS is the latest one. Ran Memtest86+ yesterday, 8 passes with all 11 tests, no errors found. Windows Memory Diagnostics didnŽt find anything either.
Please help, warranty on all hardware will run out in a month and need to find out if any HW needs to be changed.
Greetings from Gothenburg, Sweden
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff6800001e090
Arg3: c7200001eda3c847
Arg4: ffffe000607d0930
Debugging Details:
------------------
DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump
BUGCHECK_STR: 0x1a_41201
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: OneDrive.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8029b1657fd to fffff8029b146460
STACK_TEXT:
ffffd000`2390da98 fffff802`9b1657fd : 00000000`0000001a 00000000`00041201 fffff680`0001e090 c7200001`eda3c847 : nt!KeBugCheckEx
ffffd000`2390daa0 fffff802`9b03ae91 : fffff680`0001e090 00000000`03c12000 c7200001`eda3c847 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x109fd
ffffd000`2390daf0 fffff802`9b03ab69 : ffffe000`00000000 00000000`00000006 ffffe000`1ea783c8 ffffe000`19e1b080 : nt!MiQueryAddressState+0x171
ffffd000`2390db70 fffff802`9b3e193e : 00000000`00000006 00000000`00000002 00000000`03c12000 00000000`00000000 : nt!MiQueryAddressSpan+0x119
ffffd000`2390dc10 fffff802`9b3e13c1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmQueryVirtualMemory+0x56e
ffffd000`2390dd80 fffff802`9b150ca3 : fffff6fb`7da00008 fffff6fb`40001db8 fffff680`003b7710 ffff4b32`50545e44 : nt!NtQueryVirtualMemory+0x25
ffffd000`2390ddd0 00007ffe`2acf51b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0011ad28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`2acf51b4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+109fd
fffff802`9b1657fd cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+109fd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 563b1170
IMAGE_VERSION: 10.0.10586.3
BUCKET_ID_FUNC_OFFSET: 109fd
FAILURE_BUCKET_ID: 0x1a_41201_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0x1a_41201_nt!_??_::FNODOBFM::_string_
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1a_41201_nt!_??_::fnodobfm::_string_
FAILURE_ID_HASH: {48c83227-3944-10a1-bf0f-11b43dc9c13b}
Followup: MachineOwner
---------
Last edited by Janne; 14 Nov 2015 at 16:00.