Saved Bookmarks
| 1. |
Solve : Defrag not complete; Safe mode causes BSOD, but XP runs fine....? |
|
Answer» 1. Defrag. Which disk defragmentation software have you used? 1. Defrag. Which disk defragmentation software have you used? How do you know the defrag programs are not finishing the task?Quote from: soybean on December 14, 2009, 07:46:21 AM How do you know the defrag programs are not finishing the task? First of all, they only run for 10 minutes or less. Secondly, when I do a drive analysis by the Windows defrag program it still recommends defragging the drive. And THIRD, the analysis/progress bar show solid color for the first ~20% of the graph, but the remainder is tiny multicolored stripes. But my major concern is not being able to run in safe mode....if I get a virus, I'm screwed, I fear.....Quote from: killerb255 on December 13, 2009, 08:08:07 PM Did chkdsk /r find any bad sectors?killerb, No, no bad sectors. Thx, Lee Last results of chkdsk from event viewer: CHKDSK is verifying Usn Journal... Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. 31768537 KB total disk space. 25785876 KB in 98131 files. 35884 KB in 11699 indexes. 0 KB in bad sectors. 364105 KB in use by the system. 65536 KB occupied by the log file. 5582672 KB available on disk. 4096 bytes in each allocation unit. 7942134 total allocation units on disk. 1395668 allocation units available on disk. Internal Info: b0 ce 01 00 12 ad 01 00 0b 5c 02 00 00 00 00 00 .........\...... c0 00 00 00 02 00 00 00 ba 06 00 00 00 00 00 00 ................ c8 ea 76 03 00 00 00 00 10 ea e5 47 00 00 00 00 ..v........G.... 98 5f 9b 35 00 00 00 00 7e 13 8c 98 03 00 00 00 ._.5....~....... c0 ff 69 67 00 00 00 00 9c 66 fb 84 04 00 00 00 ..ig.....f...... 99 9e 36 00 00 00 00 00 08 39 07 00 53 7f 01 00 ..6......9..S... 00 00 00 00 00 50 d8 25 06 00 00 00 b3 2d 00 00 .....P.%.....-.. 1. Backup Data. Suggest you backup "data" you can't afford to lose while the system is functional. Obviously something is not right, and you don't want to lose data while attempting to fix the system. Safe Mode uses a pretty BASIC set of system files which you've verified with the System File Checker (sfc). I'm not sure what to say: hardware, system configuration, system registry, malware infection? You may be looking at a "repair" install or a complete "new" install. 2. System Restore Point. Do you have any "System Restore" points that predate the "troubles"? Note: I seem to remember READING somewhile that system restore does not preserve "folders" and "files" stored on the desktop. You may want to move them under your user's "My Documents" folder. 3. Memory Dump Analysis. Quote from: GTL on December 14, 2009, 06:46:21 AM 2. BSOD - as you suggest I downloaded and ran BlueScreenView, but it says "No crashes". The c:/windows/minidump folder is empty. Where else might the info be saved? The default location for the "info" is "%systemroot%\Minidump" which on your system is probably "C:\Windows\Minidump". The "memory dumps" may have been deleted by "CCleaner". See if there's a "check" mark for the "Memory Dumps" category. Look on CCleaner "Windows" tab, in the "System" subsection. Also verify your system is configured to generate memory dumps. To access: a. Select "Start" menu. b. Right-click "My Computer"; context menu appears. c. Select "Properties"; "System Properties" windows appears. d. Select "Advanced" tab; tabbed page comes to front. e. Select "Settings" button within "Startup and Recovery" subsection; "Startup and Recovery" windows appears. f. Look within "System failure" subsection: (1) Verify "Automatically restart" box is "unchecked". (2) Within "Write debugging information subsection, verify either "Small memory dump" or "Kernel memory dump" is selected from the pull down menu. Kernel memory dump permits deeper analysis (and still generates minidump to send to Microsoft if desired). (3) Verify "Dump file" location. Default for "small memory dump" is "%SystemRoot%\Minidump"; "Kernel memory dump" is "%SystemRoot%\MEMORY.DMP". %SystemRoot% is an environment variable which resolves to directory path of your Windows installation. For you, probably "C:\Windows". (4) You pick whether to check/uncheck "Overwrite any existing file".Quote 1. Backup Data. Suggest you backup "data" you can't afford to lose while the system is functional. Yes, of course. Quote 2. System Restore Point. Do you have any "System Restore" points that predate the "troubles"?Not really, as I'm not certain when the issues began. Quote The "memory dumps" may have been deleted by "CCleaner". See if there's a "check" mark for the "Memory Dumps" category. Look on CCleaner "Windows" tab, in the "System" subsection. Yes, I thought of that and attempted to boot in safe mode yesterday, days after I ran CCleaner. No data. Quote Also verify your system is configured to generate memory dumps. I checked and yes, it is configured to generate a dump. I appreciate your help....any other ideas? Thx, Lee |
|