chkdsk f does not run at boot Results

Sponsored Links:

In Windows Server 2008 (not R2), I can't find the expected CHKDSK summary record in any Event Log from a CHKDSK C: /F command run at boot time. Does everything now get written to C:bootex.log (which is present)?

In Windows 7 it is found in the Application log, event ID 1001, source WinInit, but there seems (surprisingly) to be no equivalent that I can find in WS2008.

Googling using likely search terms has produced nothing of value...

Hi guys,
I come back to you after some time away in a happy place where tech support is never needed, once again humbly requesting your expertise.

When my laptop hinge busted, I salvaged the HDD and decided to mount it in my next desktop build and use it until I bought another HDD to sell it with. This drive was partitioned with a dual boot of Win7pro64 and Backtrack 5r1 64, both were pretty well maintained, no foreseeable issues with swapping the drive, right?

Well, we seem to be having some technical difficulty, on both fronts. As this is sevenforums, Ill restrict this to my Windows 7 issues, but for any bilingual folks out there that are interested, I'm posting the other half of the dilemma on linuxquestions, sparing them the windows part of it lol. Ill add a link to it once its up.

Okay so here is the hardware setup I am working with.

Asus M5A97 mobo, amd970/sb950 chipset, is rated to support all components
AMD FX-8120 CPU Black Edition
16 GB G-Skill Sniper pc3-12800 ram
XFX nVidia GeForce 6800GT 256MB GDDR3 (I can hear your snickering )
Raidmax 630w PSU
Samsung Supermulti Optical
WD Scorpio Black Laptop SATA HDD

Everything listed is brand new, purchased online, save for the HDD of course. The video card was purchased used at the local computer shop, last-minute.

So just let me explain the nvidia card real fast I planned this build assuming my old HD3870 would work just fine, but it went out on me almost right away. I had it hookup up to a coby tv with a 1366x768 resolution, which is what the nvidia card is powering now as well, via DVI-I output to a DVI to HDMI adapter, then through an HDMI-HDMI cable to the tv, same as the HD3870 was (in case any of that proves relevant). My original intention was to leave this setup open for crossfire if I found another 3800 series. I should note that while the HD 3870 was working, I had booted it up alright and gotten to the boot animation for Windows 7 once. It then proceeded to reboot, after which my video card was toast and I could not get a successful POST. Now that the card is changed, here is what I am experiencing.

When I boot up, I get a POST beep, I go into the BIOS, everything is looking tip top. I select the HDD, everythings still going fine. Since I am running a dual-boot configuration, GRUB is my boot manager. I select the Windows 7 Boot Loader, and I have the option to run startup repair or try to boot normally. I tried the startup repair a few times. The first time it said attempting repairs, then said it would reboot and either boot successfully or continue startup repair. It does not boot up fine, in fact, I get a BSOD. I try the startup repair again, only for it to tell me the problem couldnt be fixed automatically. Well it gives me two options, to either view advanced details in a log file of some sort, or to log in to a user account to run some diagnostic utilities.

The log shows no errors of any kind - I went through each instance of startup repair and they were all negative for each category. There was one "root cause" listed for each attemp which said that 'a recent hardware change' may have caused this to happen. I was told by my college professor who holds an advanced certification for Windows 7 that you could swap a Windows HDD to another computer, and all that would happen is most hardware would default to Windows generic drivers, and you would have some short window of time to reactivate Windows within, due to some sort of built in anti-piracy feature throwing up red flags at the substantial hardware change. Have I been ill-informed, or do I have bigger problems than that?

I logged into my administrative account and the options provided are as follows: Startup Repair, System Restore, System Image Recovery, Windows Memory Diagnostic, and the Command Prompt.
Startup Repair just fails and loops me back, System Restore can't find any restore points (very odd), and System Image Recovery is unusable for me since I never made a backup image. I ran the memory diagnostic as well as chkdsk /f, as advised, and neither found any errors. Selecting the Commant Prompt option, my working directiory is x:windowssystem32. I can switch over to c:, and I can access all of my files, personal, applications, and system alike, which appear to be intact (much of this I have verified via examination from my Backtrack/Linux partition).

Well, I've taken the Windows 7 course, and I don't want to screw around with finding the perpetrator behind my misfortune if I don't have to - I'll just do a side by side install, throw everything on c: into the "Windows.Old" folder, and get the ball rolling on re-crafting my setup, followed by some housecleaning. I have my original product key, all I have to do is pop in that install disc, right? Save the day? I could not have been more wrong.

