Back to XP

Message Share Topic Printable Version Google Delicious Digg StumbleUpon Windows Live Yahoo Bookmarks reddit Facebook MySpace Newsvine Furl Topic Search Topic Options Post Reply Create New Topic

   I'm back....
You'll recall I first installed 7 on a spare drive keeping XP on my primary Raptor.
When I made the final switchover I put 7 on the Raptor.
I was digging it but every once in a while I'd get a sidebyside error (something I'd never seen before even though it's apparently in XP) and the drive would come up "dirty". I'd run chkdsk with both the fix and scan and repair bad sectors option (talk about a time burner) and it'd come up clean. It would flip the dirty bit.
I might add that the drive came up totally clean with any other check I ran on it and the SMART attributes said it was 100%.
Got tried of that so I switched back to the original drive which didn't have the problem.
Tried to take a Windows backup yesterday and the drive I was saving to came up dirty. More chkdsk which did find some stuff. Every time I ran backup it'd crash and chkdsk would report the same errors.
Reformatted an external drive which did save the backup with no problems at all. Took a while so when the backup finished I shut everything down.
Booted this morning and 7 wouldn't boot, just hung at the splash screen. Rebooted and tried the recovery deal about half a dozen times with no luck. I was running out of time to go to work so I didn't try to recover the Windows backup I'd taken the night before but just restored my XP backup.
Sure got to know event manager (which is really good in 7) and do research on event ID 55 but I never figured it out. Oh, also chkntfs d: which I'd never known about (and don't want to know about).
Yup, I had the latest BIOS and drivers so that can't be it so I'm guessing a compatibility problem with the SATA controller, my SATA drives and 7 or at least that's the only thing I can think of. 7 continues to run just fine on the old box....

Author	Message Share Topic Printable Version Google Delicious Digg StumbleUpon Windows Live Yahoo Bookmarks reddit Facebook MySpace Newsvine Furl Topic Search Topic Options Post Reply Create New Topic
Don Watkins Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Admin Group Admin Joined: 14 Mar 2008 Posts: 22195	Quote Reply Topic: Back to XP Posted: 01 Jan 2010 at 6:29am
	I'm back.... You'll recall I first installed 7 on a spare drive keeping XP on my primary Raptor. When I made the final switchover I put 7 on the Raptor. I was digging it but every once in a while I'd get a sidebyside error (something I'd never seen before even though it's apparently in XP) and the drive would come up "dirty". I'd run chkdsk with both the fix and scan and repair bad sectors option (talk about a time burner) and it'd come up clean. It would flip the dirty bit. I might add that the drive came up totally clean with any other check I ran on it and the SMART attributes said it was 100%. Got tried of that so I switched back to the original drive which didn't have the problem. Tried to take a Windows backup yesterday and the drive I was saving to came up dirty. More chkdsk which did find some stuff. Every time I ran backup it'd crash and chkdsk would report the same errors. Reformatted an external drive which did save the backup with no problems at all. Took a while so when the backup finished I shut everything down. Booted this morning and 7 wouldn't boot, just hung at the splash screen. Rebooted and tried the recovery deal about half a dozen times with no luck. I was running out of time to go to work so I didn't try to recover the Windows backup I'd taken the night before but just restored my XP backup. Sure got to know event manager (which is really good in 7) and do research on event ID 55 but I never figured it out. Oh, also chkntfs d: which I'd never known about (and don't want to know about). Yup, I had the latest BIOS and drivers so that can't be it so I'm guessing a compatibility problem with the SATA controller, my SATA drives and 7 or at least that's the only thing I can think of. 7 continues to run just fine on the old box....

Randy Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 22 Mar 2008 Location: USA, Georgia Posts: 15255	Quote Reply Posted: 01 Jan 2010 at 7:44am
	Ouch! That's worse than untangling your monofilament line after you let the drum free spin on your reel. When working with the old machine did you have a successful back up and restore? Maybe 64 bit related? Thought this might be of some help: Post 11 on this thread has no solution but he details out his problem: http://forums.techpowerup.com/showthread.php?t=111139 Another guy seemed to solve his problem: "I appear to have resolved the errors by removing the offending folders." Something someone else tried: ok, deactivating write cache buffer flushing does not have any effect on this issue. I noted a reoccurance of Error ID 55 (NTFS) on one of the machines already. This seems to be the most promising thing I've found so far, switching from Avira to WSE seemed to have helped this guy: "This seems to have done the trick. No more Event ID55 Ntfs issues over the past few days. Btw. Avira messes up the taskbar icons as well as avgnt.exe is still listed after removal. Some icons are offset and do not correspond with the entries anymore. Ereasing the IconCache.db file does not help. Any ideas? This is the Notification Area Icon list." ... and as a side note, "Switching one of the non affected machines to MS Security Essentials too seems to have solved another problem: the CREATIVE Autoupdate software does now recognise the hardware installed ;-) X-FI Platinum Fatal1ty Champion."

