[Deland01]

Ever since I installed XP X64 (clean install) I keep seeing the following error when I boot the system up. The error doesn’t happen every time just one in 3 times. Does anyone have any idea what it means or how to resolve it?


STOP 0x00000050 (0xFFFFFADF44307FFE, 0X0000000000000000, 0XFFFFFADF2842C2E0, 0X0000000000000000)

disk.sys - Address FFFFFADF2842C2E0 base at FFFFFADF2800 Datestamp 45d69708

Any suggestions?

[cluberti]

Usually a stop 0x50 is a page fault in nonpaged pool, and if disk.sys is doing it I'd be very suspect of anything hooking hard disk access or potentially faulty disk drivers or the underlying disk hardware itself. Have you tested your disks to make sure they're OK? I'd start there, then I'd move up the chain and make sure the disk drivers / chipset drivers themselves are of the latest version, and then I'd make sure it wasn't your antivirus package, in that order.

[ThorGoLucky]

I'm getting the same problem in x64. A possible clue is that manually launching Valve Steam often triggers the same blue screen error too.

An overnight Memtest86 test passes. BIOS and drivers are up to date. Temperatures within specs. Hmm.

Supermicro MBD-X8STE-O motherboard
Intel Core i7 920 Nehalem 2.66GHz processor
OCZ Platinum 12GB DDR3 1333 (PC3 10666) memory
Western Digital Caviar WD1001FALS 1TB hard drive
Windows x64 fully updated

[ThorGoLucky]

The problem went away after removing a couple of memory modules, reducing the total memory from 12GB to 8GB. Again, hmm.

[ThorGoLucky]

I wrote too soon. The problem returned shortly after reducing the memory size. So I bought new memory that was on the motherboard compatibility list and that fixed the problem.....for about a week. Back to the intermittent blue screens, especially when Steam connects. WTF?