I actually get a blue screen error while booting from the install disc. This is burnt with an iso obtained from MSDNAA, a legitimate copy of Windows 7 Professional 64 bit, the SP1 Debug Rollup. It's what I used to install the Windows 7 that is currently failing that I'd used for well over a year, and the Windows 7 on another machine I'd built. The serial is registered to me and it was all free through my college. When I did my second install, upon activation I asked if I would need to request a new serial since this one had been used, and was told NO, that my serial is MSDNAA specific, usable as many times as I'd like for academic purposes. You cannot even retrieve these from the system using means that would otherwise produce the correct key - it will come back as five sets of five B's. These are the only two times it has been used and this most definitely does not count as a third since it is the same OS, HDD, owner, serial, and disc even.

Circling back to the BSOD, the interesting thing to me is that the exact same blue screen error comes up while booting my Windwos partition as while attempting to boot from CD to reinstall. Is that significant? I know the terminology sort of clumps them all into the same category, but surely there is a correlation, no? I thought perhaps I was going crazy, and Windows had set some bit switch on the HDD that says "Help, I'm supposed to be in a laptop!" but this does not explain the CD.

I have tried to boot into safe mode, have tried Automatic System Recovery (which im given to understand is the same as Startup Repair), but no cigar. ASR behaves as startup repair did and safe mode = bsod. I have attached a picture of the error screen for reference. I have a copy of Ultimate Boot CD for Windows on my USB drive, but there is a plethora of utils and I dont know how to use most of them. If there is a specific tool that could remedy the issue or shed some light on the situation, I can certainly collect info and report back.


Thanks in advance, all you guys!

Hi, all!

I know how to perform a nondestructive repair install of Windows 7 under ordinary circumstances, but everything I've read so far says that you simply cannot perform that procedure if you can't boot into Windows 7 full mode first (using the hard disk partition that you want to perform the repair install onto). Even Safe Mode just won't cut it, apparently.

But since I'm now always getting the dreaded "Black Screen of Death" (not its Blue cousin), the nondestructive repair install option is reportedly out of the question...

So my question is: Is there ANY workaround that would allow me to perform a nondestructive repair install anyway, even if the procedure is difficult and/or requires third-party tools, either freeware or commercial?

For just one possible alternative, would booting from an old backup partition on a separate USB harddisk allow me to do a repair install on the internal HDD & partition with the Black Screen problem? If so, how?

I realize that I could rewrite the internal disk partition that causes the Black Screen with the backup partition I just mentioned (and then run the repair install), but of course that would destroy all the updates and changes I've made since the backup, which is exactly what I'm trying to avoid by doing the nondestructive repair install in the first place!

I also realize that if I were able to fix the Black Screen problem in the first place, there would be no need to do a repair install. Unfortunately, nothing I've tried has worked! Here's what I've already tried that have failed...

I booted up with the installation DVD and tried "Startup Repair" (in fact, I tried it three times in a row, as one site recommended), but that always fails with the message "Startup Repair cannot repair this computer automatically" with one of the problem signatures reading "MissingOsLoader". I found dozens of support sites explaining how to fix that, including:Use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows,

BCDEDIT - How to Use,

Command Prompt - Repair Missing or Corrupt Files,

How to Fix Windows 7 When It Fails to Boot,

Windows 7 will not boot past Starting Windows or in Safemode,

Troubleshooting Windows 7 Failure to Start,

Windows 7 does not boot into any mode (Normal or safe), neither the Recovery partition nor the recovery discs work,

Failed to Find OS Load. Startup Repair FAILED,

Automated Startup Repair fails. Cannot find OS Loader.,
...but I've tried everything they've suggested and nothing yet has solved my problem.

I've even tried the "Nuclear Holocaust" option described in this very good tutorial from the makers of EasyBCD: Recovering the Windows Bootloader from the DVD, but even after doing all that, the Black Screen always appears when I try to boot (even from Safe Mode and Safe Mode with Command Prompt, etc.)

For the record, I've tried using System Restore with either of the two recent Restore Points, but no luck there (the older restore points were too old). I've also tried booting with the "last known good configuration", but the results were the same. I also ran "CHKDSK C: /F /V /R", which found and repaired a single corrupt sector, and when I ran it again, no problems were reported. Also, I ran "SFC /scannow /offbootdir=C: /offwindir=C:windows" a few times and it found and reportedly repaired a few problems. Here's the log's contents:

