Yet another BSoD but no dump image produced problem.

[WinSae77]

Dear all,

I have encountered a very strange situation on Windows 7.

My Start and Recovery Tab is set as,

Write an event to the system log checked;
Automatically restert not checked.
Kernel memory dump chosen,
Dump file input as %SystemRoot%\MEMORY.DMP
Overwrite any existing file checked.


The corresponding registry values are
HKLM\SYSTEM\CurrentControlSet\Control\CrashControl |

AlwaysKeepMemoryDump REG_DWORD 1
AutoReboot REG_DWORD 0
CrashDumpEnabled REG_DWORD 2
DumpFile REG_EXPAND_SZ %SystemRoot%\MEMORY.DMP
DumpFilters REG_MULTI_SZ dumpfve.sys
LogEvent REG_DWORD 1
MinidumpDir REG_EXPAND_SZ %SystemRoot%\Minidump
MinidumpsCount REG_DWORD 50
Overwrite REG_DWORD 1


C:\Windows\system32>echo %SystemRoot%
showed
C:\Windows

Windows Error Reporting (WER) system has been set to MANUAL.

Windows Event Log Service has been started and set to automatically start.

Virtual memory tab is set as,

Automatically managing paging file size for all drives checked.

And the UAC is enabled because it can be viewed from
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

EnableLUA REG_DWORD 1

And once the MEMORY.DMP has been generated on this win7 system after I click the Crash button on NotMyFault.exe after choosing High IRQL fault(Kernel-mode).
But now no matter how many times I run NotMyFault.exe. MEMORY.DMP was never produced again even the event logged not anything about the dump or the deletion of the dump file.

I really cannot figure out if it is my fault or something make me fault again.
If anyone could help. Thanks in advance!

 

[WinSae77]

NotMyFault just caused an BSoD but no dump file. Can anyone help me?

 

[axe0]

For what are you trying to force a crash?

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

 

[WinSae77]

This is what I see after running the sfc /scannow a second time:

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.


And the CBS.log file is on the following link,

https://drive.google.com/file/d/0Bz5iDUuZc7xrNkRDVmNGNkxhNUE/view?usp=sharing

 

[axe0]

How much free space do you have?

 

[WinSae77]

There is 11.6 GB free space on my C drive (windows drive).

 

[axe0]

For Windows to create a dump, you need at least 25GB free space.
For Windows to function garanteed normal, you need at least 10-15% free space.

 

[WinSae77]

This time I freed the space on drive C (windows drive) to have a free space of 62.3G, the total space on drive C is 97.6G. But there is still no dump file was produced by BSoD of NotMyFault.

The only explanation I guess is my machine is rootkited. Some system file was modified by some evil guys.
Do I guess right? If so, how can repair from this?

 

[Golden]

Open Task Manager. Click on Processes tab. Find an innocuous process and right - click on it and choose "Create Dump File". Follow the prompts.

 

[WinSae77]

Open Task Manager. Click on Processes tab. Find an innocuous process and right - click on it and choose "Create Dump File". Follow the prompts.

What do you mean, the dump file of that process is there. What can this help to solve the missing dump file of BSoD?

BTW, till this moment, I can say it is not my fault! Absolutely!

 

[Golden]

Open Task Manager. Click on Processes tab. Find an innocuous process and right - click on it and choose "Create Dump File". Follow the prompts.

What do you mean, the dump file of that process is there. What can this help to solve the missing dump file of BSoD?

BTW, till this moment, I can say it is not my fault! Absolutely!

Who said anything about it being someone's fault?

There are many reasons why a .dmp file cannot be written. The steps I gave you are another method for creating a .dmp file, and checking for its existence.

 

[WinSae77]

OK. Thanks a lot! This dump file of that process is there. Then what should I do next to recover my dump file of BSoD?

 

[WinSae77]

Open Task Manager. Click on Processes tab. Find an innocuous process and right - click on it and choose "Create Dump File". Follow the prompts.

What do you mean, the dump file of that process is there. What can this help to solve the missing dump file of BSoD?

BTW, till this moment, I can say it is not my fault! Absolutely!

Who said anything about it being someone's fault?

There are many reasons why a .dmp file cannot be written. The steps I gave you are another method for creating a .dmp file, and checking for its existence.

I just say my unproductive dump file of BSoD is caused by but the evil guys' rootkit on modifying my system files not caused by my own fault.

So it is obviously NOT MY FAULT as GOD as my witness!

 

[WinSae77]

Dear Golden, can you give me any hint on what step should I take next to recover my dumping file function of BSoD?

 

[WinSae77]

Perhaps like what this page says,

http://answers.microsoft.com/en-us/...n/ab90eecc-49af-4502-b420-cb2d0213efb6?page=2

my last choice is to clean install?

Anyone has other opinion?

 

[axe0]

Are you using some kind of a cleaning program?

 

[WinSae77]

I have tried ccleaner. It's credible software. Many users installed it.

 

[axe0]

When was the last time you used it?

 

[Golden]

What do you mean, the dump file of that process is there. What can this help to solve the missing dump file of BSoD?

BTW, till this moment, I can say it is not my fault! Absolutely!

Who said anything about it being someone's fault?

There are many reasons why a .dmp file cannot be written. The steps I gave you are another method for creating a .dmp file, and checking for its existence.

I just say my unproductive dump file of BSoD is caused by but the evil guys' rootkit on modifying my system files not caused by my own fault.

So it is obviously NOT MY FAULT as GOD as my witness!

NotMyFault is simply a test BSOD. It doesn't contain any useful information.