Just Installed And I Get This:

Topic

New Reply

I have just installed Windows 7. It is s dual boot situation with XP. This morning the first thing I did after it had booted was try to open Firefox. I got a message that Firefox was already running and I needed to close it. It was not running as I had just booted into Windows 7. I looked at the task manager and there were no applications listed. When I rebooted CHKDSK ran. Why would CHKDSK need to run? What caused the error message regarding Firefox?

Reply | Quote

Replies

This is more than a Firefox issue. I checked the event viewer and it is full of error messages. In the system log there are very many where the source is ntfs. the event id is 55 and the task category is(2).
In the details box the message is “the file system structure on the disk is corrupt and unusable. Please run the chkdsk utility. This is a brand new hard drive. Windows XP is on another partition and is running perfectly, What is the problem with Windows 7?

Reply | Quote

This is more than a Firefox issue. I checked the event viewer and it is full of error messages. In the system log there are very many where the source is ntfs. the event id is 55 and the task category is(2).
In the details box the message is “the file system structure on the disk is corrupt and unusable. Please run the chkdsk utility. This is a brand new hard drive. Windows XP is on another partition and is running perfectly, What is the problem with Windows 7?

There are improvements in the NTFS file system incorporated into Windows 7, and it’s a little more picky than the NTFS in XP. I’m dual booting XP and 7 on a desktop and a laptop. Both needed chkdsk /r run under Wiindows 7 on all drives before it was satisfied and settled down. It rewrote gobs of security descriptors and a few other repairs, but I’ve had no further issues since.

Evidently the repairs made by Windows 7 are transparent to XP. When I boot the XP side there are no issues there, either.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Have you tried to run chkdsk /r?

It can fix a great many things.
Im not sure why it would be an issue this quickly but it would be best to
get it sorted out now.

Chances are that once it runs it wont be a problem again.

It may be something like a security descriptor that it thinks is wrong.
It doesnt necessarily mean that your data is scrambled.

Reply | Quote

It runs chkdsk almost every time Windows 7 starts. I don’t know about the chkdsk/r. Why would the system run chkdsk and not repair it?

Reply | Quote

Make sure you run chkdsk /R with a space before the /R. Windows does not run the repair option automatically. It only reports the errors but doesn’t correct them.

Reply | Quote

I ran Windows 7 version of chkdsk /r I think. I checked “Automatically fix file system errors” and “Scan for and attempt recovery of bad sectors”. It seems to have worked because so far everything is running smoothly.
I know chkdsk creates a log, but I don’t know where to look for it. I would like to see what it says.

Reply | Quote

I ran Windows 7 version of chkdsk /r I think. I checked “Automatically fix file system errors” and “Scan for and attempt recovery of bad sectors”. It seems to have worked because so far everything is running smoothly.
I know chkdsk creates a log, but I don’t know where to look for it. I would like to see what it says.

I performed a clean install of Windows 7 a few days ago and experienced the same NTFS corrupt issue. I used the same error correction routine you used (twice) and the problem was not there this morning on boot-up. Just checked the Event Viewer and found another occurrence timed 35 minutes after the initial morning boot.

This time I will use the command process with the chkdsk /r to see if the issue disappears.

Regarding your request for the chkdsk log… go to the Event Viewer | Windows Logs | Application and look for Wininit. Clicking on that entry will display the log.

Reply | Quote

I read the log and the thing that stood out was this statement ” Windows has checked the file system and found no problems.” yet everything is running smoothly now. Did just running chkdsk /r fix the problem even though windows found no problems?

Reply | Quote

I read the log and the thing that stood out was this statement ” Windows has checked the file system and found no problems.” yet everything is running smoothly now. Did just running chkdsk /r fix the problem even though windows found no problems?

Did further research after my last 55 error and found a link that suggested changing the power options resolved the issue. I went to Control Panel | Power Options and selected the High Performance setting electing to use all the defaults. Haven’t had a 55 error since the last reported one yesterday at 11:47 AM. Knock on wood the system will remain stable.

Reply | Quote

I have a lot of 55 errors too. I will try your suggestion for power settings.

Reply | Quote

I installed Corel Paint Shop Pro and then tried to install an update. I got a message about not having the program installed or the wrong version for the up date or the wrong version of the update. I rebooted and looked at event viewer and there were about a 1000 55 errors . the next two time I rebooted Chkdsk /r ran. I havent checked it this afternoon yet to see what happens now.
The Corel website says Paint Shop pro is compatible with Windows 7. Soo why the errors and chkdsk run?

Reply | Quote

I installed Corel Paint Shop Pro and then tried to install an update. I got a message about not having the program installed or the wrong version for the up date or the wrong version of the update. I rebooted and looked at event viewer and there were about a 1000 55 errors . the next two time I rebooted Chkdsk /r ran. I havent checked it this afternoon yet to see what happens now.
The Corel website says Paint Shop pro is compatible with Windows 7. Soo why the errors and chkdsk run?

There are several versions of Corel Paint Shop Pro. The current one I have installed is PSP X2 and it installed fine. Which version are you trying to install?

I have found that sometimes turning off your AV scanner for the installation of some software is required. For example, installing my nVidia software/drivers requires me to turn off NOD32 for the install process.

In some other cases, right clicking on the install packet and selecting Run as Administrator helps.

Regarding the 1000 type 55 errors… was this before or after changing the power options?. My type 55 errors have not resurfaced since changing the power options.

Over to you…

Reply | Quote

I installed version X2 also. It seemed to install fine but a message popped up that there was an update for X2. i tried downloading it from the message, as there was a link but nothing happened. I went to the Corel site and downloaded what I assumed, dumb on my part, assuming, was the same update. It was after trying to install this update that I got all the errors. I had changed the power options prior to this.
I just booted Windows 7 and event viewer said I already had 20 errors they are 455, 488, 1006, 7042.7040, 9000, 3030, and 8211 errors. Just what exactly is going on here?
Also I just got a message form Action Center that Microsoft Security Essentials and Windows Defender both report that they are turned off. I am unable to start them.

Reply | Quote