Code: 2013-02-09 03:03:45, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 03:03:45, Info CBS Starting TrustedInstaller finalization. 2013-02-09 03:03:45, Info CBS Trusted Installer core was not initialized. 2013-02-09 03:03:45, Info CBS Ending TrustedInstaller finalization. 2013-02-09 03:51:57, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 03:51:57, Info CBS Starting TrustedInstaller finalization. 2013-02-09 03:51:57, Info CBS Trusted Installer core was not initialized. 2013-02-09 03:51:57, Info CBS Ending TrustedInstaller finalization. 2013-02-09 03:55:06, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 03:55:06, Info CBS Starting TrustedInstaller finalization. 2013-02-09 03:55:06, Info CBS Trusted Installer core was not initialized. 2013-02-09 03:55:06, Info CBS Ending TrustedInstaller finalization. 2013-02-09 05:48:21, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 05:48:21, Info CBS Starting TrustedInstaller finalization. 2013-02-09 05:48:21, Info CBS Trusted Installer core was not initialized. 2013-02-09 05:48:21, Info CBS Ending TrustedInstaller finalization. 2013-02-09 05:59:58, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 05:59:58, Info CBS Starting TrustedInstaller finalization. 2013-02-09 05:59:58, Info CBS Trusted Installer core was not initialized. 2013-02-09 05:59:58, Info CBS Ending TrustedInstaller finalization. 2013-02-09 08:38:21, Info CBS Failed to initialize COM security. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE] 2013-02-09 08:38:21, Info CBS Starting TrustedInstaller finalization. 2013-02-09 08:38:21, Info CBS Trusted Installer core was not initialized. 2013-02-09 08:38:21, Info CBS Ending TrustedInstaller finalization. I don't know what to make of any of that, however. But remember that the SFC scans were all done from the Win 7 Install DVD command line, so there was no networking in place and apparently the install DVD repair tools don't run with the "Server" or RPC services running, which perhaps explains those error messages.

If anyone's interested, I've attached a zip file named that contains two files: bcd.txt - which is the output from the bcdedit enum all command, and ntbtlog.txt - which is a recent boot log (from using F8 to boot with boot log option).

So now I'm pretty close to my wit's end, but I still absolutely LOATHE the idea of perfmoring a fresh new re-install, which -- considering all the third-party applications and such I'd need to re-install -- would require at least a week of horribly tedious work!

That's why I'm desperate to find a workaround to this baffling limitation imposed on doing nondestructive repair installs on MS operating sytems more recent than XP.

