Posted 04 February 2009 - 09:18 PM
If you think it's networking-related...try uninstalling your NIC drivers (using Device Manager) and then try to boot. In fact, if you can get into the BIOS...disable the NIC...and then try to boot.
That will at least confirm/refute one possible source of driver trouble.
Very difficult to troubleshoot, following is from a very good website:
This is a very common bug check. To interpret it, you must identify which exception was generated. May also be reported as 0x1000008E.
Hard disk damage or failure
Configuration problems with the BIOS, memory, hard disk, or other devices
Incompatible device driver
You receive a Stop error message that resembles the following:
***Stop: 0x0000008e (parameter1, parameter2, parameter3, parameter4)
Stop error message on a blue screen when you transfer data to a USB device in Windows XP
When you try to transfer data to a USB (universal serial bus) device, you may receive an 8E Stop error message on a blue screen. You may see reference to the Usbser.sys file on the blue screen.
A "STOP: 0x0000008E" error message occurs when you change the hardware acceleration setting
When you try to change the Hardware Acceleration setting in the Display tool in Control Panel from None to Full, you may receive the following Stop error message in Win32k.sys: STOP: 0x0000008E (c0000005, bf875fc3, f07bcd48, 00000000)
You receive a "Stop 0x0000008E" error message after you resume your laptop computer
When you resume your laptop computer, Windows XP may stop unexpectedly (crash), and you may receive the following error message: Stop 0x0000008E
"STOP 0x0000008e" error message during Windows XP setup
When you install Microsoft Windows XP, you may receive a Stop Error message that is similar to one of the following while the Setup program is running:
STOP 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA
Additionally, if you troubleshoot by removing all unnecessary hardware devices that are installed on the computer, and then you run the Setup program, you may receive an error message that is similar to the following: Setup cannot copy the file Setupdd.sys.
Stop 0x0000008E" error message in Win32k.sys when you use the keyboard to access a program menu in Windows XP.
On your Microsoft Windows XP-based computer, you receive a Stop error message that is similar to the following: STOP 0x0000008E The Stop error occurs in the Win32k.sys driver. You may receive the Stop error when you use the keyboard to activate and control the menu items of some programs.
STOP 0x0000008E (0x00000005, 0xBF869F22, 0xF9470688, 0x00000000)
A "STOP 0x0000008E" Error Message Occurs in Wdmaud.sys
A "STOP 0x0000008E" error message may occur in Wdmaud.sys.
Random "0x0000008E" Error Message on a Blue Screen in Windows XP
When you run Microsoft Windows XP, you may randomly receive an error message on a blue screen that references a bugcheck ID 0x0000008E (KERNEL_MODE_EXCEPTION_NOT_HANDLED) error.
You receive a 0x0000008E Stop error message when you cancel a print job in Windows XP
You are using a computer that is running either Microsoft Windows XP Home Edition or Microsoft Windows XP Professional Edition, and you print a document. If you click Cancel in the Printing dialog box, you may receive a 0x0000008E Stop error message.
STOP 0x0000008E error message on a blue screen and your computer does not enter hibernation or standby after you remove an IEEE 1394 storage device
You may experience one or more of the following issues after you remove an IEEE 1394 storage device, such as a CD-ROM or external disk drive, from your Windows XP Service Pack 1 (SP1)-based computer: When you put your computer into hibernation, you may receive a Stop error message similar to the following on a blue screen: *** STOP: 0x0000008E (0xC00000005, 0x804EF844, 0xF89463FC,0x00000000)
When you put your computer into standby, the monitor turns off as expected, however the computer does not enter standby. The power indicator on your computer indicates that the computer is not on standby.
As you can see, quite varied and elusive.
Since your RAM has the "all clear" from Memtest...looks like drivers are primary suspects.