I installed version X2 also. It seemed to install fine but a message popped up that there was an update for X2. i tried downloading it from the message, as there was a link but nothing happened. I went to the Corel site and downloaded what I assumed, dumb on my part, assuming, was the same update. It was after trying to install this update that I got all the errors. I had changed the power options prior to this.
I just booted Windows 7 and event viewer said I already had 20 errors they are 455, 488, 1006, 7042.7040, 9000, 3030, and 8211 errors. Just what exactly is going on here?
Also I just got a message form Action Center that Microsoft Security Essentials and Windows Defender both report that they are turned off. I am unable to start them.

Sure looks like a mess. About the only think I can suggest at this stage (other than a complete, clean install of W7) is to try:

[*]Uninstall PSP completely…[*]Run another chkdsk /r…[*]Perform a Repair install of W7

Assuming that you haven’t turned off MSE and Defender then something is amiss in that area. Perhaps Malware? In which case use you favourite scanner to detect any nasty beasts.

Insofar as those other errors are concerned, you did not provide any descriptors and so I can’t shed any light without knowing more specifics.

Back to you…

Reply | Quote

Sure looks like a mess. About the only think I can suggest at this stage (other than a complete, clean install of W7) is to try:

[*]Uninstall PSP completely…[*]Run another chkdsk /r…[*]Perform a Repair install of W7

Assuming that you haven’t turned off MSE and Defender then something is amiss in that area. Perhaps Malware? In which case use you favourite scanner to detect any nasty beasts.

Insofar as those other errors are concerned, you did not provide any descriptors and so I can’t shed any light without knowing more specifics.

Back to you…

Actually MSE by default turns off Windows Defender since MSE by itself has all of Defenders capabilities.

Also, it is recommended that you not run 2 AV or Malware programs in real time together. I run MSE in real time and do a complete scan about once per week, but keep Maleware bytes just to scan weekly but stop it from performing real time scans. Supposedly the Maleware Bytes free version does not have real time capabilities, but mine does. It may have been a glitch in a Maleware Byte update, but if mine can who knows???

You can shut down Maleware bytes realtime if it is running by typing msconfig in the run box, choosing Selective startup, the go to the Startup tab and unchecking all that you do not want to run in realtime (background). As a side note this will also free up system resources.

Reply | Quote

Sure looks like a mess. About the only think I can suggest at this stage (other than a complete, clean install of W7) is to try:

[*]Uninstall PSP completely…[*]Run another chkdsk /r…[*]Perform a Repair install of W7

Assuming that you haven’t turned off MSE and Defender then something is amiss in that area. Perhaps Malware? In which case use you favourite scanner to detect any nasty beasts.

Insofar as those other errors are concerned, you did not provide any descriptors and so I can’t shed any light without knowing more specifics.

Back to you…

Actually MSE by default turns off Windows Defender since MSE by itself has all of Defenders capabilities.

Also, it is recommended that you not run 2 AV or Malware programs in real time together. I run MSE in real time and do a complete scan about once per week, but keep Maleware bytes just to scan weekly but stop it from performing real time scans. Supposedly the Maleware Bytes free version does not have real time capabilities, but mine does. It may have been a glitch in a Maleware Byte update, but if mine can who knows???

You can shut down Maleware bytes realtime if it is running by typing msconfig in the run box, choosing Selective startup, the go to the Startup tab and unchecking all that you do not want to run in realtime (background). As a side note this will also free up system resources.

Reply | Quote

Sure looks like a mess. About the only think I can suggest at this stage (other than a complete, clean install of W7) is to try:

[*]Uninstall PSP completely…[*]Run another chkdsk /r…[*]Perform a Repair install of W7

Assuming that you haven’t turned off MSE and Defender then something is amiss in that area. Perhaps Malware? In which case use you favourite scanner to detect any nasty beasts.

Insofar as those other errors are concerned, you did not provide any descriptors and so I can’t shed any light without knowing more specifics.

Back to you…

Actually MSE by default turns off Windows Defender since MSE by itself has all of Defenders capabilities.

Also, it is recommended that you not run 2 AV or Malware programs in real time together. I run MSE in real time and do a complete scan about once per week, but keep Maleware bytes just to scan weekly but stop it from performing real time scans. Supposedly the Maleware Bytes free version does not have real time capabilities, but mine does. It may have been a glitch in a Maleware Byte update, but if mine can who knows???

You can shut down Maleware bytes realtime if it is running by typing msconfig in the run box, choosing Selective startup, the go to the Startup tab and unchecking all that you do not want to run in realtime (background). As a side note this will also free up system resources.

Reply | Quote

Sure looks like a mess. About the only think I can suggest at this stage (other than a complete, clean install of W7) is to try:

[*]Uninstall PSP completely…[*]Run another chkdsk /r…[*]Perform a Repair install of W7

Assuming that you haven’t turned off MSE and Defender then something is amiss in that area. Perhaps Malware? In which case use you favourite scanner to detect any nasty beasts.

Insofar as those other errors are concerned, you did not provide any descriptors and so I can’t shed any light without knowing more specifics.

Back to you…

Actually MSE by default turns off Windows Defender since MSE by itself has all of Defenders capabilities.

Also, it is recommended that you not run 2 AV or Malware programs in real time together. I run MSE in real time and do a complete scan about once per week, but keep Maleware bytes just to scan weekly but stop it from performing real time scans. Supposedly the Maleware Bytes free version does not have real time capabilities, but mine does. It may have been a glitch in a Maleware Byte update, but if mine can who knows???

You can shut down Maleware bytes realtime if it is running by typing msconfig in the run box, choosing Selective startup, the go to the Startup tab and unchecking all that you do not want to run in realtime (background). As a side note this will also free up system resources.

Reply | Quote

Sure looks like a mess. About the only think I can suggest at this stage (other than a complete, clean install of W7) is to try:

[*]Uninstall PSP completely…[*]Run another chkdsk /r…[*]Perform a Repair install of W7

Assuming that you haven’t turned off MSE and Defender then something is amiss in that area. Perhaps Malware? In which case use you favourite scanner to detect any nasty beasts.

