hi all!
i have windows 7 64 bit on my system. for a couple of months now, my pc has attempted to do a full c:/ chkdsk on each startup. even if i let it scan and it does not find errors, it runs into the same procedure the next time. i tried to fix everything by chkdsk /f /r c:/ . no problems, yet chkdsk again:
ideas anyone?
btw: i use panda cloud firewall.
regards,
markus
To fix this you have to go into the Registry as outlined by Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows: http://support.microsoft.com/kb/322756
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
In the right hand pane, double click BootExecute.
The default value of the key is autocheck autochk *
* means every drive is checked for consistency. Just add /K:C at the end before *. /K switch will disable autocheck on C: drive at Windows startup. So the final value should look like this:
autocheck autochk /k:C *
If you want to add more drives, the key should look like this: (disabling C and D drives)
autocheck autochk /k:C /kD *
If you want to restore everything to default, just replace the key with the default one i.e.
autocheck autochk *
See also: Check Disk - Reset
Last edited by Brink; 21 Jun 2010 at 10:14. Reason: added link
ok - that would be a terminal solution, so to say.
i am asking myself if there is a method to track down the problem, why this strange behavior occurs at all and then go hunt the evildoer
regards,
markus
Me and one of my friends (also on Win 7 Pro x64) are having the same problem. Suddenly, for no reason, chkdsk on every boot.
I just discovered this discussion and forum in a Google search for the strings "dell xps chkdsk boot" and just joined. Although this discussion is a few months old, I would like to reopen it.
I have been having the same problem almost since I first turned it on. I will say that fishnbanjo's solution overlooks the root problem. I want the OS to check for problems because I want to solve the problem. In fact, the System Event Viewer shows that NTFS errors are occurring all the time on my machine. As a result of this, I cannot defraqment my drive (not that I really need to right now) and I cannot shrink toe partition. Now that is something I really DO need to do if I want to install another OS.
Thus far, Dell has offered to send me a new drive, already imaged exactly like mine was when they shipped it. This is also ducking the issue, besides being a great pain in the nether regions of one's anatomy to restore everything I have done so far. (Plug-Ins, registered commercial software, registered MS-Office etc)
Here is an example of one such an error report from the Event Viewer, in XML View:
-----------------------------------
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Ntfs" />
<EventID Qualifiers="49156">55</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-11-16T00:44:09.980327800Z" />
<EventRecordID>75267</EventRecordID>
<Channel>System</Channel>
<Computer>Maxwell</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>OS</Data>
<Binary>06000C000200380002000000370004C000000000020100C09000000000000000000000000000000028041400403D 00000000FD05</Binary>
</EventData>
</Event>
--------------------------------
Anyone have any idea on what this all means? It might help track down the problem, allowing it to be fixed with far less trauma.
Thanks
Rasputin Paskudniak (I'll add my cute sign-off later.)
PS: How to run the event viewer:
Start Button -> Contol Panel -> Administrative Tools -> Event Viewer
Check your ACHI drivers... I had that problem too, in the event viewer also I was having a problem with the controller of the device (error 11 AFAIR), I had to reinstall my wndows (just because I felt that my old setup was slopy and I did a wipe in my HDD) but for you, uninstalling the ACHI driver may help, the default windows driver will work for you, that or maybe you can update that...
If your system keeps dong nasty stuff... wipe your HDD (SSD / HDD : Optimize for Windows Reinstallation), reinstall windows and NEVER install your last ACHI drivers, get either an stable update or stay with the default ACHI controllers provided by Microsoft. As far as I remember, error 55 is an error in the ntfs fle system (maybe MBR is corrupted) and is logged along with error 11 (Disk) and another one that may vary depending on your ACHI controllers installed (for me, amdsata.sys was the responsable)
I hope this helps.
See ya!!!
FerchogtX,
First, how do I pronounce your moniker?
(ACHI: I assume you meant AHCI. I edited this post to correct my reply.)
OK, I had to search Google to find the Wikipedia entry for AHCI - Advanced Host Controller Interface, a technology developed by Intel. I don't know if it applies to my AMD-based machine but I'll leave that out of the discussion for now.
The suggestions you made sound scary enough - I might have to wipe my HD and reinstall Windows-7, and carefully choose the drivers that get installed. This means I would have to carefully monitor an hours-long custom install and answer a lotta questions.
But I might get by if I merely uninstall my AHCI driver(s).
Pard'n me, Guv'ner, but how does a body do that? (I sometimes lapse into Cockney when someone makes me feel stupid.) I did go into
Control Panel -> Device Manager -> Disk Drives -> Samsung HD103SJ
A right-click -> Properties found that the drivers date from 6/21/2006 and offers me the chance to update the driver. When I click on [Driver Details] it lists:
- C:\Windows\system\DRIVERS\disk.sys
- C:\Windows\system\drivers\partmgr.sys
but I don't see AHCI anywhere.
So how do I get there from here? And I WILL have to back up everything before I take that kind of risk; we all know that a device with no driver is as useful as a pet rock, only worth less money.
Thanks mucho.
Last edited by rpaskudniak; 18 Nov 2010 at 01:12. Reason: Correct spelling of a 4-letter acronym
I have stopped seeing the NTFS errors (Event ID 55, Task Category 2) since 10:00 PM last night. What did I do? Well, it's not for the faint of heart. And the usual disclaimer applies: Back up your vital data before doing this!
I downloaded System Rescue CD (SystemRescueCd-x86-1.6.3 (274 MiB) last week and finally burned a CD from the ISO file. I booted the CD and just peeked around. (Lookie Louie, that's me! :)) By the way, it boots a version of Linux.
The most invasive thing I did was to mount my C drive in read-only mode with the command:I was too chicken to try anything more. I was looking for a file-system repair utility but did not find it.Code:# mount -t ntfs /dev/sda3 /mnt/windows -o ro
I also looked into gparted, the Linux partition editor, again without effecting any changes.
The unexpected result was that when I rebooted windows, it did not go into chkdsk. And when I looked at the Event Viewer report, as I was writing this little missive, there are no NTFS errors since last night, before I booted the CD.
Note that in order to boot the CD, I had to press F2 as the machine was starting up, before Windows loaded, and change the boot-device order so that the BIOS tries the CD drive first. Hey, I said it's not for the faint of heart. But it is a great deal more innocuous than wiping the drive and reinstalling Windows. And if you mess up with the System Rescue CD, you can still have that other fun.
I will reserve judgment on whether the problem is solved until I see that the problem stays away for a couple of weeks. I'd also like if someone could post a link to more information about AHCI and how to administer it.
BTW, is there a way to flag a thread in this forum as solved, besides sticking the word into the title?
In your AMD system has a lot to do if you have AHCI enabled in your bios, which means that windows will also work on that mode, using the matching drivers... this mode is not exclusive for intel systems, AHCI was implemented on AMD motherboards too, my laptop has this technology despite is an AMD M780 chipset.FerchogtX,
First, how do I pronounce your moniker?
(ACHI: I assume you meant AHCI. I edited this post to correct my reply.)
OK, I had to search Google to find the Wikipedia entry for AHCI - Advanced Host Controller Interface, a technology developed by Intel. I don't know if it applies to my AMD-based machine but I'll leave that out of the discussion for now.
The suggestions you made sound scary enough - I might have to wipe my HD and reinstall Windows-7, and carefully choose the drivers that get installed. This means I would have to carefully monitor an hours-long custom install and answer a lotta questions.
But I might get by if I merely uninstall my AHCI driver(s).
Pard'n me, Guv'ner, but how does a body do that? (I sometimes lapse into Cockney when someone makes me feel stupid.
Control Panel -> Device Manager -> Disk Drives -> Samsung HD103SJ
A right-click -> Properties found that the drivers date from 6/21/2006 and offers me the chance to update the driver. When I click on [Driver Details] it lists:
- C:\Windows\system\DRIVERS\disk.sys
- C:\Windows\system\drivers\partmgr.sys
but I don't see AHCI anywhere.
So how do I get there from here? And I WILL have to back up everything before I take that kind of risk; we all know that a device with no driver is as useful as a pet rock, only worth less money.
Thanks mucho.
So, you only had the NTFS error? that maybe was a corrupted MBR, hopefully that was fixed
HDD Regenerator also does the trick as far as I remember, but... what the... you fixed it! that's what counts
See ya!!!
P.D. by moniker you mean my nickname? if so, just pronounce like is written :P
P.D.2. Just for the record, the wipe of the drive was just in the VERY last case, in most cases, uninstalling a bad driver solves the issue... but was not aplicable in this case :P
Quote
