Windows 10: Why MEMORY.DMP disappeared automatically in C:\Windows after BSOD?

Hi Heroes,


Windows 10


I configured my OS to generate 'auto memory dump' in sysdm.cpl, after that, I encountered a BSOD, and after Windows rebooted, I opened C:\Windows, found a memory dump named 'MEMORY.DMP' generated, I tried to copy it to another folder but it says something like"WerFault.exe is using this file", can't copy it, after a short time(less than a minute i guess), the file MEMORY.DMP is disappeared.

May I know why? how to configure my Windows 10 to generate a valid dump file?


Thanks for your help in advance!


BR,

Lanveu

:)

 

Unknown BSOD and missing DMP files.

Hello, my grandma is experiencing BSODs on her PC when the update for "Intel Corporation - Graphics Adapter WDDM1.0, WDDM1.2, WDDM1.3 released in August 2015 is trying to install. I'm accessing her PC using TeamViewer, i do not have a physical access to
it right now. When i installed Windows 10 to her PC this summer i have set it to record a full memory dmp, but there are no generated .dmp files neither in Minidump nor in C\Windows. THIS is
a link to the attached Event logs and SysInfo.nfo log along with a screenshot of the update. There are no .dmp files as i already said, i tried installing the update manually 3 times just to be sure that there are no dmp files. Every time the PC crashed with
a BSOD but there weren't any .dmp files.

 

BSOD issue help!!!

I built a new computer specs are in my signature but I keep having BSOD issues. Usually the monitors just shut off and computer still runs for another 10 seconds and then freezes.

Sometimes it reboots but mostly monitors loose signal then 10 seconds later the computer activity locks up. I can tell this because if I am watching a movie the audio still plays and on my Logitech G510 the display shows CPU and Ram activity.

Here is a copy of dumps from yesterday. They seem to all be different which drives me crazy.
Any suggestions?



020412-8190-01.dmp 2/4/2012 10:46:01 PM MACHINE_CHECK_EXCEPTION 0x0000009c 00000000`00000000 fffff880`031dfc70 00000000`00000000 00000000`00000000 hal.dll hal.dll+12818 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\020412-8190-01.dmp 8 15 7601 276,912


020412-8065-01.dmp 2/4/2012 9:21:39 PM 0x00000116 fffffa80`06cb72f0 fffff880`0447b8f0 ffffffff`c00000b5 00000000`0000000a dxgkrnl.sys dxgkrnl.sys+5d000 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\020412-8065-01.dmp 8 15 7601 1,667,696


020412-7597-01.dmp 2/4/2012 1:54:00 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000000 fffff800`034e7bb6 tcpip.sys tcpip.sys+7c610 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\020412-7597-01.dmp 8 15 7601 276,912

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.