Insofar as those other errors are concerned, you did not provide any descriptors and so I can’t shed any light without knowing more specifics.

Back to you…

Actually MSE by default turns off Windows Defender since MSE by itself has all of Defenders capabilities.

Also, it is recommended that you not run 2 AV or Malware programs in real time together. I run MSE in real time and do a complete scan about once per week, but keep Maleware bytes just to scan weekly but stop it from performing real time scans. Supposedly the Maleware Bytes free version does not have real time capabilities, but mine does. It may have been a glitch in a Maleware Byte update, but if mine can who knows???

You can shut down Maleware bytes realtime if it is running by typing msconfig in the run box, choosing Selective startup, the go to the Startup tab and unchecking all that you do not want to run in realtime (background). As a side note this will also free up system resources.

Reply | Quote

Sure looks like a mess. About the only think I can suggest at this stage (other than a complete, clean install of W7) is to try:

[*]Uninstall PSP completely…[*]Run another chkdsk /r…[*]Perform a Repair install of W7

Assuming that you haven’t turned off MSE and Defender then something is amiss in that area. Perhaps Malware? In which case use you favourite scanner to detect any nasty beasts.

Insofar as those other errors are concerned, you did not provide any descriptors and so I can’t shed any light without knowing more specifics.

Back to you…

Actually MSE by default turns off Windows Defender since MSE by itself has all of Defenders capabilities.

Also, it is recommended that you not run 2 AV or Malware programs in real time together. I run MSE in real time and do a complete scan about once per week, but keep Maleware bytes just to scan weekly but stop it from performing real time scans. Supposedly the Maleware Bytes free version does not have real time capabilities, but mine does. It may have been a glitch in a Maleware Byte update, but if mine can who knows???

You can shut down Maleware bytes realtime if it is running by typing msconfig in the run box, choosing Selective startup, the go to the Startup tab and unchecking all that you do not want to run in realtime (background). As a side note this will also free up system resources.

Reply | Quote

Sure looks like a mess. About the only think I can suggest at this stage (other than a complete, clean install of W7) is to try:

[*]Uninstall PSP completely…[*]Run another chkdsk /r…[*]Perform a Repair install of W7

Assuming that you haven’t turned off MSE and Defender then something is amiss in that area. Perhaps Malware? In which case use you favourite scanner to detect any nasty beasts.

Insofar as those other errors are concerned, you did not provide any descriptors and so I can’t shed any light without knowing more specifics.

Back to you…

Actually MSE by default turns off Windows Defender since MSE by itself has all of Defenders capabilities.

Also, it is recommended that you not run 2 AV or Malware programs in real time together. I run MSE in real time and do a complete scan about once per week, but keep Maleware bytes just to scan weekly but stop it from performing real time scans. Supposedly the Maleware Bytes free version does not have real time capabilities, but mine does. It may have been a glitch in a Maleware Byte update, but if mine can who knows???

You can shut down Maleware bytes realtime if it is running by typing msconfig in the run box, choosing Selective startup, the go to the Startup tab and unchecking all that you do not want to run in realtime (background). As a side note this will also free up system resources.

Reply | Quote

Sure looks like a mess. About the only think I can suggest at this stage (other than a complete, clean install of W7) is to try:

[*]Uninstall PSP completely…[*]Run another chkdsk /r…[*]Perform a Repair install of W7

Assuming that you haven’t turned off MSE and Defender then something is amiss in that area. Perhaps Malware? In which case use you favourite scanner to detect any nasty beasts.

Insofar as those other errors are concerned, you did not provide any descriptors and so I can’t shed any light without knowing more specifics.

Back to you…

Actually MSE by default turns off Windows Defender since MSE by itself has all of Defenders capabilities.

Also, it is recommended that you not run 2 AV or Malware programs in real time together. I run MSE in real time and do a complete scan about once per week, but keep Maleware bytes just to scan weekly but stop it from performing real time scans. Supposedly the Maleware Bytes free version does not have real time capabilities, but mine does. It may have been a glitch in a Maleware Byte update, but if mine can who knows???

You can shut down Maleware bytes realtime if it is running by typing msconfig in the run box, choosing Selective startup, the go to the Startup tab and unchecking all that you do not want to run in realtime (background). As a side note this will also free up system resources.

Reply | Quote

I did uninstall PSP and ran chkdsk /r again. Event viewer shows no errors this time. However the log show I have had over 57,000 errors in the last 24 hrs.
Here is a screen shot of some of the errors I mentioned in my last post:
One other strange thing happened this time. I went to open Mozilla Thunderbird to check my email and I had to set up my account again. It was as if this was the first time I had used it. Very weird.

Reply | Quote

I did uninstall PSP and ran chkdsk /r again. Event viewer shows no errors this time. However the log show I have had over 57,000 errors in the last 24 hrs.
Here is a screen shot of some of the errors I mentioned in my last post:
One other strange thing happened this time. I went to open Mozilla Thunderbird to check my email and I had to set up my account again. It was as if this was the first time I had used it. Very weird.

As in my previous post, I would recommend checking for malware. I notice that you are running NOD32 and if you are using the current version, it does have spyware protection… but I`m not positive about its ability to detect and remove malware. Perhaps you should make that your next process.

Regarding the 57,000 logged items… once things have settled, you can always archive the log and perform the clear operation to remove them from your history.

Again, also think about performing that Repair Install of W7

Edited: to correct the remark about you using NOD32… I misread ESENT for ESET (which is NOD32)

Reply | Quote

I did uninstall PSP and ran chkdsk /r again. Event viewer shows no errors this time. However the log show I have had over 57,000 errors in the last 24 hrs.
Here is a screen shot of some of the errors I mentioned in my last post:
One other strange thing happened this time. I went to open Mozilla Thunderbird to check my email and I had to set up my account again. It was as if this was the first time I had used it. Very weird.

As in my previous post, I would recommend checking for malware. I notice that you are running NOD32 and if you are using the current version, it does have spyware protection… but I`m not positive about its ability to detect and remove malware. Perhaps you should make that your next process.

