Travel Technology - BSOD 0x000000F4

Got this error a few times today on my car computer after about 45min or so driving. Everything works, then music stops and the blue screen with stop 0x000000F4. I think from what I read online my hard drive is dying slowly. I did though replace the motherboard with a new one without reinstalling windows, but it did work fine last weekend on a 5hr drive....

This means it got an error reading or writing to the pagefile on the disk.

First, if it's not a laptop, check to see if your hard drive is jumpered as slave without a master drive connected. http://support.microsoft.com/default.aspx?scid=kb;en-us;330100

Second, try reallocating the pagefile. (For XP, system control panel, Advanced, Performance Settings, Advanced, Virtual memory change). If it's not set to custom, change it to that and used the recommended size that's shown below. You can change it back after rebooting. The idea is to get it to recreate the pagefile.

If this doesn't work, get the drive diagnostic program from the website of the drive maker and run it on the drive.

Could it simply be heat? Is the carPC cooled sufficiently?

I'd seriously consider either a shock mount or a large SSD for a car PC, I am looking into this myself and the biggest problem I have in driving is burning CDs or intensive reading due to bounces causing the heads to jump.

Heat I don't think is an issue as a/c blows over it. I will be moving to a CF card method with EWF and it should work good, but I didnt have no problems for over a year now.
Ill check the HDD and paging files settings later this weekend when I get a chance.

Turned off paging.
works now for about 5min before it reboots.
I also got this error message today.
"NTOSKRNL.EXE is missing or corrupt."

So as it looks either the windows got messed up badly, or most likely the HDD is failing. Looks like time to go shopping for a new one. I think it all started when I mounted the HDD vertically, not horizontally.

99% it's the hard disk. The "missing" NTOSKRNL.EXE is because it can't read it from the drive.