Any suggestions, folks? Attached Files (12.1 KB, 5 views) Last edited by Ninethe; 02-13-2013 at 08:06 AM. Reason: Added log zip file attachment Share Share this post on Digg Technorati Twitter
Operating System Windows 7 Home Premium 32-bit (Not SP1 yet)
Computer Type Dell Inspiron 1526 Laptop
OS Service Pack SP1 (build 7601)
Internet Explorer Version 8
DirectX Version 11
CPU Type and Speed AMD Turion 64 X2 Mobile TL-60 - 2GHz
CPU Cooling (on board)
CPU Idle Temp ~ 140 F
CPU Load Temp ~ 165 F
Motherboard Chipset Mobo: Dell Inc. 0WP019 - Chipset: N: ATI RS690/RS690M - S: ATI SB600 rev. 00
System BIOS Revision A16
System Memory Type 2 GB DDR2
System Memory Speed 332MHz
System Memory Clocking 5-5-5-15
Video Card Type and Speed ATI Radeon X1200 Series - 27000 HDMI
Video Card Cooling (on board)
Video Card Temperature (not reported)
Sound Card IDT High Definition Audio HDMI
Hard Drive 250 GB WDC WD2500BEVS-75UST0 Sata
Optical Drives PBDS DVD+-RW DS-8W1P
Network Adapter NETGEAR WNA3100 N300 Wireless USB Adapter
Network Speed 50 Mbps
Anti-virus Software Avira 2013 / Comodo Firewal
Computer Skill Level Self-Taught Expert
Reply With Quote .postbitlegacy .postfoot .textcontrols a.post_info_button, .postbit .postfoot .textcontrols a.post_info_button { background: url(/images/post_infobox.png) no-repeat transparent left; padding-left: 20px; } .postbitlegacy .postfoot .textcontrols a.post_info_button:hover, .postbit .postfoot .textcontrols a.post_info_button:hover { background: url(/images/post_infobox-hover.png) no-repeat transparent left; JavaScript must be enabled 02-13-2013 #2 patcooke Tier 2 Moderator Microsft Most Valuable
Join Date May 2010 Age 67 Posts 2,167 Re: Is there ANY workaround for Win 7 nondestructive repair install when unable to boot? Black screen is cause by failure to access a critical system file - usually because it is missing/corrupt etc or because it has been compressed. If you can identify the mising frile from any report to the screen during failre you may be able to replace it. Failing that the prospect of reinstalling all from scratch (loathsome though it may appear) may be as nothing compared with the spectre of interminable problems raised by what seems to be a system which has suffered serious corruption and sooner or later would require a clean reinstall which in the long term I reckon is to be the lesser of two evils. I get the impression this problem has already consumed significant time, effort and head banging! For the future I would strongly recommend you look into implementing a regular backup regime of imaging your system drive on a regular basis using something like Acronis True Image. You can download a full working trial copy, it is not expensive and the very first time you need it (incircumstances such as this) it is worth every penny. It is also insurance against total hdd failure, bad malware infection, bad installs and host of other evils.

Chad, Thank you for your posts…

Please comment.

I just put together my first computer with all top brand hardware pieces…
nothing OEM .. except the Windows XP with SP2 disk…

I installed everything okay.. installed all the drivers that came with the
hardware… only one that said it wasn’t MS approved.. was the View sonic LCD
monitor… Also, I don’t have any printers or scanners hooked up to the
computer… just trying to get it running clean… (Note: I don’t own an Astra

I have creative Sound Blaster Audigy 2zs … but my sound wasn’t working… so,
I went into device manager and selected the sound card.. updated the driver
with the disk in the drive.. and it worked, I had sound…. But somewhere after
that it started that reboot continuously thing… long story short.. I have
wiped the drive and started over 5 times… and found that article on the UMAX
driver… and searched for it on my system and found the .dll

I have been racking my brain to figure where I got it.. I scanned all the
disks… except for the Windows XP sp2 disk, and no luck… where I am getting
it… then I checked on the WinXP disk… sure enough it’s on there!! Why?? If
they don’t support the driver why is it in their

It has been consistent in failing after I have windows install that one
driver… I don’t require Windows to install any other drivers.. just that
sound card one.

ALSO … I thought this was weird.. the umax.ini file was created at 2:55am..
I went to bed at 2:30am.. (trying to work on this) and I had left it
reformatting the drive and installing XP. When I woke… I had the blue screen
error message… waiting for me to read it.. I ended up reformatting again…..
at about 9:30am … so that umax.ini file should have been wiped… I don’t get
it. .. I did let Windows do the formatting.. and not fdisk… which I thought
would be the same.

I am reformatting again… and thinking .. maybe don’t install all the
drivers… OR … maybe let windows do all of them.. OR … update windows as soon
as possible.

The service pack in embedded on the disk.. so I can’t tell when it is

I really want my system to run at the best optimum capability it has. I
would think installing the drivers and utilities would do that. ARGHHH!!

"Chad Harris" wrote:

Guy with late homework--

See if a UMAX driver could be the problem via this KB:

After you install Windows XP Service Pack 2, your computer restarts

Over-heating, and a bad stick of RAM have been known to cause this--so if
software remedies don't do it, look to hardware, memory sticks in place,
cables, ect.

*Often, booting to the Recovery Console and running chkdsk /r will help this
problem.* I don't know if you have an XP CD, because lately so many people
with boot problems have not had one supplied by their OEM, but if you do
this would be my first choice to try to ditch the endless loop this way.

Description of the Windows XP Recovery Console;en-us;314058

Scroll down for instructions on running chkdsk /r.

Using the Recovery Console

RC Overview

Recovery Console in XP

I didn't know if you could break the loop to F8 as Will says. In my
experience, Last Known Good Configuration almost never works statistically,
but if it does and this is gone, more power to you. Keep in mind that it's
a snapshot of your configuration immediately after you booted, so if you
have been booted up for a long time then you're not going to track settings
changes since that time.

I'd first try to F8 to the Windows Advanced Options menu and use Safe Mode
and then try System Restore from Safe Mode. You will probably be back at
the version before you installed SP2. There is also this option for aborted
SP2 installs or SP2 installs with the problem like the one you're having,
but again System Restore may not solve your endless loop problem and Last
Known Good may not. You may need to run a chkdsk /r or use some of the
other tools I describe.

Resources for troubleshooting startup problems in Windows XP (Info on F8 and
Advanced Options Menu)

How to use the Automatic Recovery feature to recover your computer if the
Windows XP Service Pack 2 Setup program is not completed successfully

A description of the Safe Mode Boot options in Windows XP

If you were unable to use the Recovery Console because you had no XP CD, and
haven't installed it already but could get back to Windows:

If you can tap F8 to get back to Windows via either Safe Mode or as a last
resort in my opinion, Last Known Good Configuration, then you're still faced
with the possible "endless loop problem." That's why my first suggestion
was to boot to the Recovery Console and run chkdsk /r from the recovery

You would be possibly faced with the endless loop proble again or when you
installed SP2 so I would run chkdsk /r from the command prompt or the run

The reason for the endless loop is often that something has set the volume's
"dirty bit." When a volume's dirty bit is set, autochk automatically checks
the volume for errors the next time the computer is restarted.If a volume's
dirty bit is set, this indicates that the file system may be in an
inconsistent state. The dirty bit can be set because the volume is online
and has outstanding changes, because changes were made to the volume and the
computer shutdown before the changes were committed to disk, or because
corruption was detected on the volume. If the dirty bit is set when the
computer restarts, chkdsk runs to verify the consistency of the volume.

See if you have any disk corrpution by typing "fsutil dirty query [C]: Sub
any drive you want for "C". If it says the volume isn't dirty, you don't
need to run chkdsk because there aren't any errors on the disk. But I know
you want to run it to see that it runs properly without this read-only
error. The KB I'm going to list advises you to run "chkdsk volume_label: /v
/f" to fix this. This will fix any errors on the disk and the "v" causes it
to name each fixed file. Hopefully that will resolve it.
But if it doesn't then run "chkdsk_volume label: /r", and if that doesn't
then run the chkdsk /r from the recovery console.

If the disk is dirty, then System Restore is not going to fix that.

Every time Windows XP starts, Autochk.exe is called by the Kernel to scan
all volumes to check if the volume dirty bit is set. If the dirty bit is
set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f
verifies file system integrity and attempts to fix any problems with the

Here's what to do:

Go to Start/Run/CMD and type in: fsutil dirty query c: (or whatever drive
his XP is on). You'll get back either the drive "is dirty" or "it's not

Info on a "Fsutil Query" in the KB below--also see the Explanation at
Windows Help and Support--type "helpctr" into your run box:

The Fsutil Query Tool:

An Fsutil Query Does Not Work Properly on FAT or FAT32 Volumes

You have 4 choices that may work:

1) You can run chkdsk /r from the Recovery Console. I think this is the
fastest and most effective. I've seen it work for this several times.

2) You can run the chkntfs /d and reboot and chkdsk won't run on the next
boot. What this does is to restore default settings. Note this is a
different command than chkdsk. Chkntfs is a command that displays or
specifies whether automatic checking is schduled to run on a FAT, FAT32, or
NTFS volume when the computer is started.