Regarding the 57,000 logged items… once things have settled, you can always archive the log and perform the clear operation to remove them from your history.

Again, also think about performing that Repair Install of W7

Edited: to correct the remark about you using NOD32… I misread ESENT for ESET (which is NOD32)

Reply | Quote

I did uninstall PSP and ran chkdsk /r again. Event viewer shows no errors this time. However the log show I have had over 57,000 errors in the last 24 hrs.
Here is a screen shot of some of the errors I mentioned in my last post:
One other strange thing happened this time. I went to open Mozilla Thunderbird to check my email and I had to set up my account again. It was as if this was the first time I had used it. Very weird.

As in my previous post, I would recommend checking for malware. I notice that you are running NOD32 and if you are using the current version, it does have spyware protection… but I`m not positive about its ability to detect and remove malware. Perhaps you should make that your next process.

Regarding the 57,000 logged items… once things have settled, you can always archive the log and perform the clear operation to remove them from your history.

Again, also think about performing that Repair Install of W7

Edited: to correct the remark about you using NOD32… I misread ESENT for ESET (which is NOD32)

Reply | Quote

I did uninstall PSP and ran chkdsk /r again. Event viewer shows no errors this time. However the log show I have had over 57,000 errors in the last 24 hrs.
Here is a screen shot of some of the errors I mentioned in my last post:
One other strange thing happened this time. I went to open Mozilla Thunderbird to check my email and I had to set up my account again. It was as if this was the first time I had used it. Very weird.

As in my previous post, I would recommend checking for malware. I notice that you are running NOD32 and if you are using the current version, it does have spyware protection… but I`m not positive about its ability to detect and remove malware. Perhaps you should make that your next process.

Regarding the 57,000 logged items… once things have settled, you can always archive the log and perform the clear operation to remove them from your history.

Again, also think about performing that Repair Install of W7

Edited: to correct the remark about you using NOD32… I misread ESENT for ESET (which is NOD32)

Reply | Quote

I did uninstall PSP and ran chkdsk /r again. Event viewer shows no errors this time. However the log show I have had over 57,000 errors in the last 24 hrs.
Here is a screen shot of some of the errors I mentioned in my last post:
One other strange thing happened this time. I went to open Mozilla Thunderbird to check my email and I had to set up my account again. It was as if this was the first time I had used it. Very weird.

As in my previous post, I would recommend checking for malware. I notice that you are running NOD32 and if you are using the current version, it does have spyware protection… but I`m not positive about its ability to detect and remove malware. Perhaps you should make that your next process.

Regarding the 57,000 logged items… once things have settled, you can always archive the log and perform the clear operation to remove them from your history.

Again, also think about performing that Repair Install of W7

Edited: to correct the remark about you using NOD32… I misread ESENT for ESET (which is NOD32)

Reply | Quote

I did uninstall PSP and ran chkdsk /r again. Event viewer shows no errors this time. However the log show I have had over 57,000 errors in the last 24 hrs.
Here is a screen shot of some of the errors I mentioned in my last post:
One other strange thing happened this time. I went to open Mozilla Thunderbird to check my email and I had to set up my account again. It was as if this was the first time I had used it. Very weird.

As in my previous post, I would recommend checking for malware. I notice that you are running NOD32 and if you are using the current version, it does have spyware protection… but I`m not positive about its ability to detect and remove malware. Perhaps you should make that your next process.

Regarding the 57,000 logged items… once things have settled, you can always archive the log and perform the clear operation to remove them from your history.

Again, also think about performing that Repair Install of W7

Edited: to correct the remark about you using NOD32… I misread ESENT for ESET (which is NOD32)

Reply | Quote

I did uninstall PSP and ran chkdsk /r again. Event viewer shows no errors this time. However the log show I have had over 57,000 errors in the last 24 hrs.
Here is a screen shot of some of the errors I mentioned in my last post:
One other strange thing happened this time. I went to open Mozilla Thunderbird to check my email and I had to set up my account again. It was as if this was the first time I had used it. Very weird.

As in my previous post, I would recommend checking for malware. I notice that you are running NOD32 and if you are using the current version, it does have spyware protection… but I`m not positive about its ability to detect and remove malware. Perhaps you should make that your next process.

Regarding the 57,000 logged items… once things have settled, you can always archive the log and perform the clear operation to remove them from your history.

Again, also think about performing that Repair Install of W7

Edited: to correct the remark about you using NOD32… I misread ESENT for ESET (which is NOD32)

Reply | Quote

I did uninstall PSP and ran chkdsk /r again. Event viewer shows no errors this time. However the log show I have had over 57,000 errors in the last 24 hrs.
Here is a screen shot of some of the errors I mentioned in my last post:
One other strange thing happened this time. I went to open Mozilla Thunderbird to check my email and I had to set up my account again. It was as if this was the first time I had used it. Very weird.

As in my previous post, I would recommend checking for malware. I notice that you are running NOD32 and if you are using the current version, it does have spyware protection… but I`m not positive about its ability to detect and remove malware. Perhaps you should make that your next process.

Regarding the 57,000 logged items… once things have settled, you can always archive the log and perform the clear operation to remove them from your history.

Again, also think about performing that Repair Install of W7

Edited: to correct the remark about you using NOD32… I misread ESENT for ESET (which is NOD32)

Reply | Quote

Ok. This morning I ran chkdsk /r because last night I couldn’t install Malwarebyte’s Anti Malware because I had corrupt files. The first thing I tried to do this morning was install it. I still couldn’t because I had corrupt files. Also after running chk dsk this morning it wiped out my email settings again. This sucks. I never had these problems when I was running the RC version.
I ran a scan of the partition that has Windows 7 on it with Malwarebyte’s from XP and it came up clean. I am going to format the drive and do a clean install. This will be the third time I have done this.

Reply | Quote

Ok. This morning I ran chkdsk /r because last night I couldn’t install Malwarebyte’s Anti Malware because I had corrupt files. The first thing I tried to do this morning was install it. I still couldn’t because I had corrupt files. Also after running chk dsk this morning it wiped out my email settings again. This sucks. I never had these problems when I was running the RC version.
I ran a scan of the partition that has Windows 7 on it with Malwarebyte’s from XP and it came up clean. I am going to format the drive and do a clean install. This will be the third time I have done this.

