Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Intel Corporation (INTC) -- Ignore unavailable to you. Want to Upgrade?

To: Paul Engel who wrote (150476)	11/29/2001 11:20:13 PM
From: ptanner	Read Replies (1) \| Respond to of 186894

Paul, re: "Your initial problem - according to you - was a memory failure - was it not?" I frankly didn't know what the problem with the machine was and set it aside until I found the patience to investigate. Each crash gave a nice BSOD with a cryptic (to me) message of the following sort: * STOP: 0x0000007A (0xE1C06384,0xC000000E,0xA00D12ED,0x0AE58860) KERNEL_DATA_INPAGE_ERROR * Address A00D12ED base at A0000000, DateStamp 3aa010b4 - win32k.sys However, I forgot something important which I rediscovered during last nights investigation: when trying to restart the system after a crash it could not find the HDD. So the problem was likely due to the hard drive failing to respond to some request by the OS. I had tried different sticks of Crucial memory with the system at default settings and experienced the same problem so I felt it was limited to the motherboard and/or HDD. With a replacement drive all appears well but it is too early to say - the testing will continue for a while before I return the system to service. Sorry for any confusion but the only memory failure was my own. <g> -PT