File XFR Between DualBooting Causing CHKDSK

[2therock]

I Dual boot with a WD640GB (Black) RAID1 Array in Vista x64 and Windows 7 Pro on a WD1TB (Black) stand alone disk.

All is well until I move files between the two Hard Drive sets.
Example: In Vista, I open a MS Office 07 excel document and make my changes and save. I then click "Save As" and shoot it to the HDD Win 7 is on in the User\Me\My Documents folder.
This is so when I need to work with it and I'm in the other OS I'm good.
I have also opend a office document from one OS that was in another and saved it in place.

Then I get the CHKDSK in restarts. It is always when booting into Vista. I blame it on the file transfers or cross OS saves because I see the files in question listed durring the CHKDSK process.

When I finally get to the Vista desktop Intel Matrix Storage Manager (IMSM) rebuilds or repairs my RAID set.
It does not happen again until I work as stated above.

Well today after such a session it would not boot back into Vista. No CHKDSK, just a tiny flicker of a BSCOD and a loop.
So at the OS option I chose Win7 and installed Intel Matrix Storage Manager there and let it repair the RAID set from there.
I rebooted and Vista came up and again with (IMSM).

Well I will learn and not do the document thing again and am about to ditch the Vista all together but wanted to put it out here incase I can get some do's and dont's input from you guys.

Can I expect this when doing other mass file transfers that are not the result of a save as?

 

[usasma]

Please run this on the Vista installation: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Does the Win7 installation get BSOD's? If so, run the above tool on it also.

 

[2therock]

Please run this on the Vista installation: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Does the Win7 installation get BSOD's? If so, run the above tool on it also.

No, the Vista gets the BSOD when trying to boot. Just a tiny flicker. I booted back to 7 and ran the Intel Matrix Storage Manager and she went back OK.

As long as I do not drag and drop office documents across OS's HDD's it's fine. It may just be going from My documents to My documents but I'm not gonna do it any more.

 

[usasma]

Please run this on the Vista installation: Blue Screen of Death (BSOD) Posting Instructions

 

[2therock]

Do I post and attach the results here?

 

[usasma]

Yes. If using the Quick Reply section, select the "Go Advanced" button. That'll take you to a page where you can attach things.

Below the text window are Additional Options
In that section is a sub-section to Attach Files

 

[2therock]

Thanks,

I uploaded it and named the contained .html file BCOD_HTML.
You told me to run it in Vista so here are the stats..... I have the Win7 ran also if needed.
The Vista is a OEM x64 disc purchased @ newegg.com.
The Win7 is a OEM x64 disc purchased @ newegg.com.

I assembled the machine with loving care and installed both of the OS's. I am very selective in the software installed and keep it updated.
I purchased the Motherboard in 11/19/2008 and promptly assembled the system with Vistax64 on the WD640GB Black HDD's and all new parts. She has been FLAWLESS.

The Win7 has been installed since 3/17/10 on the WD1TB HDD to accommodate a Beta project for Adobe running the pre-release CS5. I ran CS5 alone installing NOTHING else until after the final release and am now migrating.

You will a see a 1394 device that is not enabled. This is my PCI Koutech model 1314, 3+1 Port FireWire/1394b & 1394a PCI Host Controller. I use it for fast Compact Flash XFR's with a Sandisk Extreme Firewire reader. For some reason it gets listed twice in device manager. Once where it belongs, and again in the network category as disabled. I have never went after this as the machine runs great.

The errors or problems contained in this thread are the ONLY problems I have ever had across both OS's. She is my Baby.

MoBo= GA-EP45-UD3P
CPU= Q6600 - Stock Clock / Lapped w/Roswell cooler.
RAM= 8GB 4 X 2GB CORSAIR XMS2 DHX DDR2 - Voltage @ 2.1 (MFG Recommended)
PSU= 620W CORSAIR CMPSU-620HX Modular
GPU= POWERCOLOR AX3650 512MD2 Radeon HD
HDD= WD Black 640GB @ RAID-1 Vista x64
HDD= WD Black 1TB Windows 7x64 Pro
HDD= WD Green 750GB Storage
External eSATA HDD Box w/WD750GB RE2 x2 @ RAID1
External HDD= WD MyBook 500GB USB Misc Storage
Dual Booting to Vista x64HP & Windows 7 x64Pro
Dual Samsung SyncMaster 215TW displays.

Happy Thanksgiving !

 

[usasma]

There are no memory dumps in this file. There are 2 listed in the MSINFO32 file - from Dec 2009 and Jan of 2010
I'm looking for this most recent Blue Screen of Death memory dump file.

Most often it's in C:\Windows\Minidump. But if it's not there, then it's usually a file named MEMORY.dmp in the C:\Windows directory (if it's this one, it'll be huge - so zip it up and upload it to a free filehosting service. Then give us the link to download it from)