Reply | Quote

Ok. This morning I ran chkdsk /r because last night I couldn’t install Malwarebyte’s Anti Malware because I had corrupt files. The first thing I tried to do this morning was install it. I still couldn’t because I had corrupt files. Also after running chk dsk this morning it wiped out my email settings again. This sucks. I never had these problems when I was running the RC version.
I ran a scan of the partition that has Windows 7 on it with Malwarebyte’s from XP and it came up clean. I am going to format the drive and do a clean install. This will be the third time I have done this.

Reply | Quote

Ok. This morning I ran chkdsk /r because last night I couldn’t install Malwarebyte’s Anti Malware because I had corrupt files. The first thing I tried to do this morning was install it. I still couldn’t because I had corrupt files. Also after running chk dsk this morning it wiped out my email settings again. This sucks. I never had these problems when I was running the RC version.
I ran a scan of the partition that has Windows 7 on it with Malwarebyte’s from XP and it came up clean. I am going to format the drive and do a clean install. This will be the third time I have done this.

Reply | Quote

Ok. This morning I ran chkdsk /r because last night I couldn’t install Malwarebyte’s Anti Malware because I had corrupt files. The first thing I tried to do this morning was install it. I still couldn’t because I had corrupt files. Also after running chk dsk this morning it wiped out my email settings again. This sucks. I never had these problems when I was running the RC version.
I ran a scan of the partition that has Windows 7 on it with Malwarebyte’s from XP and it came up clean. I am going to format the drive and do a clean install. This will be the third time I have done this.

Reply | Quote

Ok. This morning I ran chkdsk /r because last night I couldn’t install Malwarebyte’s Anti Malware because I had corrupt files. The first thing I tried to do this morning was install it. I still couldn’t because I had corrupt files. Also after running chk dsk this morning it wiped out my email settings again. This sucks. I never had these problems when I was running the RC version.
I ran a scan of the partition that has Windows 7 on it with Malwarebyte’s from XP and it came up clean. I am going to format the drive and do a clean install. This will be the third time I have done this.

Reply | Quote

Ok. This morning I ran chkdsk /r because last night I couldn’t install Malwarebyte’s Anti Malware because I had corrupt files. The first thing I tried to do this morning was install it. I still couldn’t because I had corrupt files. Also after running chk dsk this morning it wiped out my email settings again. This sucks. I never had these problems when I was running the RC version.
I ran a scan of the partition that has Windows 7 on it with Malwarebyte’s from XP and it came up clean. I am going to format the drive and do a clean install. This will be the third time I have done this.

Reply | Quote

Ok. This morning I ran chkdsk /r because last night I couldn’t install Malwarebyte’s Anti Malware because I had corrupt files. The first thing I tried to do this morning was install it. I still couldn’t because I had corrupt files. Also after running chk dsk this morning it wiped out my email settings again. This sucks. I never had these problems when I was running the RC version.
I ran a scan of the partition that has Windows 7 on it with Malwarebyte’s from XP and it came up clean. I am going to format the drive and do a clean install. This will be the third time I have done this.

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

OK, reset the Power Option settings to High Performance if you haven’t done so already.

Force a chkdsk /r to run on reboot, then restart and check the Event Viewer for the Wininit log. If everything looks ok, try another restart and see if things have settled down.

If not, check let me know if there are any messages, Critical or Error in the Event Viewer. If so, provide the description(s).

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

OK, reset the Power Option settings to High Performance if you haven’t done so already.

Force a chkdsk /r to run on reboot, then restart and check the Event Viewer for the Wininit log. If everything looks ok, try another restart and see if things have settled down.

If not, check let me know if there are any messages, Critical or Error in the Event Viewer. If so, provide the description(s).

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

OK, reset the Power Option settings to High Performance if you haven’t done so already.

Force a chkdsk /r to run on reboot, then restart and check the Event Viewer for the Wininit log. If everything looks ok, try another restart and see if things have settled down.

If not, check let me know if there are any messages, Critical or Error in the Event Viewer. If so, provide the description(s).

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

OK, reset the Power Option settings to High Performance if you haven’t done so already.

Force a chkdsk /r to run on reboot, then restart and check the Event Viewer for the Wininit log. If everything looks ok, try another restart and see if things have settled down.

If not, check let me know if there are any messages, Critical or Error in the Event Viewer. If so, provide the description(s).

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

OK, reset the Power Option settings to High Performance if you haven’t done so already.

Force a chkdsk /r to run on reboot, then restart and check the Event Viewer for the Wininit log. If everything looks ok, try another restart and see if things have settled down.

If not, check let me know if there are any messages, Critical or Error in the Event Viewer. If so, provide the description(s).

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

OK, reset the Power Option settings to High Performance if you haven’t done so already.

Force a chkdsk /r to run on reboot, then restart and check the Event Viewer for the Wininit log. If everything looks ok, try another restart and see if things have settled down.

If not, check let me know if there are any messages, Critical or Error in the Event Viewer. If so, provide the description(s).

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

OK, reset the Power Option settings to High Performance if you haven’t done so already.

Force a chkdsk /r to run on reboot, then restart and check the Event Viewer for the Wininit log. If everything looks ok, try another restart and see if things have settled down.

If not, check let me know if there are any messages, Critical or Error in the Event Viewer. If so, provide the description(s).

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

OK, reset the Power Option settings to High Performance if you haven’t done so already.

Force a chkdsk /r to run on reboot, then restart and check the Event Viewer for the Wininit log. If everything looks ok, try another restart and see if things have settled down.

If not, check let me know if there are any messages, Critical or Error in the Event Viewer. If so, provide the description(s).

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

Reply | Quote

I reinstalled Windows 7. I went to windows update and installed all the important updates and one optional update related to the intel chipset in my computer. I rebooted after the updates were installed, successfully according to Windows. What happens when I reboot? Chkdsk runs. Why? The only other things I had installed were Microsoft Secrity Essentials and Malwarebyte’s Anti Malware. Something is not right.