3) You should be able to fix this by using "chkntfs/X C" if C were the
problem drive or whatever letter--this works when the drive is dirty and I
showed you above how to verify this. The advantage of sticking the X in the
command is that it saves time by causing the command to skip checking cycles
within the folder.

4) You can go to Kelly's XP Tweaks and click line 76 left column and see if
this VB script will stop it.

Kelly's Tweaks

Troubleshooting Windows XP

In addition, When there is improper shutdown, the Autochk program runs on
all NTFS drives in XP, 2K, NT where a disk write was in process at the time
of shutdown. This gets exacerbated if you have write caching enabled on a
hard drive connected to a standard IDE controller. It improves performance,
by delaying data writing while other work is done, but it ups the risk of
lost data or corruption.

Open the run box with the Windows Key + "r" and type in diskmgmt.msc. From
the graphical display in the bottom of the Disk Management window,
right-click the disc icon and chooose Properties. On the policies tab, clear
Enable Write Caching on the Disk. (Note this option, ie. the policies tab,
may not be available if your disk is connected to a High Performance ATA-66
or ATA-100 IDE controller.)

After you find the cause of the underlying problem if there is improper
shutdown, re-enable write caching.

Additional references for definitions context:

Chkdsk.exe or Autochk.exe starts when you try to shut down or restart your

An Fsutil Query Does Not Work Properly on FAT or FAT32 Volumes


Chad Harris

"Guy with late home work" Guy with late home

I've a customer who has the same problem and I've waiting
to see if someone replied to this post for a fix. The
customer had a trojan removed from their PC and then
started receiving the same message whenever they tried to
run a dos program. When I started the machine in safe
mode everything worked fine. Today the PWSteal.Banker.B
trojan was reported by norton's on this computer which I
removed. This trojan was only discovered on June 17 and
is not supposed to affect XP. I decided to try running and sysedit to see if removing the trojan had
any effect on this problem. Much too my surprise and
relief it did. Hopefully this might help you if you go to
symantec's sight they have the information needed to
remove the virus. The file that the virus creates is
lsd_f3.dll in the system32 folder. Let me know if this

-----Original Message-----
I apologize for the lengthy post.

I'm running win xp pro (system came with win xp, I
upgraded immediately to
win xp pro. This current problem has nothing to do with
the upgrade to win
xp pro, which was done over a year ago) on an e-machine
T2625 AMD Athlon xp
2600+ 2.12GHz, 1GB RAM.
Note: My computer came with the primary partition
(system partition, C:
drive) configured to NTFS. All other partitions that I
have created on that
physical hard drive and on other physical hard drives
are FAT32.

A week ago, I had just finished fully cleaning my system
(a long process)
and then went to play tetris and BAM! A new problem. How
nice. I have a
number of dos programs, including tetris.exe, some old
astronomy dos
software, etc. which have worked fine on win xp pro for
quite some time
until recently (the last week) when they collectively
began to fail with an
"attempt to access invalid address" error. I cannot
ascertain the exact time
at which this problem began since I only use the DOS
programs infrequently.

