Win 7 BSOD and file system corruption after update
Hello! Running Win7 Pro. Yesterday a few updates popped up - a few criticals and two driver updates (controller card and video). After reboot got BSOD. Repair tools indicated corrupt registry. Rolled registry back which allowed starting the system up and booting. However, the system indicates the file system on C: is still corrupt. ChkDisk fails to correct it due to "recently installed software package" and System Restore doesn't work because C: drive is corrupt. Catch 22. How do I get it to actually fix the C: drive? I already know C:\Windows\Prefetch is corrupt and inaccessible. The scheduled chkdsk fails, as I mentioned, to correct anything. Obviously dangerous to use the comp with corrupt file system... Thoughts? Best regards, DZM
August 27th, 2010 4:55am

First of all, remove all unnecessary hardware devices from the computer, try entering Windows safe mode to test whether it is a third-party software/hardware compatibility issue. If so, please download and run Windows 7 Upgrade Advisor to check the reason for the issue. If the issue is caused by some incompatible driver, you might go to Device Manager, right click your hardware device in the list and select Update Driver Software; then click Search automatically for updated driver software. If you still get the BSOD error after installing the latest driver, please understand that Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services). The system goes to a blue screen 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.
Free Windows Admin Tool Kit Click here and download it now
August 27th, 2010 7:59am

Hi, As Andre.Ziegler said, your dump file is necessary, please refer to the following to collect minidump files. 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”. Regards, Miya YaoThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
August 31st, 2010 9:03am

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

Other recent topics Other recent topics