Windows 10: BSOD with Memory Dump

Discus and support BSOD with Memory Dump in Windows 10 Ask Insider to solve the problem; I honestly have no idea how to read this, can anyone give me some pointers? Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64 Copyright (c)... Discussion in 'Windows 10 Ask Insider' started by /u/Slacker1540, Jul 19, 2020.

  1. /U/SLACKER1540
    /u/Slacker1540 Win User

    BSOD with Memory Dump


    I honestly have no idea how to read this, can anyone give me some pointers?

    Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [c:\windows\minidump\071920-13656-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Error: Set symbol search path attempts to access 'c:\windows\i386' failed: 0x2 - The system cannot find the file specified. ************* Path validation summary ************** Response Time (ms) Location Error c:\windows\i386 ************* Path validation summary ************** Response Time (ms) Location Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: c:\windows\i386 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 = 0xfffff805`57a00000 PsLoadedModuleList = 0xfffff805`57e48190 Debug session time: Sun Jul 19 12:04:05.030 2020 (UTC - 4:00) System Uptime: 1 days 2:10:59.855 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ...................................... Loading User Symbols Loading unloaded module list ...................... For analysis of this file, run !analyze -v 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8055def61a6, The address that the exception occurred at Arg3: ffff900ef09f6e48, Exception Record Address Arg4: ffff900ef09f6690, Context Record Address Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for win32k.sys KEY_VALUES_STRING: 1 Key : AV.Fault Value: Execute Key : Analysis.CPU.Sec Value: 4 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-VIF4KUJ Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 10 Key : Analysis.Memory.CommitPeak.Mb Value: 73 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: 7e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff8055def61a6 BUGCHECK_P3: ffff900ef09f6e48 BUGCHECK_P4: ffff900ef09f6690 EXCEPTION_RECORD: ffff900ef09f6e48 -- (.exr 0xffff900ef09f6e48) ExceptionAddress: fffff8055def61a6 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000008 Parameter[1]: fffff8055def61a6 Attempt to execute non-executable address fffff8055def61a6 CONTEXT: ffff900ef09f6690 -- (.cxr 0xffff900ef09f6690) rax=fffff8055def61a6 rbx=ffffaf8912c1d000 rcx=ffff900ef09f70c8 rdx=ffff900ef09f7130 rsi=0000000000000000 rdi=0000000000002000 rip=fffff8055def61a6 rsp=ffff900ef09f7088 rbp=ffff900ef09f7190 r8=ffff900ef09f7100 r9=ffffaf890e129040 r10=fffff80557b37eb0 r11=0000000000000000 r12=0000000000000000 r13=0000000000000020 r14=0000000000000000 r15=ffff900ef09f7501 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050246 fffff805`5def61a6 ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System EXECUTE_ADDRESS: fffff8055def61a6 FAILED_INSTRUCTION_ADDRESS: +0 fffff805`5def61a6 ?? ??? ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. EXCEPTION_CODE_STR: c0000005 EXCEPTION_PARAMETER1: 0000000000000008 EXCEPTION_PARAMETER2: fffff8055def61a6 EXCEPTION_STR: 0xc0000005 STACK_TEXT: ffff900e`f09f7088 fffff805`584e560e : 00000000`00000000 ffff900e`f09f7120 ffff900e`00000020 00000000`00000000 : 0xfffff805`5def61a6 ffff900e`f09f7090 fffff805`5825da40 : 00000000`00000000 00000000`00000000 00000000`001e001c fffff805`5818c950 : hal!HalpEnumerateEnvironmentVariablesWithFilter+0x14e ffff900e`f09f7380 fffff805`5825d301 : 00000000`00002000 ffff900e`f09f7469 00000000`00000002 ffffc903`948d9090 : nt!IopEnumerateEnvironmentVariablesHal+0x20 ffff900e`f09f73c0 fffff805`583133a9 : 00000000`00002000 ffff900e`f09f7660 ffff9901`1c74f000 00000000`00000000 : nt!IoEnumerateEnvironmentVariablesEx+0x6d ffff900e`f09f74d0 fffff805`57bd3c15 : 00000000`00002000 ffff900e`f09f77d0 00000000`00002000 00000000`4b444342 : nt!NtEnumerateBootEntries+0x1d9 ffff900e`f09f75e0 fffff805`57bc61e0 : fffff805`583331cf 00000000`00000000 ffff900e`f09f7869 ffff900e`f09f77f4 : nt!KiSystemServiceCopyEnd+0x25 ffff900e`f09f7778 fffff805`583331cf : 00000000`00000000 ffff900e`f09f7869 ffff900e`f09f77f4 ffff900e`00000000 : nt!KiServiceLinkage ffff900e`f09f7780 fffff805`583323d8 : ffffc903`aa0b2eb0 ffff900e`f09f7869 00000000`00002000 00000000`00000016 : nt!BiEnumerateBootEntries+0x97 ffff900e`f09f77c0 fffff805`583320f9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!BiBuildIdentifierList+0x280 ffff900e`f09f78d0 fffff805`58204f1c : 00000000`00000000 ffffffff`00000000 00000000`00000000 00000000`00000002 : nt!BiBindEfiNamespaceObjects+0x49 ffff900e`f09f7910 fffff805`5813bd24 : ffff900e`f09f7a40 fffff805`00000000 00000000`00000006 00000000`00000001 : nt!BiOpenSystemStore+0xc8880 ffff900e`f09f7990 fffff805`582b8811 : ffffaf88`fe7fcd70 fffff805`57f9f770 00000000`00000000 00000000`00000000 : nt!BcdOpenStore+0x6c ffff900e`f09f79d0 fffff805`58128fdf : ffffaf89`0e129040 fffff805`5812923b ffffaf89`0e129040 fffff805`00000000 : nt!PopBcdOpen+0x11 ffff900e`f09f7a00 fffff805`57f9f7df : 00000000`00000000 ffffaf89`0e129040 ffffaf88`f588b560 fffff805`58128a90 : nt!PopFreeHiberContext+0x2b ffff900e`f09f7a40 fffff805`57a83965 : ffffaf88`f588b560 ffffaf89`0e129000 ffffaf88`f588b500 ffffaf88`ff551698 : nt!PopUnlockAfterSleepWorker+0x6f ffff900e`f09f7a70 fffff805`57b1e155 : ffffaf89`0e129040 00000000`00000080 ffffaf88`f58a7100 fffff805`57b01359 : nt!ExpWorkerThread+0x105 ffff900e`f09f7b10 fffff805`57bc99c8 : ffff9901`1af8b180 ffffaf89`0e129040 fffff805`57b1e100 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffff900e`f09f7b60 00000000`00000000 : ffff900e`f09f8000 ffff900e`f09f1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: nt!IopEnumerateEnvironmentVariablesHal+20 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.18362.959 STACK_COMMAND: .cxr 0xffff900ef09f6690 ; kb BUCKET_ID_FUNC_OFFSET: 20 FAILURE_BUCKET_ID: AV_BAD_IP_nt!IopEnumerateEnvironmentVariablesHal OS_VERSION: 10.0.18362.1 BUILDLAB_STR: 19h1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {cb08ffe2-fecf-1a23-2030-12f447e007f9} Followup: MachineOwner ---------
    submitted by /u/Slacker1540
    [link] [comments]

    :)
     
    /u/Slacker1540, Jul 19, 2020
    #1
  2. SUMIT DHIMAN2
    Sumit Dhiman2 Win User

    Driver verifier dump file BSOD

    The Memory dump you uploaded was had a bugcheck of 50, not C4(Driver verifier Detected Violation). Nothing constructive was found in the dump, though.

    Step 1:

    Configure your PC to generate MiniDumps:

    Configure Windows 10 to Create Minidump on BSOD

    Step 2:

    Do a memory Test:

    Memory problems.
     
    Sumit Dhiman2, Jul 19, 2020
    #2
  3. BORE07TM
    Bore07tm Win User
    Frequent Memory Dumps

    Thank you for your response.

    I have uninstalled cccleANER as suggested.

    I have turned off real time scanning on McAfee Total Protection.

    A couple of questions:

    1. How can I check that I am not getting Memory dump files anymore? - they were detected by cccleANER
    2. How can I check that I'm not getting interference between Malwarebytes and McAfee? - i.e. I need to know what level of RAM?
    Thank you for your assistance
     
    Bore07tm, Jul 19, 2020
    #3
  4. AELTZIS
    aeltzis Win User

    BSOD with Memory Dump

    Dumping physical memory

    Last days i get bsod all the time with different error code each time. Probably its a driver issue. But my question is why in all bsod i got, at the bottom of the bsod where it says "dumping physical memory to disk..." its always less than 100? Usually
    it says dumping physical memory to disk 95 but some times is only 50. What does that mean?
     
    aeltzis, Jul 19, 2020
    #4
