Quote:
Originally Posted by Phil^
hm, sounds like hardware issue then.
perhaps overheating?
|
I'm pretty sure that my mates checked that for me and said it was fine. Also wouldn't that cause more of a problem when it has been on for a while rather than when first loading up after a few weeks off?
Quote:
However, goto your control panel->administrative tools and open the event viewer and look for entries with a red cross next to them.. see if there's any consistancy in the errors reported and if any relate to a specific file or program.
|
One that seems to reappear is:
=========================
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 06/01/2006
Time: 10:18:11
User: N/A
Computer: REBORN
Description:
Error code 1000000a, parameter1 00000520, parameter2 00000002, parameter3 00000000, parameter4 804ee011.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 35 32 30 2c 20 000520,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 65 00, 804e
0050: 65 30 31 31 e011
=========================
Details
Product: Windows Operating System
Event ID: 1003
Source: System Error
Version: 5.2
Symbolic Name: ER_KRNLCRASH_LOG
Message: Error code %1, parameter1 %2, parameter2 %3, parameter3 %4, parameter4 %5.
======================
then in the more help section the:
filename is always faultrep.dll
version 5.1.2600.2180
=============
sorry about just giving you all that, it just means nothing to me so I have no idea what is useful