No crash dump file right after BSOD. Dumps set up properly and HDD LED blinking during a BSOD dump.
What title says. Windows 7 Pro x64 RTM. All updated. I have tried changing various settings in the Recovery options. Right now the settings are as follows: Write and event to system log: Yes; Automatically restart: No; Write debugging info: Kernel memory dump; Dump file: C:\CRASH.DMP; Overwrite existing: Yes; Yes, it didn't work even with the original path to %SystemRoot%... I have tried adding Everyone with Full Control to the folder, result is the same. This problem started occuring EXACTLY after I upgraded from Vista Business x64 months ago. Vista had this working just fine. You need BSOD and feedback, just ask. System config: Core 2 2.8GHz, 4GB DDR2, Quadro FX3600 512MB, C:\ has 2GB free (but it never worked when the space was even 16GB; yes, I tried different drives) Thanks in advance.
May 6th, 2010 5:29pm

Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software or anti-virus services (buggy services). The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are). To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: Microsoft - Help and Support If you are outside the US please see Microsoft Worldwide Home for regional support phone numbers. Meantime we can try some available steps as a general troubleshoot. 1. Please remove the antivirus and run the system with a period. If the issue does not occur, mainly focus on antivirus settings and compatibility. 2. Disable Automatic Restart and see detail information on the blue screen. 1).Click Start, in the Start Search box enter sysdm.cpl. 2).Click the tab Advanced. Under Startup and Recovery, click the Settings button. 3). Uncheck “Automatically restart”. 4). On the drop-down menu “Write debugging information”, choose “Small memory dump”. 5). Click OK. When Blue Screen displays, you may get more information from it.Arthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
May 10th, 2010 10:54am

Well, useful information. I am perfectly capable of debugging it myself. Moreover, if someone will be up to debug this, they won't be able to, as there is no dump file to debug. Even with the settings you gave me. Which is the main issue here. If I have some faulty driver, I can't know which exactly, as the SYS files mentioned in the Blue Screens are not always the root cause. 1. Windows Defender... should it cause any incompats? 2. Automatic restart is disabled and everything configured. As per your suggestion, I changed "Kernel memory dump" setting to "Small memory dump". That's all what I had different from your list. As I said, BSODs are of various seemingly unrelated types caught in various kernel mode drivers. They usually go away, once I really know which driver might have caused it, and I got it updated. But it's hit and miss (just miss mostly)T due to the mentioned reasons in the beginning of this post. Anyway, to test the OS failure to dump (with the new "Small memory dump" setting), I used the brute force kill switch to the OS... "End Process Tree" on "System" process entry in Task Manager. Yes, I know what this means. So, it BSODs with something like "Crucial kernel thread/process exited or was terminated...", as I expected it to be. As a normal BSOD, it "shows" the progress of a dumping process (which goes from 0 to 100 in Kernel memory dump mode over ~15 secs) and then tells it succeeded and I should contact technical support. I go to the configured dump folder... It's empty. Do a search in the whole %systemroot%, no indication of dump files, except for the pre-7-upgrade Vista dump files (a heap of those which I deleted a while ago). %SystemRoot% now has 11 GB of free space. Worth noting that I've had few to none BSODs lately. But when it happens, the OS feels like telling lies. And, yes, I really want the dumps back. Thanks again.
May 10th, 2010 7:27pm

An answer, that was an answer... not to this thread.
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2010 12:56pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics