[Jonesey]

Hi there.

I've had a couple of random automatic reboots recently, and a 1 BSOD.

Before getting too involved in technical stuff, I was wondering if my temps & voltsages are ok.

These are the results from Everest:

Temperatures:
Motherboard 34 °C (93 °F)
CPU 39 °C (102 °F)
WDC WD2000BB-22GUC0 42 °C (108 °F)
WDC WD2500JB-00REA0 46 °C (115 °F)

Cooling Fans:
CPU 3013 RPM

Voltage Values:
CPU Core 1.46 V
+1.5 V 1.54 V
+3.3 V 3.22 V
+5 V 5.00 V
+12 V 11.86 V
-12 V -11.71 V
-5 V 3.55 V
+5 V Standby 4.92 V
VBAT Battery 3.20 V
Debug Info F FF 70 FF
Debug Info T 34 39 127
Debug Info V 5B 60 C9 BA C3 27 E0 (01)



Is this enough information for one of the experts to make a judgment?

If not, please let me know.



Many thanks,

Jonesey

[Advertisements]

Hello Jonesey,

It sounds to me alright. Maybe you have the memory problem. In order to troubleshoot the ram try run computer with 1 by 1 stick and let me know what happens.

Regards,

[mirjel]

Hello Jonesey,

It sounds to me alright. Maybe you have the memory problem. In order to troubleshoot the ram try run computer with 1 by 1 stick and let me know what happens.

Regards,

[happyrock]

have you added any new hardware or software recently...
updated windows or any other software just prior to having the problem...
what are you doing when you have the problem....
your voltage and temps look good...were the posted numbers after using the computer for awhile or at idle...

[Jonesey]

Hello Jonesey,

It sounds to me alright. Maybe you have the memory problem. In order to troubleshoot the ram try run computer with 1 by 1 stick and let me know what happens.

Regards,

Thanks mirjel - will get back to you when I've done this.

When I've got the covers off, I'll also clear out any dust, clean fans etc.

Won't be this week as I'm going on holiday tomorrow!!!!!

[Jonesey]

have you added any new hardware or software recently...
updated windows or any other software just prior to having the problem...
what are you doing when you have the problem....
your voltage and temps look good...were the posted numbers after using the computer for awhile or at idle...

Hi happyrck

No hardware/software added- I did remove Acronis trueimage.

All readings taken when idle.

I'll use it for a while then run the Everest report again.

I did run Registry Mechanic which found several file problems which were auto-corrected. Could this be a possible cause?
RM sets a restore point before removal which I can go back to if necessary

[happyrock]

did run Registry Mechanic which found several file problems which were auto-corrected. Could this be a possible cause?

yep...try to restore the" file problems"...
no joy ...
try system restore..

don't forget to run memtest...bad RAM can cause your symptoms too

Edited by happyrck, 05 July 2008 - 12:10 PM.

[Jonesey]

did run Registry Mechanic which found several file problems which were auto-corrected. Could this be a possible cause?

yep...try to restore the" file problems"...
no joy ...
try system restore..

don't forget to run memtest...bad RAM can cause your symptoms too

Ok - haven't tried any of the above yet, was just using the pc, nothing too taxing, playing a simple game of bookworm, a download running in the background, and Firefox/Outlook open when it craches again.

No BSOD, the pc just decided to reboot.

Once back up, I immediately ran another Everest report, results below:

Sensor

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


Sensor Properties:
Sensor Type Winbond W83627HF (ISA 290h)
Motherboard Name DFI LANParty Pro875 Series

Temperatures:
Motherboard 33 °C (91 °F)
CPU 47 °C (117 °F)
WDC WD2000BB-22GUC0 43 °C (109 °F)
WDC WD2500JB-00REA0 45 °C (113 °F)

Cooling Fans:
CPU 3154 RPM

Voltage Values:
CPU Core 1.44 V
+1.5 V 1.54 V
+3.3 V 3.22 V
+5 V 4.92 V
+12 V 11.92 V
-12 V -11.79 V
-5 V 3.55 V
+5 V Standby 4.92 V
VBAT Battery 3.20 V
Debug Info F FF 6B FF
Debug Info T 33 47 20
Debug Info V 5A 60 C9 BA C3 26 E0 (01)