Reply | Quote

It is s dual boot situation with XP.

Chkdsk runs on only one drive/partition per session. Which drive/partition is triggering chkdsk to run?

Have you run chkdsk /r on all drives/partitions?

I have 3 physical hard drives on my desktop with a total of 12 partitions (which are seen by disk management as drives). When I first installed 7 Ultimate I had a number of incidents of unrecognized partitions, partitions being reported as unallocated, chkdsk needing to run, etc. After reading that there were improvements in NTFS with Windows 7, I ran a manual chkdsk /r on each and every drive/partition on my machine, and that ended it.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

It is s dual boot situation with XP.

Chkdsk runs on only one drive/partition per session. Which drive/partition is triggering chkdsk to run?

Have you run chkdsk /r on all drives/partitions?

I have 3 physical hard drives on my desktop with a total of 12 partitions (which are seen by disk management as drives). When I first installed 7 Ultimate I had a number of incidents of unrecognized partitions, partitions being reported as unallocated, chkdsk needing to run, etc. After reading that there were improvements in NTFS with Windows 7, I ran a manual chkdsk /r on each and every drive/partition on my machine, and that ended it.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

It is s dual boot situation with XP.

Chkdsk runs on only one drive/partition per session. Which drive/partition is triggering chkdsk to run?

Have you run chkdsk /r on all drives/partitions?

I have 3 physical hard drives on my desktop with a total of 12 partitions (which are seen by disk management as drives). When I first installed 7 Ultimate I had a number of incidents of unrecognized partitions, partitions being reported as unallocated, chkdsk needing to run, etc. After reading that there were improvements in NTFS with Windows 7, I ran a manual chkdsk /r on each and every drive/partition on my machine, and that ended it.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

It is s dual boot situation with XP.

Chkdsk runs on only one drive/partition per session. Which drive/partition is triggering chkdsk to run?

Have you run chkdsk /r on all drives/partitions?

I have 3 physical hard drives on my desktop with a total of 12 partitions (which are seen by disk management as drives). When I first installed 7 Ultimate I had a number of incidents of unrecognized partitions, partitions being reported as unallocated, chkdsk needing to run, etc. After reading that there were improvements in NTFS with Windows 7, I ran a manual chkdsk /r on each and every drive/partition on my machine, and that ended it.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

It is s dual boot situation with XP.

Chkdsk runs on only one drive/partition per session. Which drive/partition is triggering chkdsk to run?

Have you run chkdsk /r on all drives/partitions?

I have 3 physical hard drives on my desktop with a total of 12 partitions (which are seen by disk management as drives). When I first installed 7 Ultimate I had a number of incidents of unrecognized partitions, partitions being reported as unallocated, chkdsk needing to run, etc. After reading that there were improvements in NTFS with Windows 7, I ran a manual chkdsk /r on each and every drive/partition on my machine, and that ended it.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

It is s dual boot situation with XP.

Chkdsk runs on only one drive/partition per session. Which drive/partition is triggering chkdsk to run?

Have you run chkdsk /r on all drives/partitions?

I have 3 physical hard drives on my desktop with a total of 12 partitions (which are seen by disk management as drives). When I first installed 7 Ultimate I had a number of incidents of unrecognized partitions, partitions being reported as unallocated, chkdsk needing to run, etc. After reading that there were improvements in NTFS with Windows 7, I ran a manual chkdsk /r on each and every drive/partition on my machine, and that ended it.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

It is s dual boot situation with XP.

Chkdsk runs on only one drive/partition per session. Which drive/partition is triggering chkdsk to run?

Have you run chkdsk /r on all drives/partitions?

I have 3 physical hard drives on my desktop with a total of 12 partitions (which are seen by disk management as drives). When I first installed 7 Ultimate I had a number of incidents of unrecognized partitions, partitions being reported as unallocated, chkdsk needing to run, etc. After reading that there were improvements in NTFS with Windows 7, I ran a manual chkdsk /r on each and every drive/partition on my machine, and that ended it.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

It is s dual boot situation with XP.

Chkdsk runs on only one drive/partition per session. Which drive/partition is triggering chkdsk to run?

Have you run chkdsk /r on all drives/partitions?

I have 3 physical hard drives on my desktop with a total of 12 partitions (which are seen by disk management as drives). When I first installed 7 Ultimate I had a number of incidents of unrecognized partitions, partitions being reported as unallocated, chkdsk needing to run, etc. After reading that there were improvements in NTFS with Windows 7, I ran a manual chkdsk /r on each and every drive/partition on my machine, and that ended it.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

Ted: I didn’t even have Malwarebytes installed when I was having all the problems before I did the new install. I will disable it from start up.

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

There is no difference between running through the cmd or using Windows 7 assuming you select the right parameters. With cmd you would be using the /r parameter. With Windows 7 | Drive? | Properties check off both Auto fix… and Scan for… As you no doubt are aware, either will process on rebooting.

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

There is no difference between running through the cmd or using Windows 7 assuming you select the right parameters. With cmd you would be using the /r parameter. With Windows 7 | Drive? | Properties check off both Auto fix… and Scan for… As you no doubt are aware, either will process on rebooting.

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

There is no difference between running through the cmd or using Windows 7 assuming you select the right parameters. With cmd you would be using the /r parameter. With Windows 7 | Drive? | Properties check off both Auto fix… and Scan for… As you no doubt are aware, either will process on rebooting.

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

There is no difference between running through the cmd or using Windows 7 assuming you select the right parameters. With cmd you would be using the /r parameter. With Windows 7 | Drive? | Properties check off both Auto fix… and Scan for… As you no doubt are aware, either will process on rebooting.

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

There is no difference between running through the cmd or using Windows 7 assuming you select the right parameters. With cmd you would be using the /r parameter. With Windows 7 | Drive? | Properties check off both Auto fix… and Scan for… As you no doubt are aware, either will process on rebooting.

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