Information which may be helpful:
The first thing I did was Google search with the
following string: "attempt
to access invalid address" xp dos.
This search brought some (perhaps) useful info, which I
will relay he

"Andrew" on June 02, 2004 said "Todays morning, after
one hour of work I
needed to restart computer becouse I was not able to
disconnect from
internet. There was no activity but it was not
disconnecting. After that I
can't start any DOS program on this computer, any dclick
in icon to program
is giving error: "Attempt to access invalid address".
When I try to run DOS
program from command prompt window I see : "Cannot
execute program". I scan
comp. for viruses - it did not find anything. Any sug.? "

"Bill Mason" on June 08, 2004 said "I currently have a
similar problem to
what you descibed. I found that if I start Windows in
the "safe" mode I can
then access what I need to. This is not a satisfactory
solution for me. I
would greatly appreciate any better cures if you are now
aware of any.
Thanks! "

"Christopher" on June 15, 2004 said "Same symptoms, XP
Pro. User reported a
few xxx popups while downloading NAV2004 just prior to
problem. Checked her
index.dat file and found NO record of browsing anything
but okay sites.
Tried NAV2004, Adaware, Spybot, TrojanHunter, turning
off servies, msconfig,
logged in as Administrator, checked config.nt and
autoexec.nt, nothing
worked. Finally had to use XP system restore and roll
back 3 days. Maybe
something nailed the Environment Variables ? Didn't
think to check those
until after restore. "

"manu (by manu24)" on June 30, 2004 said "same prob.
here with win xp home,
but sometime back i turned off my system restore for
some reason and forget
to turned it on, so now i cannot roll back, so what do
now? any suggestions.
manu "

end of thread

"akinsey " on June 7th, 2004 said " I have a user who is
running XP Home on
a newer HP Pavilion, which had a bad hard drive and was
replaced a week ago
under warranty at Best Buy. She cannot use any DOS
programs under XP, even
using any of the available compatibility modes. HOWEVER,
there was no
problem with ANY DOS programs running under XP prior to
the drive being
1) MS KB searches on DOS Compatibility Problems in XP
point to NTVDM
configuration problems. I.E.:
When you have problems with MS-DOS programs:
Test the NTVDM (Windows Virtual DOS Machine) subsystem:
1. Start / Run / / OK.
2. If a session does NOT
open, the NTVDM is
misconfigured. Check the Config.nt and Autoexec.nt files
in the
%SystemRoot%System32 folder for non-standard entries...
[snip] (enter) yields the error "attempt
to access invalid
address". (see attachment, error.JPG)
All appear in the windowssystem32 folder. I looked at
the config.nt and
autoexec.nt files and they're pure, exactly as extracted
from the XP cd.

"Paladisious" on July 1st, 2004 said "The exact same
thing is happening to
me in Win XP Home, except I formated my machine, and
since then I've
reinstalled windows and all those lovely classic DOS
games, but that
'invalid adress' error keeps coming up when I try to run

"noseBleeD " on July 1st, 2004 said "I am fairly sure
when it says the
address is invalid, it means it has gone beyond the end
of the memory
registers that are assigned to the program you are
trying to run.
Does this happen in safe mode?
This could be caused by a memory leak.
This could be caused by a bad virus that harmed your
hdd, and ram, or video
ram, or more.
I would verify the above posts like you said concerning
the winXp version
first, then try safe mode and see if problem still exist.
I would then boot into recovery console and run
chkdsk /f command.
I would the test memory with other known good memory and
if good, add more."

end of thread


"fcoen " on June 16, 2004 said "I have recently re-
installed windows 2000
server, but now all the dos programs that used to work
on it give an error:
"attempt to access invalid address". Not only that but
things like the edit
command give the same error. Any suggestions. Thanks. "

"MaddMaxx" on June 16, 2004 said "Did you switch from
FAT32 to NTFS?"

"fcoen " on June 17, 2004 said "yes..."

end of thread


"stevewdindas" on 06/09/2004 said "I have notebook that
has had and repaired
a number of viruses. However, even though it is
reporting clean after
several different scans whenever I try to run most .exe
applications it
reports the error "Attempt to access invalid address".
I have tried the
programme in safe mode and it works. Any suggestions?"

end of thread

"manu (by manu24)" on July 01, 2004 said "Hi, my comp
got hijacked with some
xxx dialer n dl.html file etc and some trojans. i got
rid of those now i m
facing this problem when ever i click some dos
application like my turbo
c++.exe or some other dos application i got this
error"Attempt to access
invalid address". unfortunately some time back i turned
off my system
restore so i m unable to rool back my system. plz help
me, ne suggestion
will br g8tly appreciated. Manu using win xp"

end of thread.