The event viewer for the system logfile shows corruption in the file system every day or two. And every day or two it is successfully repaired.
So, I'd suggest running hard drive diagnostics on ALL of your hard drives using these free tests: HD Diagnostic (read the details at the link)

 

[2therock]

Thanks,

I have no .dmp files on either OS drives. I did a *.dmp search on both drives (indexing is disabled).
The drives you see toggling may be because I was persuaded to turn off TLER at one point and will have to check. I remember discussing it but cannot remember if I did or not. This will persuade me to keep a journal starting now.
Do you know how I can look to see if it is on or off?

I want to elaborate on my BSCOD one more time about it being so fast if one blinked he would miss it. Perhaps it was not a BSCOD?

 

[usasma]

There are other things that can cause a flash of blue as the system reboots. I haven't seen them very frequently, but I seem to recall a flash of a blank blue screen at work at one point (can't recall the cause or the fix).

I don't know what TLER is, so I don't have any suggestions. I still suggest that you run the hard drive diagnostics to be sure that the drives aren't failing.

Please look at this link for the appropriate settings for your memory dump files: Set MiniDump If those settings are correct, then it's likely that there's a reason that the system isn't collecting them. Why? Well, that's a long involved process. Have you tweaked any settings about error collecting or about temp file space? Have you messed with anything in WMI (since there's no report of the BSOD). When exactly in the process does the BSOD happen? Is it in the boot process, or after the system has been up and running for a bit?

FWIW - I had some issues with collecting dump files when I was using RAID (I had a HighPoint Controller). It wasn't constant, but it did skip a few. I wonder if the 3rd party RAID drivers are robust enough to survive a crash and let the dump be written to the hard drive(s) without corruption (if Windows determines that the dump is corrupted, it won't let it be written).

I wonder about the PSU's ability to handle all that power draw. Can you disconnect some of the drives (including internal and external) and one of the monitors?

I do recall, quite some time ago, that we saw some issues with the GA-EP45 series of boards. I haven't seen any of these in a long time, so it may not be significant. My suggestion for this is to visit the Corsair website and obtain the exact settings/timings/voltages for your system - and then set those settings/timings/voltages in your BIOS (in other words, DO NOT use any of the Auto settings for the RAM in your BIOS).

 

[2therock]

Thanks,

TLER is a correction thing for HDD's in WD anyway and some disable it to squeeze a little more speed. I may have made the tweak. It has to do with the amount of seconds the drives give each other to correct them selves in RAID. I will be enabling it if indeed I did tweak it.
I have not messed with the settings you asked me about.
My OP explains when I xfr files between OS HDD's and restart I got CHKDSK.

• What I do is in Vista I open an explorer window to the My Documents folder.

• Then another explorer window showing the HDD Win7 is on with the My Documents folder open there.
• Then I drag and drop (copy) files from the vista HDD My Documents to the Win 7 My documents folder.
• Then when I boot to Win7 it does a CHKDSK on the Vista Raid set and the files I copied are in the list of what it's doing. It moves fast but I managed to see it say "Deleting" reference I think?
• Then I boot back to Vista and it repeats.

Then its all good until I do it again. If I do not move files it does not CHKDSK when booting to and fro. The files are Office 2007 .xlsm files.
I decided to stop doing it.
I am planning to format the Vista RAID set and move Win 7 into it. The Win 7 has won me over and I'll be ditching the vista.
Is there a way to check the HDD's in a RAID set for errors? WD's Lifeguard will not do it. If not I'll just format and make them stand alone and check them out before moving it al over with Acronis.

Thanks Again

 

[usasma]

The RAID set should be self-testing (my RAID controller listed it in the RAID BIOS).
This is separate from the HDD diags. You should be able to run the Seagate Seatools on most RAID controllers - but that's 100% sure. Also, in some BIOS's you'll have to disable AHCI and set the drives as something else (usually IDE) to get the tests to work.

Worst case is that you have to use the Windows tests on the HDD's - or slave the HDD's to another system and test them there. All of this difficulty is the reason that I gave up RAID.

Good luck!

 

[2therock]

Thanks, I'll get it eventually. I do know Intel's Matrix Storage Manager seems to look them over pretty good. But I will do some other tests to be sure before changing the set to run Win7. I'm using the MoBo's Intel RAID controller.

I Run RAID1 on my OS so I can keep rolling if one dies and avoid a time sensitive recovery. As a photographer/investigator I need to avoid the downtime if I can. It proved good once when a WD640GB failed and she rolled along until I got the RMA completed. I slapped her in and she rebuilt. I also run backups to another external eSATA RAID1 set.