RJARRRPCGP

Are you overclocking your processor core? That can cause that error when the processor core is running faster than it can handle.

Looks like a malware attack. The only other thing that I'm aware of that can hide space is a hard disk drive with HPA set.

Loose RAM is also a possible cause! Gotten 0x0000008E before reseating the DDR 2 SDRAM on a HP PC.

There's a subcode, "D1", which does mean a bad driver. The more generic "a" variant always meant CPU corruption, when I received it.

I just noticed this, while OTOH, the build number looks right.

--> Looks like your processor is overclocked. --> This bugcheck code, when ending with "A" or "a", usually means CPU data corrupted. --> That's what happens when your processor is having computational issues, because of running at a frequency that your processor can't handle. Or your Vcore setting is wrong in the BIOS. Reminds me of my bad T-Bird overclocks back in 2002. I wouldn't be surprised if the Prime95 test fails on you. *IF* the stop error code ends with "D1", then it's usually just a pesky driver issue.

Security software may be obstructing! If you have Kerio or Winpooch, don't be surprised if you get a file-not-found error.

Huh, being optimistic here, Windows Update actually went fine with Service Pack 1 integrated. It's when I have zero service packs. And the updating appeared to actually go faster. I had positive results so far with Service Pack 1 on the DVD. Thanks for letting me know, but updates haven't failed so far.

O_O, that sounds like my Adaptec 29160 SCSI card and Plextor SCSI CD drives.

Intel is better under GNU/Linux than under Windows. From my experience, it's pretty much just the DirectX support that isn't too good. I just tested the one on my Acer Aspire M5630, the GMA 3100 and it works nice under Ubuntu. GMA 3100 don't suck like the 82815 did!

Windows Update has an issue where if you didn't install service packs yourself and if you try to get a service pack with Windows Update, the way that Microsoft wants home users to update Windows, then apparently, Windows Update then F-s up, it fails to install service packs before other updates! And thus, apparently, Windows Update keeps trying to install updates without prerequisites and thus Windows Update gives an error! Especially with an update for .Net Framework 3.5, you're probably gonna get a message from Windows Update telling you that it didn't complete and give you an error code! The only solution is to have the service packs installed manually BEFORE running Windows Update!

Looks like your hardware is majorly unstable. Looks like overclocking too much -or- need more Vcore for your CPU -or- you have faulty hardware. These symptoms may be caused by the processor heatsink having an obstruction! If you download and run Prime95, selecting "round off error checking" (or similar) and select "torture test", Prime95 should be able to tell you if your CPU is having a problem.

Did you even bother to view the PubMed entries? Chlorine Dioxide has been proven yet denied by the FDA because it cannot be patented and therefore not profited from. So you're saying that the FDA laws have been rigged by medicinal companies!

Likely a faulty HDD.

The readyboost driver in Vista indeed does not support exFAT, but Win7's does. Why did Disk Management even let me choose exFAT then? I cannot use Windows 7 at this time! (unless I violate the EULA)

/facepalm (I always install the chipset driver first)

A delay before it reboots sounds like the dreaded infinite loop problem crash problem I used to have. (That would occur when running Need For Speed III, in 2002, when Windows XP was the new kid on the block. (video) ) The symptoms would be that the video freezes for at least around 10 seconds then Windows reboots. (stop error, obviously!) (And in 1 case, when I was running Need For Speed III, the music would still be playing like nothing happened during the freeze before Windows reboots. LOL. ) -> The blame would go on the video driver. Do you have a "STOP: 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER" logged? Sounds like that problem may be back with Windows 7.

Not true, it's not the installer giving an error message. It's now obviously because the driver files don't have the right stuff and Windows has a hissy fit. The installer seemed to go through fine, it was Windows that rejected the driver.

It will act as if I tried to use a Unix file system! LOL! It will claim it only supports FAT32, FAT16 and NTFS.

Windows will refuse to use the driver and display the following error message (or similar) in Device Manager: The device cannot start. (Code 10) I don't understand, never a failure until this year! This was with a fresh Windows installation. And after downloading the April release of ForceWare, IIRC, from Nvidia's web site. Apparently, Nvidia lied, unless Nvidia F-ed up. Nvidia's web site still reported the GeForce 7600 GS being supported and Nvidia's web site didn't warn people about discontinuing AGP support, IIRC.

Likely a damaged or dirty DVD. Windows may log those errors when it just has trouble reading a DVD!

Yep, right on! It's got to be a stop error.

Possible cause: Your processor core is set to a speed it can't handle.

Heads up, DMA is disabled by default with Windows 98! You must enable DMA yourself!

I hope more people complain about this, because people likely are going to stop upgrading. (TBH, I may have to condemn Windows 7, this is bull, Microsoft, you seem to lately not care about advanced users.)