The most useful fact which I gathered from these threads
is that this is a
recent problem (Note the dates of the posts), since I
have tried many other
searches on Google, other search engines, and usenet
groups such as this and
found no other references to this problem. Therefore the
only references to
this problem are recent. This indicates to me that we
are dealing with a
virus, trojan, or malware which has began to show its
effects only in the
last month or so. Further evidence for this being a
recent virus is that
none of the above referenced threads includes any
definite answers or
solutions, just people trying to find answers to
(roughly) the same problem
at (roughly) the same time, indicating (to me) that this
is a new virus or a
new version of an old one.

MY Hijackthis log is clean:
"Logfile of HijackThis v1.97.7
Scan saved at 9:15:56 AM, on 7/2/2004
Platform: Windows XP (WinNT 5.01.2600)
MSIE: Internet Explorer v6.00 (6.00.2600.0000)

Running processes:
C:Program FilesStop-the-Pop-Up Litestopthepop.exe
C:Program FilesAVPersonalAVGNT.EXE
C:Program FilesAVPersonalAVGUARD.EXE
C:Program FilesAVPersonalAVWUPSRV.EXE
C:Program FilesAheadInCDInCDsrv.exe
C:Program FilesCommon FilesMicrosoft
C:Program FilesNorton UtilitiesNPROTECT.EXE
C:Program FilesSpeed Disknopdb.exe
C:Program FilesInternet Exploreriexplore.exe
C:Program FilesOutlook Expressmsimn.exe
C:Program FilesHijackThisHijackThis.exe

R1 - HKCUSoftwareMicrosoftInternet
ExplorerMain,Start Page_bak =
O4 - HKLM..Run: [NvCplDaemon] RUNDLL32.EXE
O4 - HKLM..Run: [NeroCheck] C:WINDOWSsystem32
O4 - HKLM..Run: [sureshotpopupkiller] "C:Program
Litestopthepop.exe" -minimized
O4 - HKLM..Run: [AVGCtrl] C:Program
FilesAVPersonalAVGNT.EXE /min
O4 - HKCU..Run: [NvMediaCenter] RUNDLL32.EXE
O4 - HKCU..Run: [ctfmon.exe] C:WINDOWSSystem32
O8 - Extra context menu item: &Define -
O8 - Extra context menu item: &Search the Web -
O8 - Extra context menu item: E&xport to Microsoft
Excel -
O8 - Extra context menu item: Look Up in &Encyclopedia -
O16 - DPF: {74D05D43-3236-11D4-BDCD-00C04F9A3B61}
(HouseCall Control) -
O16 - DPF: {9A9307A0-7DA4-4DAF-B042-5009F29E09E1}
(ActiveScan Installer
Class) -
O16 - DPF: {A3009861-330C-4E10-822B-39D16EC8829D}
(CRAVOnline Object) -"

I have already performed all of the usual tasks
associated with a difficult
1. Ran online panda-antivirus, trend micro, ranta-
antivirus, downloaded and
ran free AVG antivirus, then uninstalled it, and then
downloaded and ran
free AntiVir. Ran all of these again in safe mode except
for AVG free, which
doesn't like winXP safe mode and can't find core driver.
That's nine virus
scans which found nothing (due to the fact that, just
prior to noticing the
current problem, I had just run all of these scans and
more as part of
monthly maintenance).