Now - if I'm reading this correctly, then the PSU is putting out a voltage 3.55V when it should be -5.00V

Otherwise, the rest seem ok yes?

[mirjel]

Hello Jonesey,

It sounds to me alright. Maybe you have the memory problem. In order to troubleshoot the ram try run computer with 1 by 1 stick and let me know what happens.
Regards,

Thanks mirjel - will get back to you when I've done this.

When I've got the covers off, I'll also clear out any dust, clean fans etc.
Won't be this week as I'm going on holiday tomorrow!!!!!

Do this.

Regards,

[happyrock]

Windows XP is set by default to reboot your computer when it hits a critical error. For most users I suppose this is a good thing, as no one likes to see the BSOD (blue screen of death). But in this case, we actually WANT to see the BSOD because it contains some useful information in diagnosing the problem. In order to force your computer to show you the BSOD, you need to tell it to stop auto restarting on critical errors.

Right-click...My Computer... and then click ...Properties...
Click the ..Advanced tab...
Under Startup and Recovery.. click ..Settings... to open the Startup and Recovery dialog box....
Clear the ..Automatically restart.. check box, and click OK the necessary number of times...

Restart your computer for the settings to take effect....

[Jonesey]

BSOD message reads:

STOP: 0X0000008E (0XC0000005, OXBF800ADF, OXB6459CD0, 0X00000000)

win32k.sys - Address BF800ADF base at BF800000, datestamp 00000000

[mirjel]

That error usually points to a driver issue or the need for a bios update. Have you done anything to your ram what i suggested you. Try to switch the slot that your current ram is in or try run computer with one slot of ram.

Regards,

[123Runner]

Run memtest overnight on the ram. Do 1 module at a time.

Have you used or looked at the event viewer logs? They may tell you a great deal more about the error. Right click My Computer and choose Manage. In the left pane expand the event viewer and look at System and Application errors that are logged. Hilight the errors with a red x to learn more about them. Does it blue screen at random or only when running certain applications/programs?

Also check out WINDOWS ERROR MESSAGES

[mirjel]

Run memtest overnight on the ram. Do 1 module at a time.

Have you used or looked at the event viewer logs? They may tell you a great deal more about the error. Right click My Computer and choose Manage. In the left pane expand the event viewer and look at System and Application errors that are logged. Hilight the errors with a red x to learn more about them. Does it blue screen at random or only when running certain applications/programs?

Also check out WINDOWS ERROR MESSAGES

Hello 123Runner,

How he can use all of that with BSOD message reads:

STOP: 0X0000008E (0XC0000005, OXBF800ADF, OXB6459CD0, 0X00000000)

win32k.sys - Address BF800ADF base at BF800000, datestamp 00000000

Regards,

[Jonesey]

Hi guys, just a very quick update as I'm currently in work.

Last night I removed the covers and did a fairly throrough clean inside the box.

The worst of the dust & muck was inside the power supply, but all the fans have now been cleaned, heatsinks removed and cleaned etc.

Didn't have much time after this was done, but in the time it was booted up and running, I didn't get any crashes of any kind.

I reapplied some thermal compound between CPU & heatsink.

CPU temperature was running at 25C.

Re the memory testing - I've got 3 sticks, 1 x 1Gb and 2 x 256Mb = 1.5Gb overall.

Does anyone know where I can download memtest, or something similar?

Regarding drivers - the only thing I've been having problems with recently has been the cable modem drivers (Scientific Atlantic - Virgin/Telewest modem)


It might be worth mentikoning that I've only had ONE BSOD sinc ethis trouble started, and the message was reported above.

Thanks for all your time & consideration.

Jonesey

[Daz3210]

It could well be that the cleanout has solved your problems for you.

I had it with a machine where when I tried to run MS Flightsim (Nothing else) it did the random restart.

I took the machine covers off and cleaned the heatsink on the CPU (it was really full of dust) and voila it solved the problem.

Basically it is the machines way of protecting itself.