• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

randomn restarts

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

RIPSTER

Member
Joined
May 1, 2004
Location
England
I have windows XP pro SP2 installed, I am getting randomn irregular restarts, I cant seem to find the problem ive installed all updates for windows, When windows loads from a random restart it comes up with a send error report saying "windows has recovered from a serious error" so im guessing this rules out psu problems seeing as its a windows error, If anyone could give me any info on how to solve this problem I would be very grateful.


thnx in advance

RIPSTER
 
Open Event Viewer (Start | Run | Type eventvwr.msc, and click OK), in order to access the error logs and check for any critical errors | Highlight both "Application" and "System" independently in the LH pane | Right click a couple of the newest crtical errors you've received (critical errors are in Red), and select "Properties" | Copy and paste (use the "Copy to Clipboard" button under the arrow butons in the Event Properties" window) a couple of the latest critical error messages as they appear under the "Description" field, and post them in this thread.
 
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 14/05/2006
Time: 14:32:41
User: N/A
Computer: MS
Description:
Error code 0000001a, parameter1 00041284, parameter2 dc7c0001, parameter3 000027b9, parameter4 c0c00000.

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 30 30 30 30 30 30 31 0000001
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 34 31 32 38 34 2c 20 041284,
0038: 64 63 37 63 30 30 30 31 dc7c0001
0040: 2c 20 30 30 30 30 32 37 , 000027
0048: 62 39 2c 20 63 30 63 30 b9, c0c0
0050: 30 30 30 30 0000

-----------------------------------------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 14/05/2006
Time: 14:31:37
User: N/A
Computer: MS
Description:
The General Purpose USB Driver (adildr.sys) service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------------------------
Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 14/05/2006
Time: 04:23:23
User: N/A
Computer: MS
Description:
Hanging application IEXPLORE.EXE, version 6.0.2900.2180, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 49 45 58 50 4c 4f IEXPLO
0018: 52 45 2e 45 58 45 20 36 RE.EXE 6
0020: 2e 30 2e 32 39 30 30 2e .0.2900.
0028: 32 31 38 30 20 69 6e 20 2180 in
0030: 68 75 6e 67 61 70 70 20 hungapp
0038: 30 2e 30 2e 30 2e 30 20 0.0.0.0
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 30 30 30 t 000000
0050: 30 30 00

---------------------------------------------------
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 14/05/2006
Time: 03:06:19
User: N/A
Computer: MS
Description:
Faulting application explorer.exe, version 6.0.2900.2180, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x00009f50.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 65 78 70 ure exp
0018: 6c 6f 72 65 72 2e 65 78 lorer.ex
0020: 65 20 36 2e 30 2e 32 39 e 6.0.29
0028: 30 30 2e 32 31 38 30 20 00.2180
0030: 69 6e 20 6b 65 72 6e 65 in kerne
0038: 6c 33 32 2e 64 6c 6c 20 l32.dll
0040: 35 2e 31 2e 32 36 30 30 5.1.2600
0048: 2e 32 31 38 30 20 61 74 .2180 at
0050: 20 6f 66 66 73 65 74 20 offset
0058: 30 30 30 30 39 66 35 30 00009f50
0060: 0d 0a ..
-------------------------------------------------

thats is what I could find the first two are from system and the second two from application some of the descriptions dont seem to be associated with the restarts,

thnx

RIPSTER
 
Have you made any alterations to the Windows Paging File, or edited the Memory Management sub-key in the registry? Under System properties --> "Advanced" tab | Performance --> "Settings" button | "Advanced" tab --> Memory usage... is it set to "Programs" or "System cache"?
 
What's your reply to my other question?...
Have you made any alterations to the Windows Paging File, or edited the Memory Management sub-key in the registry?
... and have you checked your RAM using Memtest?
 
no changes made to memory managment or paging file, I suspected one of the chips of RAM that Ive had from the begining of this setup to be dodgy, I replaced it and then tested each seperatley, I thought I had solved the problem by swapping it out till 5 mins ago when the pc restarted :(.
 
I was looking under system properties in control panel and found the startup and recovery section, I unchecked the box restart after system failure I reckoned that next time my pc crashed instead of restarting I would get a BSOD, well I was right I got a BSOD I wrote down the info-
-------------------------------------------------------------------------
A problem has been detected and windows haws been shutdown to prevent damage to your system

IRQL_NOT_LESS_OR_EQUAL


(load of moaning about restarting in safe mode and removing any recent new hardware)

Technical Information-

*** stop: 0x0000000A (0x00004008, 0x00000002, 0x00000000, 0x804f2178)

Beginning Physical Dump Of Memory

--------------------------------------------------------------------------

I hope this can help with resolving this issue, I might just buy a 512mb Chip of RAM and a new HD and get this over with.

thnx in advance

RIPSTER
 
You may be required to increase the Vcore if OC'ing your processor. That looks like the typical symptoms of an unstable CPU OC. Did you run Prime95?

I used to get that BSOD when my processor chip didn't have enough Vcore or was at a wall. :mad:

But, because you have a PIII system in your sig, your PC likely has bad caps. Did you check the caps on the motherboard?
 
Back