"ntfs.sys" BSOD during fresh win7 install

[CakeMonster]

I've put together a pc from parts from other computers, all of the parts have been working before i moved them so I doubt any of them have gone bad right at this moment.

However, I get a BSOD with "ntfs.sys" during Win7 install. It can happen right after I boot from USB or DVD, or it can happen as late as after during the file copying after the partitioning phase, but I've never gotten past the install.

I am really out of ideas now, does anyone have any ideas what it could be?

 

[mvbighead]

Download Ultimate Boot CD. Test the RAM, and test the hard disk for bad sectors.

It may be possible that your working parts are not compatible together. IE - I've seen some older memory that works in one MB but not another, etc.

 

[ch33zw1z]

Like mvbighead said:

1. Memtest86+ for memory diagnostics

2. hard disk diagnostics

 

[Soundmanred]

How many hard drives do you have hooked up?

 

[denis280]

I've put together a pc from parts from other computers,

What are those parts.

 

[Ketchup]

Some more details about parts and the exact error message would be helpful, but this error usually occurs when the installer can't recognize the data that was stored in RAM. Hopefully, memtest can tell you which stick is at fault (if more than one).

This can also occur when the file system is corrupt, but since this is a fresh install, that would be less likely unless the hard drive is in REALLY bad shape.

 

[CakeMonster]

Thanks for the input. After starting to pull out parts, it turned out that it would reliably crash with one of the ram sticks in the set (Corsair XMS3 1600), while with the other stick it won't. The funny thing is that these two have been running for 2 years in the main pc of a friend of mine who I game with regularly and who has never complained about crashes. Yet installing windows makes it crash apparently. The mobo is also the same that it was used with before (P8P67) so this is strange.

I guess I'll have to go hunt for some new ram now.

 

[ch33zw1z]

Memtest86+ will confirm a failure. Chances are those sticks have lifetime warranty through Corsair...just don't peel the labels off of them!

 

[CakeMonster]

Ok, both sticks pass, separately and together. Not sure what to do here because this is all I have. It appears to be stable after the installation, I will run some tests on it and see what happens, but I do feel a bit wary of giving it away considering what I experienced that was so clearly tied to that one stick....

 

[ch33zw1z]

1 pass does not a stable dimm make

I wouldn't trust them either. Memtest86+ for 24 hours

 

[Ketchup]

... but I do feel a bit wary of giving it away considering what I experienced that was so clearly tied to that one stick....

Did you figure out which stick it was? Memtest isn't perfect.

 

[CakeMonster]

Yep I know which one. It doesn't look any different physically.

I will try and run memtest overnight then.

 

[CakeMonster]

Tried to run the pc with windows installed one stick at the time now, and it will BSOD with the bad one, usually before I get into windows. Same memory slot. So its pretty safe to say that that's it.

BUT I ran memtest86+ for ~20 hours and it did not fail once on that stick. Now I just wonder if there's any point in RMAing it because I can imagine what kind of nightmare that could turn out to be...

 

[Steltek]

Is there a BIOS update available for the machine? Also, have you tried resetting the CMOS memory to defaults and then re-entering your BIOS settings?

Concerning the RMA, I'd just tell Corsair that you are getting random failures that you've traced back to this one module. I doubt they'll give you much of a problem with it. I presume that you've checked the BIOS to make sure that the system is properly detecting that module with the right memory timings?

 

[CakeMonster]

Yep, ran it with XMP, and with 1333 and 1600 manually. BIOS is latest which I updated before I installed anything. I have not tried reset CMOS, I will do that too but I doubt that any BIOS settings would so specifically fail with one specific module.