Thema:

BSOD with Memory Dump

Loading...

  1. BSOD with Memory Dump - Similar Threads - BSOD Memory Dump

  2. Memory dump errors, glitchy BSODs

    in Windows 10 Software and Apps
    Memory dump errors, glitchy BSODs: Since the beginning for May I have been experiencing my rig hard restarting sometimes with a glitchy BSOD with no discernable error code and other times my screen just freezes until restarting without producing a memory.dmpI know that trying to produce this file results in an...

  3. BSOD / Memory Dump

    in Windows 10 Software and Apps
    BSOD / Memory Dump: The issue is:PAGE_FAULT_IN_NONPAGED_AREA 50Invalid system memory was referenced. This cannot be protected by try-except.Typically the address is just plain bad or it is pointing at freed memory.I have been having on and off crashing with this error as well...

  4. BSOD / Memory Dump

    in Windows 10 BSOD Crashes and Debugging
    BSOD / Memory Dump: The issue is:PAGE_FAULT_IN_NONPAGED_AREA 50Invalid system memory was referenced. This cannot be protected by try-except.Typically the address is just plain bad or it is pointing at freed memory.I have been having on and off crashing with this error as well...

  5. BSOD / Memory Dump

    in Windows 10 Gaming
    BSOD / Memory Dump: The issue is:PAGE_FAULT_IN_NONPAGED_AREA 50Invalid system memory was referenced. This cannot be protected by try-except.Typically the address is just plain bad or it is pointing at freed memory.I have been having on and off crashing with this error as well...

  6. BSOD - memory dump analysis

    in Windows 10 BSOD Crashes and Debugging
    BSOD - memory dump analysis: I've been getting BSOD, for a few times now in the last few months. The debugging showed same issue every time. Can someone help me figure out the exact root cause of the issue ?Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 3 Key :...

  7. BSOD - memory dump analysis

    in Windows 10 Gaming
    BSOD - memory dump analysis: I've been getting BSOD, for a few times now in the last few months. The debugging showed same issue every time. Can someone help me figure out the exact root cause of the issue ?Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 3 Key :...

  8. BSOD - memory dump analysis

    in Windows 10 Software and Apps
    BSOD - memory dump analysis: I've been getting BSOD, for a few times now in the last few months. The debugging showed same issue every time. Can someone help me figure out the exact root cause of the issue ?Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 3 Key :...

  9. BSOD Memory Dump

    in Windows 10 BSOD Crashes and Debugging
    BSOD Memory Dump: Just purchased a new Surface Laptop 3 i5, 128GB SSD, 8GB RAM. I'm receiving BSOD's even after re-installing the OS Windows 10 Pro x64. I collected the dump file and need confirmation as the error appears to be hardware Memory related. Please analyse and advise. Link to DMP...

  10. Questions regarding BSODs and Memory Dumps

    in Windows 10 BSOD Crashes and Debugging
    Questions regarding BSODs and Memory Dumps: Hello Microsoft Community I recently have had some blue screens the recently this month. It happens sporadically but in all of the times the computer often restarts too quickly to display an error code on what was the cause. Another problem was that I also tried to find the...