2. In safe mode, and then again in regular mode, deleted
all files in the
following directories: Temporary Internet Files (for all
users, verifying it
to be empty, verifying that Content.IE5 was either empty
or deleted, for
each user and Admin and 'All usuers' and 'default user'
and localservices
and networkservices); Cookies; Windows/Temp;
Windows/Downloaded program
files (except for those downloaded program files
associated with the online
virus scanners); windows/prefetch; Windows/web;
C:recycler (except for
S-1-5-21-760979014-647424850-2722162428-1005, the actual
recycle bin, which
it won't let me delete); and then ran accessories|system
tools|disk cleanup
on all drives, in both regular and safe mode, deleting
everything which I
could (but everything was empty by then - in, fact,
everything had already
been empty because I had already done all of this just
prior to noticing the

3. Ran SpyBot search and destroy and Ad-Aware in regular
and safe mode.
Already clean.

Some things of note:
1. Since my primary partition (system c: drive) came as
NTFS, I have never
been able to access it directly when in DOS mode or when
booted from a DOS
floppy, since DOS can't recognize NTFS, so recently,
having finally grown
annoyed enough to do something about it, I searched the
net and downloaded
'ntfsdos', a DOS program which acts as a file system
driver for DOS/Windows
and that is able to recognize and mount NTFS drives for
transparent access.
It makes NTFS drives appear indistinguishable from
standard FAT drives,
providing the ability to navigate, view and execute
programs on them from
DOS. It is an older program which was apparently
necessary in the days when
FAt32 windows couldn't recognize NTFS. I mention this
merely for the sake of
completeness, since none of the other people in the
above referenced threads
mentioned this ntfsdos program, which is a relatively
rare program, and it
is unlikely that it would be present on any of their
systems, and therefore
unrelated to the present problem. However, one post
asked if the person had
changed from FAT32 to NTFS, but didn't explain why he
thought this might be
important, and although I didn't change from FAT32 to
NTFS, I just thought
I'd mention that I ran this NTFSDOS program so as to be
able to access NTFS
C: drive from DOS.

2. As suggested in one of the above-mentioned posts, I
ran, but
got the error "attempt to access invalid address". All
the usual dos
programs and associated files are present in system32
folder, and config.nt
and autoexec.nt appear to be fine.

3. My DOs stuff works fine in safe mode.

4. I don't seem to have the recovery console, or at
least I don't see it
listed when booting.

5. A month ago when last cleaning the system, I turned
off system restore
before running the virus scans, as always, but forgot to
turn it back on, so
if I want to restore windows I'll have to go back at
least a month. I'd
rather avoid that.

Sorry for the long post.
Any help is appreciated.


Hello Everyone,
I have an old issue with a new twist, for me at least. I'm hoping someone has an idea.
This home office PC has suddenly begun running CHKDSK at startup on every boot and only on the D: partition. The C: partition stays "clean". No errors are found by the chkdsk run. Running CHKDSK /f /r or the version from the My Computer>Disk D>Properties>Error Check does not fix the problem. Using CHKNTFS /X D: does not prevent the chkdsk at startup either; neither does fixing the "BootExecute" line in the registry. Running Recovery Console does fix the problem.........until the next boot.

I'm thinking some some application or service is not shutting down properly and leaving a bit open somewhere and causing this issue. My question is if anyone knows any trick, other than trial and error (of course ) to try to pin the the (possibly) offending application or service. I suppose I can just go through Task Manager stopping 5 or so processes until the problem stops (possibly).

Anyway, as always, thanks for any suggestions, and enjoy daylight savings time this weekend!!

I was getting BSOD and freezeups/slow downs on my Vista machine and did the easiest (but most expensive fix) - I upgraded by doing a new build.

Windows 7 x64
Intel i5-750 Lynnfield on a Gigabyte P55A-UD4P mobo
8 GB (4x2GB) Corsair DDR3 1600
OCZ Vertex 120GB SSD for the system drive
2 - 1TB WD Green (1 EAD and 1 EAR - my bad on the EAR, as I had to do a 7-8 jumper to get it aligned)
Asus ATI EAH5780 1 GB videocard
Corsair 750W PSU

Software Loaded:
NIS 2010 (Norton - I know, most people think it's crap)
Various software: Quickbooks, Adobe PS CS4, Foxit, WinRAR, TeraCopy, VLC player, etc.

I ran Windows Update and updated all the drivers I could (curiously, the Gigabyte Motherboard DVD would not run under W7...) including chipset, Realtek, IDE, USB, etc. I DID NOT flash the BIOS - I figured it was the latest since it was so new).

I followed some "tweak" recommendations for the SSD and Windows 7:
Disabled defrag, superfetch and prefetch, drive indexing on the SSD (some of these W7 does auto)
Reduced the Page File size, moved some folders off the SSD (like "My Music", etc.)

I also tried to set up the drives as AHCI instead of IDE even though I won't do a RAID (I have a Windows Home Server for backup and storage); however, I didn't do it initially, and I made a regedit change and then changed the BIOS to the AHCI. I couldn't get that to ever boot so I changed back to IDE.

The BSODs started randomly, maybe after the AHCI but maybe before. Various problems:

I am running the Windows Memory Diagnostic Tool now (it takes forever - actually I think IT HAS FROZEN too!) and I have the memtest86++ disk to test afterwards. If that is OK, I read to go into the System logs in Event Viewer and use chkdsk /f/v.

Is there something else to do? I'm not sure how to look at a minidump (that's what I feel like doing to my PC right now).

Thanks in advance for your help. I really don't want to do a re-install unless I know it's not a hardware issue!

Hi, I have been getting the little popup blip from the taskbar saying it has found a file or folder that was "Corrupt and unreadable, please run chkdsk".
I have run chksdk /f /r from the recovery console and windows and it finds and fixes corrupt or incorrect files.
On the next boot I can scan the file trees and the blip will pop up again saying the same thing but a different file or folder.

I figured my windows install was corrupting so I did and in-place upgrade hoping that would fix it, it did not. I have also tried sfc but it doesn't finds any errors.

The files are un openable and chkdsk does fix them.

My computer runs pretty bare so there isn't anything writing or reading at these files unless I am directly accessing them, the popup only occurs when I run something that tries to access them.

What would be causing my files to constantly corrupt like this?


64bit win7