Don Watkins Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Admin Group Admin Joined: 14 Mar 2008 Posts: 22195	Quote Reply Posted: 01 Jan 2010 at 8:29am
	Don't see why 64 bit would effect it but I'm 64 bit on the other machine, too. Saw that thread and tried disabling write caching and tried switching to WSE as well as running with no AV software at all. As for removing the offending folders those that I could identify were volume shadow copies. I did remove them but the errors started cropping up again. I do think the errors were VSS related or at least that's when most of the errors would crop up but I tried everything I could find on fixing it and none of those made a difference either.

Karl_db Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 12 Mar 2008 Posts: 29259	Quote Reply Posted: 01 Jan 2010 at 2:25pm
	Was the spare drive a Raptor? So the only difference was the drive and the channel?

Don Watkins Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Admin Group Admin Joined: 14 Mar 2008 Posts: 22195	Quote Reply Posted: 01 Jan 2010 at 3:45pm
	No, the spare drive was a WD Black as was the 2nd drive that kept going EID 55 when I tried to back up to it.

Karl_db Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 12 Mar 2008 Posts: 29259	Quote Reply Posted: 01 Jan 2010 at 5:01pm
	Haven't been to MS site to check, assume you have. Did do a Google search. Mostly scanned the results and noticed a lot of "64 bit" references in the hits. But I'm lazy...and didn't click on every result to see. From what I've ran into...it really sounds like something with Win7 itself...that's conflicting with a lot of different products, hence there seems to be many "solutions": http://techblog.avira.com/2009/11/26/chkdsk-in-windows-7/en/

Don Watkins Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Admin Group Admin Joined: 14 Mar 2008 Posts: 22195	Quote Reply Posted: 01 Jan 2010 at 5:05pm
	Hehe, well, it's not like there aren't twenty bazillion permutations of hardware out there. I'm checking Asus daily, I expect a fix will show up there as I think that it's at the hardware microcode level

Karl_db Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 12 Mar 2008 Posts: 29259	Quote Reply Posted: 01 Jan 2010 at 5:12pm
	Well....that's why they (MS) gets paid the big bucks....(both jesting and serious).... It sure sounds like it. Something not quite kosher when the hardware and a driver is chatting?

Don Watkins Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Admin Group Admin Joined: 14 Mar 2008 Posts: 22195	Quote Reply Posted: 01 Jan 2010 at 5:18pm
	It'll get fixed, either with a BIOS update or a service pack and it'll be very quite and one day it'll just start working....

Karl_db Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 12 Mar 2008 Posts: 29259	Quote Reply Posted: 01 Jan 2010 at 5:22pm
	So...does this mean you're back to XP...or just have to use a different drive/rig?

Don Watkins Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Admin Group Admin Joined: 14 Mar 2008 Posts: 22195	Quote Reply Posted: 01 Jan 2010 at 5:25pm
	I'm back to XP on my main machine, just can't have anything that's not 100% solid. I'll keep plugging away at it but won't switch until I'm 100% certain. But I'll continue to use 7 on my play machine. It's been solid there even though Asus says 7 isn't supported. The only problem is that if it goes into hibernate mode it throws off a HAL error that sounds like the world has ended but has never caused a real problem. I fixed it. I turned off powersave.

Karl_db Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 12 Mar 2008 Posts: 29259	Quote Reply Posted: 01 Jan 2010 at 5:32pm
	Good fix! A while back you had some "I fixed it" stuff. An email? Anyhow...did you know there's a web site called that?http://thereifixedit.com/

Don Watkins Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Admin Group Admin Joined: 14 Mar 2008 Posts: 22195	Quote Reply Posted: 02 Jan 2010 at 2:10am
	Haha, that's funny stuff. My fix wasn't nearly so elegant. I was trying to remember that error message this morning and just couldn't but it was akin to the memory catching on fire.

Randy Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 22 Mar 2008 Location: USA, Georgia Posts: 15255	Quote Reply Posted: 02 Jan 2010 at 9:22am
	LOL! Loved these on that site: http://thereifixedit.com/tag/computer/ ... especially the gas powered fan on the PC in the last pic.

Karl_db Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 12 Mar 2008 Posts: 29259	Quote Reply Posted: 02 Jan 2010 at 9:39am
	HeeHee ROFL I hadn't seen that one. Hope it's well anchored!! I kind of liked the mod to the old CRT monitor. Here. I've been wondering what to do with mine.

Randy Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 22 Mar 2008 Location: USA, Georgia Posts: 15255	Quote Reply Posted: 02 Jan 2010 at 10:39am
	Looked like the perfect choice to me.

Don Watkins Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Admin Group Admin Joined: 14 Mar 2008 Posts: 22195	Quote Reply Posted: 02 Jan 2010 at 11:20am
	I had a bit to fool around with it so I restored the backup and it failed just like it did after the backup. Figured that would be the case but I had it so... Reinstalled from scratch, didn't installed ANY third party stuff, not even AV and ran backup first thing. Same Event ID 55 and backup failure. It's a hardware thing.