There is no difference between running through the cmd or using Windows 7 assuming you select the right parameters. With cmd you would be using the /r parameter. With Windows 7 | Drive? | Properties check off both Auto fix… and Scan for… As you no doubt are aware, either will process on rebooting.

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

There is no difference between running through the cmd or using Windows 7 assuming you select the right parameters. With cmd you would be using the /r parameter. With Windows 7 | Drive? | Properties check off both Auto fix… and Scan for… As you no doubt are aware, either will process on rebooting.

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

There is no difference between running through the cmd or using Windows 7 assuming you select the right parameters. With cmd you would be using the /r parameter. With Windows 7 | Drive? | Properties check off both Auto fix… and Scan for… As you no doubt are aware, either will process on rebooting.

Reply | Quote

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

A portion of your boot files are located on the XP partition since that was your original boot drive.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

A portion of your boot files are located on the XP partition since that was your original boot drive.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

A portion of your boot files are located on the XP partition since that was your original boot drive.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

A portion of your boot files are located on the XP partition since that was your original boot drive.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

A portion of your boot files are located on the XP partition since that was your original boot drive.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

A portion of your boot files are located on the XP partition since that was your original boot drive.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

A portion of your boot files are located on the XP partition since that was your original boot drive.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

A portion of your boot files are located on the XP partition since that was your original boot drive.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

Ted: I didn’t even have Malwarebytes installed when I was having all the problems before I did the new install. I will disable it from start up.

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

Ted: I didn’t even have Malwarebytes installed when I was having all the problems before I did the new install. I will disable it from start up.

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

Ted: I didn’t even have Malwarebytes installed when I was having all the problems before I did the new install. I will disable it from start up.

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

Ted: I didn’t even have Malwarebytes installed when I was having all the problems before I did the new install. I will disable it from start up.

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

Ted: I didn’t even have Malwarebytes installed when I was having all the problems before I did the new install. I will disable it from start up.

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

Ted: I didn’t even have Malwarebytes installed when I was having all the problems before I did the new install. I will disable it from start up.

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

Reply | Quote

Bob: I did set the power options to high performance as soon as it booted up after the install. I will runn chkdsk /r when I get home this afternoon. Is there a difference between scheduling it through cmd or using Windows7 ?

Ted: I didn’t even have Malwarebytes installed when I was having all the problems before I did the new install. I will disable it from start up.

bbearren: The Windows 7 partition is triggering it. I haven’t run it on the XP partition becaus I am not having any problems with that. I will run it on there just to keep things honest. I hope.

So running a manual dskchk is the best option?

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

1st – glad the system is behaving. Let’s hope it stays that way.

2nd – cannot comment on dual boot environments. Have no experience along those lines as have never seen need to run two O/Ses.

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

1st – glad the system is behaving. Let’s hope it stays that way.

2nd – cannot comment on dual boot environments. Have no experience along those lines as have never seen need to run two O/Ses.

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

1st – glad the system is behaving. Let’s hope it stays that way.

2nd – cannot comment on dual boot environments. Have no experience along those lines as have never seen need to run two O/Ses.

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

1st – glad the system is behaving. Let’s hope it stays that way.

2nd – cannot comment on dual boot environments. Have no experience along those lines as have never seen need to run two O/Ses.

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

1st – glad the system is behaving. Let’s hope it stays that way.

2nd – cannot comment on dual boot environments. Have no experience along those lines as have never seen need to run two O/Ses.

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

1st – glad the system is behaving. Let’s hope it stays that way.

2nd – cannot comment on dual boot environments. Have no experience along those lines as have never seen need to run two O/Ses.

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

1st – glad the system is behaving. Let’s hope it stays that way.

2nd – cannot comment on dual boot environments. Have no experience along those lines as have never seen need to run two O/Ses.

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

1st – glad the system is behaving. Let’s hope it stays that way.

2nd – cannot comment on dual boot environments. Have no experience along those lines as have never seen need to run two O/Ses.

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Yes, the order of installation matters. XP first, then Windows 7.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Yes, the order of installation matters. XP first, then Windows 7.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Yes, the order of installation matters. XP first, then Windows 7.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Yes, the order of installation matters. XP first, then Windows 7.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Yes, the order of installation matters. XP first, then Windows 7.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Yes, the order of installation matters. XP first, then Windows 7.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Yes, the order of installation matters. XP first, then Windows 7.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Yes, the order of installation matters. XP first, then Windows 7.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Reply | Quote

So far this afternoon it is behaving. I will run chkdsk /r on the XP partition as well. Would it have been better to install Windows 7 first then Xp or doesn’t that make any difference?

Reply | Quote

I did install XP first although it was an image rather than an actual clean install would this make a difference? Also

It is happening again I have over 1300 errors in event viewer in both the application log and security log. In the application log they are mostly:
Source: ESENT
Event ID: 455
Task Category: Login/Recovery
In the system log they are mostly
Source:Ntf
Event ID: 55
Task Category: 55 (2)
I tried to take a screen shot but when I tried to save it I was told “disk structure corrupted and unreadable”
Any thoughts?

Reply | Quote

I did install XP first although it was an image rather than an actual clean install would this make a difference? Also

Not sure if it would make a difference. However, if the image contains corrupted sectors, then they would be restored in bad shape. Which imaging program was used to create that backup? Some imaging apps allow a chkdsk to be run against the imaged backup file. For example Shadow Protect does have that feature. Not sure about others like True Image.

It is happening again I have over 1300 errors in event viewer in both the application log and security log. In the application log they are mostly:
Source: ESENT
Event ID: 455
Task Category: Login/Recovery
In the system log they are mostly
Source:Ntf
Event ID: 55
Task Category: 55 (2)
I tried to take a screen shot but when I tried to save it I was told “disk structure corrupted and unreadable”
Any thoughts?

The NTFS Event ID 55 is not good. The descriptive should tell you the volume name that has the corruption. That would tell you whether it is your XP or W7 environment. Obviously, you will have to run another chkdsk /r against that volume.

Reply | Quote

