BSOD's on WinXP, totally random, multiple reasons

[rafalenew]

Hi


I am currently upgrading my computer with the following configuration

CPU - intel Core i3 2100 3.10ghz SandyBridge
Motherboard - intel DH67CL
RAM - G.Skill DDR3 2GB x2, 1.5v, 1333mhz, Dual Channel
HDD - Seagate 1TB SATA 6gb/s
DVD Writer
Onboard Graphics
Onboard Audio

Drivers - All original updated from intel.com
No Overclocking, stock BIOS
USB pendrive drivers
USB 2.5" WD Passport for backup

WinXP Pro SP3

New installation from on PC after full format, no imaging

Problem
PC isgiving me intermittent BSOD's with two reasons. I cannot reproduce or anticipate the BSOD, they might occur after 1hr or after 3hrs ??

PAGE_FAULT_IN_A_NON_PAGED_AREA fastfat.sys
IRQL_NOT_LESS_OR_EQUAL

I am at my wits end trying to understand the reason behind this. I have installed no new software, no device drivers. All external peripherals are old and well tested. I did have a hairy time moving WinXP to AHCI after installation, but it was working fine after that.

I have included dump files from several events to help understand the problem. I am currently not in front of this PC, so please bear me out.

What causes these BSOD's and how to remove them ??

 

[Route44]

Check you RAM voltage in the BIOS. Is it set at 1.5v as per the manufacture's specs? If not set it manually.

 

[Tmagic650]

Also, run memtest86 to check the memory after you confirm the voltage

 

[rafalenew]

Route44:

The RAM voltage is set at 1.5v, I checked.


Tmagic650:

I have not tried memtest86+, but Windows Memory Diag passed the memory. I will test the memory with memtest over the weekend.


Any other suggestions ??

 

[Route44]

Memtest is much more extensive thus T's suggestion. Usually when we see random BSODs with various error codes this is a strong indicator of memory issues.

For diagnostic purposes run Seagate's SeaTool hard drive diagnostics especially the long test but after you run memtest. Make sure that you allow it to run for a minimum of 7 Passes.

 

[rafalenew]

Route44:

memtest passed the RAM, I have included a pic of the final status.

I have not been able to surface scan the drive as yet, I hope to do it today. In the meantime I am trying to reinstall the whole OS and drivers etc.

I will report again in a few hours.

 

[Route44]

How went the hard drive diagnostics?

 

[rafalenew]

The HDD Surface scan was fine.

I have now reinstalled the whole OS, drivers, software etc.

BSOD's came again today.

They might be caused with True Crypt, I am looking into this

 

[Route44]

Attach those minidump files if you want.

 

[rafalenew]

I believe I have found out the problem. I use True Crypt 4.3a extensively for my office documents. I believe that FAT32 volumes of true crypt are causing all these errors in a multi-processor setting.

These two URL's also corroborate the issue faced by me.

Sorry cannot post


I have moved my documents into a new NTFS volume and am keeping my fingers crossed

 

[rafalenew]

www.bradmcallister.com/posts/windows-bsod-with-fastfat-sys-and-truecrypt

www.softblog.com/2008-02/the-hunt-for-blue-screen

 

[Route44]

NTFS is the better way to go in most cases. Please keep us updated.

 

[rafalenew]

Well, I am happy to report that the problem has been resolved completely.

It seems that the FAT32 volumes created under True Crypt have a tendency to cause Fastfat.sys related BSOD's under a multi-processor system. The problem persists in True Crypt v7 as well. The only work around is to re-format truecrypt volumes under NTFS or create new NTFS volumes.

 

[Route44]

Thanks for the update.