DFI 855GME NO_MORE_IRP_STACK_LOCATIONS
OK, Jennie installed iTunes and the next thing I know, I start getting a strange stop code, the machine just blue screens and then on every subsequent restart has the same problem called the NO_MORE_IRP_STACK_LOCATIONS Stop 0x00000035. Lots of digging to figure out why, the long and short of it is that I can boot to safe mode, uninstall the nVidia 6800GT driver and then the machine boots and you can reinstall the driver.
This happens mainly when playing games, so it feels like I've found some bug somehow and I'm not sure how iTunes caused it, but it does seem like that is a coincidence.
Not clear how to fix, but installed the 71.x beta drivers and that did not help.
Other possible causes are noted below:
Common Stop Codes. NO_MORE_IRP_STACK_LOCATIONS 0x35 With this code, if you've added a new virus scanner or someone has accessed a shared volume over the network for the first time on the machine, the Server device driver can be at fault. The Server device driver constructs I/O request packets with a slot for every device driver on the path to the disk. Sometimes the number of I/O request packets the Server device driver allocates is insufficient, resulting in this Stop Code. Try increasing the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ServicesLanmanServer\IrpStackSize setting to a number higher than 4 (or whatever it's set to) and see whether the problem goes away.
* "USB Device plugged in":http://forum.pcstats.com/archive/index.php/t-19198.html. It's a uncommon error that you'll likely to get if you have any sort of USB device plugged in during the installation. the problem is caused by the invalid IO driving loading paremeter for the certain USB device. Also if you have a copy of "GO BACK" installed on the current HDD get rid of it. If none of these two solutions fixes your problem i would try a complete reformat of the HDD from a bootup disk.
* "Bad Memory or driver":http://www.hardwareanalysis.com/content/topic/27947/. Like me this fellow found out that it was a bad video driver. With me, something keeps corrupting it for once I reinstall the nVidia driver, the problem returns. Other alternative is bad ram or too much overclocking (right now my 1.8GHz Pentium M is overclocked to 2.15GHz and the memory from DDR333 to DDR400).
So that something fun to try, fixing some mysterious registry setting.
Other folks have found the bug with Norton Ghost and USB 2.0 flash drives, but that doesn't seem related. There is also an old post on Windows NT having to do with Intellitype 2.0 but that doesn't seem related either.