Sorry Stephen, I should have added that I will be going off air for awhile. I broke my wrist 7 weeks ago and the bones are not healing as expected. I am heading to the hospital tomorrow (Saturday) for surgery. They’re going to insert pins and some gawd awful contraption called an external fixation. So, not sure when I’ll be back on line. Perhaps some other folks can jump in here to continue helping you.

Reply | Quote

Have you run chkdsk /r from the Windows 7 environment on the XP partition?

Have you run the hard drive manufacturer’s diagnostic utility on your drive?

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

No I haven’t done that I didn’t know it could be done. How would I do that? from the cmd prompt?
I have run intel’s diagnostic utility on both partitions and no errors were reported. I suppose I should mention that this is a solid state drive. I don’t know how that would change what is going on here.

Reply | Quote

No I haven’t done that I didn’t know it could be done. How would I do that? from the cmd prompt?

Yes, open a command prompt and type

chkdsk /r D:

(“D” is whatever drive letter that is shown for the XP partition when you’re running Windows 7).

Visit the drive manufacturer’s site and see if there is a diagnostic utility for your drive model available for download.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

How does running chkdsk from the Windows7 environment on the XP partition differ from scheduling it in the Xp partition itself?

As I have stated many times, even in my previous post: “I have run Intel’s diagnostic utility on both partitions and no errors were reported”. This is an Intel 160 GB SSD.

Reply | Quote

How does running chkdsk from the Windows7 environment on the XP partition differ from scheduling it in the Xp partition itself?

There are improvements in the NTFS in Windows 7 over the NTFS in 2000/XP. If you run it under XP, you don’t get the benefit of having the XP partition NTFS upgraded to the same level as Windows 7 NTFS.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Windows 7 works great unless I try to do something other than use my web browser. I tried to download something this morning and I get an error message saying it couldn’t be saved because an unknown error occurred.
I checked event viewer and it said over 2700 errors had occurred in the last hour. I think I wasted my money on this one.

Reply | Quote

It sure appears that based on your system (harware as well as software) your having major problems with the dual boot. I realize that some don’t want to give up there XP OS, but based on all the problems you have had, the best solution may be to wipe out everything and start with a fresh install of Win 7 without the dual boot. I do NOT believe you have wasted your money. Once Win 7 is running well, then install an XP emulator. There are some setups that even if Win 7 compatibility shows it will work, there are still conflicts.

As always, if you decide to go this route, create a backup first, then just go for it. I don’t miss XP at all. In fact my employer (a very large corp with multiple locations) is looking at replacing our entire XP system with Win 7 and I am looking forward to it.

Reply | Quote

Have you run chkdsk /r on the XP partition from the Windows 7 installation yet?

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Have you tried updating both your chip set & controller drivers, as well as the firmware on the SSD itself? Also if it’s a first gen SSD you may need to get a manual trim utility from Intel?

Reply | Quote

Yes I ran chkdsk /r from the Windows 7 installation. That was before I had the download issue this morning.
I had no problem with the dual boot situation when I had the RC version of Windows 7 installed.
I updated the firmware on the SSD before I installed either OS. Intel does have a manual trim utility that supposedly I only need for XP as Windows 7 is supposed to do this. I have, however, used it on the Windows 7 partition as well.
I will check on the chipset drivers. What controller drivers are you referring to?

Reply | Quote

The SATA drive controller, you should be able to find them on the manufacturers web site. You can find them listed in Device Manager under IDE ATA/ATAPI controllers.

Reply | Quote

The SATA drive controller seems to be part of the chipset which has the latest drivers.
Also I am still getting a lot of errors mostly they are 55 errors. I just booted and there were 10 errors. I have changed the performance settings as was suggested. I shouldn’t have to run chkdsk every time I boot. I really ready to kiss the money I spent on Windows 7 goodbye.

Reply | Quote

This really is unsatisfactory. 2000 errors mostly 55. Isn’t there anybody here who can help with this problem?

Reply | Quote

This really is unsatisfactory. 2000 errors mostly 55. Isn’t there anybody here who can help with this problem?

Did you run the Windows 7 Upgrade Advisor – Download – Microsoft Windows before you installed Windows 7? You can still run it after the install also.

Joe

--Joe

Reply | Quote

Yes I did run it and I was told my computer could run Windows 7. I had none of these problems when I had the RC candidate of Windows 7 installed.

Reply | Quote

Yes I did run it and I was told my computer could run Windows 7. I had none of these problems when I had the RC candidate of Windows 7 installed.

It seems as though you’ve got a hardware problem. Have you checked the physical connections for everything inside the PC?

Joe

--Joe

Reply | Quote

This is a laptop.

Reply | Quote

This is a laptop.

Laptops still have physical connections. The hard drive module plugs directly into the controller without a ribbon cable, but there is still a physical connection between the hard drive and the controller. There are probably other peripherals that plug into the motherboard, as well. My D800 has a graphics card, a modem, a smartcard reader, a bluetooth apapter, all of which can be replaced and have physical connections to the motherboard.

Laptops can get a lot of twisting and flexing, not to mention the thermal cycling which can loosen connections. I’m not necessarily saying that is the problem, but don’t rule it out by any means. I fixed an error with my modem by unplugging it and plugging it back in. I never use it, but I started getting a hardware error popping up almost everytime I started the laptop. Unplugging and replugging the modem eliminated the modem hardware error.

You may want to start a dialogue with the laptop manufacturer and/or Intel on your drive.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

I reseated the hard drive and got 13 errors after booting up and doing nothing but check event viewer. None of these errors are considered critical.
I have no problems with the XP partition.

Reply | Quote

I know of no laptops that do not use a ribbon cable to connect the HD to the controller… They may be made of mylar, but they are still ribbon cables. Also, I am not so sure the NTFS improvements are indeed improvements. Takes longer to write data, frags faster. Not a good thing IMHO.

Reply | Quote

This is how I solved this problem:
I installed Windows 7 on a different hard drive. I worked fine with no errors. I formatted the partition in the SSD that had Windows7 on it and put an image of Windows 7 from the functioning hard drive. It is running fine with no errors. Why did this work but not when I installed it on the SSD from the installation disk?

Reply | Quote