[HELP!!] Win XP reboots sometimes *after* startup [Any Ideas?]

[tomos]

This started about a month ago (I think after the Windows updates mid-June).

Restarting after hibernate failed sometimes - mostly it did manage to restart and show all windows, but then screen would often go black, and and it would reboot. (Sometimes one drive would be checked on reboot, see below)

So I gave up on hibernate, but I'm getting the same symptoms with a full restart! I'm not even sure if it's every time (I tend to do something else when starting from scratch, so may have missed it sometimes).

I did get one or two blue screens, I copied the message (below) and googled it with no results. Unfortunately my Dr.Watson (is that what it's called) doesnt work -due to a windows update- a MS-known problem to which there is no solution offered. That means I cannot use e.g. NirSoft's BlueScreenView to check out what the problem might be.)

0x0000008e (0xc0000005, 0x00000000, 0xb3816850, 0x00000000)

.
Often (but not always) on reboot it checks partition X -which is where temp folders are, and also where the page file is (on second drive). But I dont get any messages - i.e. it seems to be okay. Drives (two of them) sound okay but I havent checked anything.

Around about that time, I installed the following

Spoiler (click to show/hide)

==================================================
Entry Name          : GPSoftware Directory Opus
Installation Date   : 2011-06-17 12:03:18
Product Name        : Directory Opus
Uninstall String    : "C:\Program Files\InstallShield Installation Information\{556DF27F-5B74-11D5-B876-004005E12EF1}\setup.exe" -runfromtemp -l0x0407  -DentalFloss -removeonly
Company             : GPSoftware
Version             : 10.0.1.0
Description         : InstallScript Setup Launcher
Obsolete            : No
Installation Folder : C:\Program Files\InstallShield Installation Information\{556DF27F-5B74-11D5-B876-004005E12EF1}
Uninstall           : Yes
Web Site            : www.gpsoft.com.au
Installation Change String: "C:\Program Files\InstallShield Installation Information\{556DF27F-5B74-11D5-B876-004005E12EF1}\setup.exe" -runfromtemp -l0x0407  -DentalFloss
Quiet Uninstall     : No
Registry Key        : {556DF27F-5B74-11D5-B876-004005E12EF1}
Installer           : Unknown
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Adobe Reader 8.3.0
Installation Date   : 2011-06-17 09:30:56
Product Name        :
Uninstall String    : MsiExec.exe /X{AC76BA86-7AD7-1033-7B44-A83000000003}
Company             : Adobe Systems Incorporated
Version             : 8.3.0
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            : http://www.adobe.com
Installation Change String: MsiExec.exe /I{AC76BA86-7AD7-1033-7B44-A83000000003}
Quiet Uninstall     : No
Registry Key        : {AC76BA86-7AD7-1033-7B44-A83000000003}
Installer           : Windows Installer
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Microsoft .NET Framework 2.0 Service Pack 2
Installation Date   : 2011-06-16 10:34:22
Product Name        :
Uninstall String    : MsiExec.exe /X{C09FB3CD-3D0C-3F2D-899A-6A1D67F2073F}
Company             : Microsoft Corporation
Version             : 2.2.30729
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            : http://go.microsoft.com/fwlink/?LinkId=98073
Installation Change String: MsiExec.exe /I{C09FB3CD-3D0C-3F2D-899A-6A1D67F2073F}
Quiet Uninstall     : No
Registry Key        : {C09FB3CD-3D0C-3F2D-899A-6A1D67F2073F}
Installer           : Windows Installer
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161
Installation Date   : 2011-06-16 10:29:52
Product Name        :
Uninstall String    : MsiExec.exe /X{9BE518E6-ECC6-35A9-88E4-87755C07200F}
Company             : Microsoft Corporation
Version             : 9.0.30729.6161
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            :
Installation Change String: MsiExec.exe /X{9BE518E6-ECC6-35A9-88E4-87755C07200F}
Quiet Uninstall     : No
Registry Key        : {9BE518E6-ECC6-35A9-88E4-87755C07200F}
Installer           : Windows Installer
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Security Update for Windows XP (KB2476490)
Installation Date   : 2011-06-16 10:29:46
Product Name        :
Uninstall String    : "C:\WINDOWS\$NtUninstallKB2476490$\spuninst\spuninst.exe"
Company             : Microsoft Corporation
Version             : 1
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            : http://support.microsoft.com
Installation Change String:
Quiet Uninstall     : No
Registry Key        : KB2476490
Installer           : Unknown
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Security Update for Windows XP (KB2503665)
Installation Date   : 2011-06-16 10:29:41
Product Name        :
Uninstall String    : "C:\WINDOWS\$NtUninstallKB2503665$\spuninst\spuninst.exe"
Company             : Microsoft Corporation
Version             : 1
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            : http://support.microsoft.com
Installation Change String:
Quiet Uninstall     : No
Registry Key        : KB2503665
Installer           : Unknown
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Security Update for Windows XP (KB2535512)
Installation Date   : 2011-06-16 10:29:36
Product Name        :
Uninstall String    : "C:\WINDOWS\$NtUninstallKB2535512$\spuninst\spuninst.exe"
Company             : Microsoft Corporation
Version             : 1
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            : http://support.microsoft.com
Installation Change String:
Quiet Uninstall     : No
Registry Key        : KB2535512
Installer           : Unknown
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Security Update for Windows XP (KB2536276)
Installation Date   : 2011-06-16 10:29:31
Product Name        :
Uninstall String    : "C:\WINDOWS\$NtUninstallKB2536276$\spuninst\spuninst.exe"
Company             : Microsoft Corporation
Version             : 1
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            : http://support.microsoft.com
Installation Change String:
Quiet Uninstall     : No
Registry Key        : KB2536276
Installer           : Unknown
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Security Update for Windows Internet Explorer 8 (KB2530548)
Installation Date   : 2011-06-16 10:29:26
Product Name        :
Uninstall String    : "C:\WINDOWS\ie8updates\KB2530548-IE8\spuninst\spuninst.exe"
Company             : Microsoft Corporation
Version             : 1
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            : http://support.microsoft.com
Installation Change String:
Quiet Uninstall     : No
Registry Key        : KB2530548-IE8
Installer           : Unknown
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Security Update for Windows XP (KB2544893)
Installation Date   : 2011-06-16 10:27:41
Product Name        :
Uninstall String    : "C:\WINDOWS\$NtUninstallKB2544893$\spuninst\spuninst.exe"
Company             : Microsoft Corporation
Version             : 1
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            : http://support.microsoft.com
Installation Change String:
Quiet Uninstall     : No
Registry Key        : KB2544893
Installer           : Unknown
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Microsoft Visual C++ 2005 Redistributable
Installation Date   : 2011-06-16 10:27:37
Product Name        :
Uninstall String    : MsiExec.exe /X{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
Company             : Microsoft Corporation
Version             : 8.0.61001
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            :
Installation Change String: MsiExec.exe /X{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
Quiet Uninstall     : No
Registry Key        : {710f4c1c-cc18-4c49-8cbf-51240c89a1a2}
Installer           : Windows Installer
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : Security Update for Windows Internet Explorer 8 (KB2544521)
Installation Date   : 2011-06-16 10:25:41
Product Name        :
Uninstall String    : "C:\WINDOWS\ie8updates\KB2544521-IE8\spuninst\spuninst.exe"
Company             : Microsoft Corporation
Version             : 1
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            : http://support.microsoft.com
Installation Change String:
Quiet Uninstall     : No
Registry Key        : KB2544521-IE8
Installer           : Unknown
Root Key            : HKEY_LOCAL_MACHINE
==================================================

==================================================
Entry Name          : pdfforge Toolbar v4.4
Installation Date   : 2011-06-14 21:40:32
Product Name        :
Uninstall String    : MsiExec.exe /X{BCB52F35-4C56-49F2-A3D6-FDED54B01847}
Company             : Spigot, Inc.
Version             : 4.4
Description         :
Obsolete            : No
Installation Folder :
Uninstall           : Yes
Web Site            :
Installation Change String: MsiExec.exe /X{BCB52F35-4C56-49F2-A3D6-FDED54B01847}
Quiet Uninstall     : No
Registry Key        : {BCB52F35-4C56-49F2-A3D6-FDED54B01847}
Installer           : Windows Installer
Root Key            : HKEY_LOCAL_MACHINE
==================================================

I really wish I had taken better notes so I could narrow it down more, but I didnt

Since then I upgraded the driver on my video card (nvidea) but that hasnt made any difference.
I thought I'd restore an image from before all this and try installing things one by one and see how I get on (or maybe that mighn't even fix the problem - if it's hardware...)

Any tips !?


Edir 2011-07-14 / added [HELP!!] to the title

[4wd]

If it helps, I have all the above installed except for the following on my XP Pro netbook and the Hibernate works fine:

pdfforge Toolbar v4.4
Adobe Reader 8.3.0

The XP Pro system on the netbook has been nlited a bit to remove things I don't use/need.

[40hz]

Had same error code myself.

Long shot: Are you running an AMD or an Intel CPU?

If AMD and your mobo is using nForce drivers, try temporarily disabling the onboard nForce NIC(s) and see if the problem goes away. I had that happen on an AMD box I had after I installed a 1Gb NIC card and stopped using the built-in. I took me forever to figure out since the problem surfaced about three months afterwards following an WSUS update so I didn't equate hardware with the problem.

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

Anyway...

Here's the "official" description of an 8E error:

STOP 0x0000008E errors are usually caused by memory hardware failures and more rarely by device driver issues, viruses, or hardware failures other than your RAM.

Here's the rest of it:

It's pretty long!

Problem Event Name: BlueScreen
BCCode: 8e
Cause of STOP 0x0000008E Errors

STOP 0x0000008E errors are usually caused by memory hardware failures and more rarely by device driver issues, viruses, or hardware failures other than your RAM.

If STOP 0x0000008E isn't the exact STOP code you're seeing or KERNEL_MODE_EXCEPTION_NOT_HANDLED isn't the exact message, please check my Complete List of STOP Error Codes and reference the troubleshooting information for the STOP message that you are seeing.
Resolution

   Restart your computer if you haven't already done so. The STOP 0x0000008E blue screen error might be a fluke.

   Did you just install new hardware or make a change to some hardware or a hardware driver? If so, there's a very good chance that the change you made caused the STOP 0x0000008E error.

   Undo the change you made and test for the 0x8E blue screen error.

   Depending on what change you made, some solutions might include:
       Remove or reconfigure the newly installed hardware.
       Startup with Last Known Good Configuration to undo related registry and driver changes.
       Use System Restore to undo recent changes.
       Roll back any device drivers you've installed to versions prior to your update.
   Test your RAM. The most common cause of the STOP 0x0000008E error is memory that is damaged or has stopped working properly for some reason.

   Replace any nonworking memory modules if your tests show a problem.

   Verify that the system memory is properly installed. Memory that's installed in some way other than that suggested by your motherboard manufacturer could cause STOP 0x0000008E errors and other related problems.

   Note: If you have any doubt about the proper memory configuration in your computer, please consult your computer or motherboard manual. All motherboards have fairly stringent requirements on the types and configurations of RAM modules.

   Return BIOS settings to their default levels. Overclocked or misconfigured memory settings in BIOS have been known to cause STOP 0x0000008E errors.

   Note: If you've made several customizations to your BIOS settings and don't want to load the default ones then at least try returning all BIOS memory timing, caching, and shadowing options to their default levels and see if that fixes the STOP 0x0000008E error.

   Apply all available Windows updates. Several service packs and other patches have specifically addressed STOP 0x0000008E issues.

   Note: This particular solution is likely to solve your problem if your STOP 0x0000008E error is accompanied by a mention of win32k.sys or wdmaud.sys, or if it occurred while making changes to the hardware acceleration on your graphics card.

   If STOP error 0x0000008E is followed by 0xc0000005, as in STOP: 0x0000008E (0xc0000005, x, x, x), applying the latest Windows service pack will likely fix your issue.

   Perform basic STOP error troubleshooting. If none of the specific steps above help fix the STOP 0x0000008E error you're seeing, take a look at this general STOP error troubleshooting guide. Since most STOP errors are similarly caused, some of the suggestions might help.

Please let me know if you've fixed a blue screen of death with the STOP 0x0000008E STOP code using a method that I don't have above. I'd like to keep this page updated with the most accurate STOP 0x0000008E error troubleshooting information as possible.
Applies To

Any of Microsoft's Windows NT based operating systems could experience the STOP 0x0000008E error. This includes Windows 7, Windows Vista, Windows XP, Windows 2000, and Windows NT.
Still Having STOP 0x0000008E Issues?

Let a community of computer support enthusiasts help out! Post the details of your STOP error in the PC Support Forums. Be sure to let us know the that you're seeing the 0x0000008E STOP code and also what steps, if any, you've already taken to resolve it.

Also, please make sure you've looked at my general STOP Error Troubleshooting Guide before posting.

Buried in there was one thing in it I didn't know. This note:

If STOP error 0x0000008E is followed by 0xc0000005, as in STOP: 0x0000008E (0xc0000005, x, x, x), applying the latest Windows service pack will likely fix your issue.

Might be worth a try.

Note: if you let Windows update any hardware drivers thru WSUS - roll them back. The generic ones Microsoft issues don't work very well with a lot of hardware. I always use the drivers supplied by the PC manufacturer if at all possible. Especially if they're non-Intel chipset video drivers.

Luck!

[4wd]

Buried in there was one thing in it I didn't know. This note:

...

The top bit is interesting too:

STOP 0x0000008E errors are usually caused by memory hardware failures and more rarely by device driver issues, viruses, or hardware failures other than your RAM.

You could try reseating the RAM or running memtest from a bootable flash drive.

[Cloq]

What model/brand motherboard?

Do you know if you have sata set to ahci mode? If so, download and install intel storage matrix drivers, assuming mobo is intel chipset and sata ports that is.

I know several (various big name brand) laptop and desktop models that spontaneously rebooted randomly till the intel drivers were installed.

[tomos]

oups - forgot the hardware info - it was from a site where you can choose the different parts and they build it

CPU: Intel core 2 duo e4400 tray 2048kb, lga775, 64bit 100,60 € Mobo: Msi p35 neo-f, intel p35, atx 90,75 € CPU fan: Arctic freezer 7 pro sockel 775 14,17 € Memory: 2048Mb-kit ddr2 mdt , pc6400/800, cl5 70,91 € Box: Coolermaster centurion5 schw. Cac-t05-uw no PSU 44,49 € PSU: Atx-netzteil corsair vx450w 450 watt 65,00 € Graphic card: ASUS GF-7100GS Silent, 128MB, Nvidia 7100GS, PCIe 36,50 € Harddrives: Samsung hd321kj 320gb serial ata-ii, 7200 upm, 16mb 60,40 € Samsung hd321kj 320gb serial ata-ii, 7200 upm, 16mb 60,40 € DVD burner: Samsung sh-s183l bare schwarz 35,38 € Floppy Laufwerk 1.44 Mb,3.5" Schwarz 4,99 € Sound: Terratec aureon 5.1 Pci 16,40 € Modem: Devolo microl. 56K pci (bulk) pci 11,55 €

[tomos]

What model/brand motherboard?

Mobo: Msi p35 neo-f, intel p35, atx

Do you know if you have sata set to ahci mode?

I have no idea (!) any tips how I might check?

[4wd]

Do you know if you have sata set to ahci mode?

I have no idea (!) any tips how I might check?

According to the specs on MSIs site, (MSI P35 Neo*), it doesn't have AHCI, (it's only the ICH9 chipset not the ICH9R which includes RAID/AHCI).

Otherwise, if you go into the BIOS and look under Integrated Peripherals->SATA Mode, (IIRC), it will give you the option of IDE, RAID, AHCI - if any of or all those modes are available.

* I know it doesn't say specifically P35 Neo-F but from what I've read on the forums, they are one and the same.  Compare this to the P35 Neo2-FR which does list AHCI function.

[tomos]

^ thanks 4WD for that info!

well, I bought a can of compressed air and just used up the most of it on the inside of the machine - I made the mistake of starting at the bottom, and had to redo a lot of it... It actually wasnt as bad as I thought it might be, but the intake fan was really bad. It restarted fine, but fan sound is very uneven now, and louder than before or louder at the back of the machine at any rate. Maybe I should start it with the case open see if the fans working okay.

Also going to install Speedfan for a look.

If the problem recurs, I'll have a look at the memory.
Will let ye know how it gets on....

[cranioscopical]

well, I bought a can of compressed air and just used up the most of it on the inside of the machine

I have to chip in with this, expecting that you're fully aware of it, but…

BE CAREFUL with that stuff! You can do a lot of damage inadvertently.
Don't let that 'freezing' propellant get near to anything.
Also, lock the blades of the fans somehow before blasting them, you don't want to rev them faster than they're designed to go.
If you don't already, turn off all power to the machine and let the entire thing stand for a while.

You'd be better off using straws and soft-bristle, artist-style paint brushes.

[tomos]

BE CAREFUL with that stuff! You can do a lot of damage inadvertently.
Don't let that 'freezing' propellant get near to anything.
Also, lock the blades of the fans somehow before blasting them, you don't want to rev them faster than they're designed to go.
If you don't already, turn off all power to the machine and let the entire thing stand for a while.

oups! (There's lots I dont have a clue about so thanks for the advice...)
I did keep it a good distance from everything at least.
Also I had plugged everything out and earthed myself first on the heater.

You'd be better off using straws and soft-bristle, artist-style paint brushes.

do I have to suck up the dust through the straw
... or what ?!!

[Stoic Joker]

Also, lock the blades of the fans somehow before blasting them, you don't want to rev them faster than they're designed to go.

While it is true that ballbearings can explode if they are overspeed with compressed air, fans aren't really that dangerous. You really stand a better chance of breaking it trying to hold it still, than if you just let it spin. Just use a bit of common sense when the speed hits a high whistle and back off ... It'll be fine.

You'd be better off using straws and soft-bristle, artist-style paint brushes.

Never use a brush with electronics. The bristles are static generators to the Nth power.

[cranioscopical]

@StoicJoker

You would know better than I, and I bow to your expertise.
Thanks for putting me right!

That said, I still feel uncomfortable about using compressed air.


@Tomos

See — what do I know? 

[Stoic Joker]

That said, I still feel uncomfortable about using compressed air.

Understood. I've heard some horror stories about it to, but they usually involve missing parts after someone used the (undried/cleaned) shop line pressure of 140psi. The air can's low pressure tiny plastic tube is substantially more "forgiving"...

Years ago I worked soldering/stuffing board for a local manufacturer. It amazed me to no end that the completed boards were run through what amounted to a small car-wash. The liquid (mostly water) didn't hurt the board in the slightest. It's only an issue if the board is wet and energized at the same time (It's a potential problem...).

Years later I had to completely disassemble a server, and scrub it down with baking soda, water, and a tooth brush. to get the surprisingly corrosive insecticide out of it after the bug guy sprayed it to death.

Sun dried and reassembled it booted and ran just fine for another 3 years.

[cranioscopical]

Years later I had to completely disassemble a server, and scrub it down with baking soda, water, and a tooth brush. to get the surprisingly corrosive insecticide out of it after the bug guy sprayed it to death.

I've heard of debugging but that's a bit over the top!

[4wd]

Years ago I worked soldering/stuffing board for a local manufacturer. It amazed me to no end that the completed boards were run through what amounted to a small car-wash. The liquid (mostly water) didn't hurt the board in the slightest. It's only an issue if the board is wet and energized at the same time (It's a potential problem...).

Years later I had to completely disassemble a server, and scrub it down with baking soda, water, and a tooth brush. to get the surprisingly corrosive insecticide out of it after the bug guy sprayed it to death.

Sun dried and reassembled it booted and ran just fine for another 3 years.

I've also put small circuit boards through a cycle in the dishwasher with no ill effects, I don't recommend doing this for all boards - some board components aren't sealed against liquid - but it worked OK after being dried off.

WRT, the compressed air, (not trying to pick a fight SJ, just a different perspective ), I still use a vacuum cleaner mainly because I prefer to pull dust away from pins rather than push dust toward them.  Side benefit: it's cheaper  

But I suspect it's more a case of six of one, half-dozen of the other.

With the fan argument, I consider it's more the point of turning the fan into a wind generator than causing it damage - putting a fingertip just inside the fan frame will stop them turning without having to exert pressure on the hub/blades themselves.  If you don't want to do that, unplug the fan from the motherboard before blasting it with an airflow, (either compressed or vacuum).

EDIT: And now what I really meant to say

My netbook has just started doing the same thing, ie. reboot after hibernate or at machine start.

However, it's only when the 3G dongle is plugged in - so it seems to be a driver/software conflict in my case.

[Stoic Joker]

WRT, the compressed air, (not trying to pick a fight SJ, just a different perspective ), I still use a vacuum cleaner mainly because I prefer to pull dust away from pins rather than push dust toward them.  Side benefit: it's cheaper

A vacuum cleaner can be a viable option if you're really carefull, and don't use a brush attachment. All of our printer techs have/carry/use mini-vacs for printer service/cleaning (much electronics in them these days...). As you said it's cheaper, and you don't get toner blown all over the client's office (tends to make them cranky).

At home I use my air compressor quite frequently (cheaper...), but I know how to keep the pressure down to a safe level from years of being a mechanic.

[nudone]

(I don't think this has been mentioned yet.)

I tried compressed air, vacuum and brushes (and I think a brush did once kill something inside the machine via static).

Having read about why all of the above are bad in some way I tried to find something similar to compressed air but without the cost.

I now use a mini leaf-blower (or whatever you want to call it). It's like a large hair dryer, nowhere near the size of a proper leaf-blower, but is a lot more powerful than a hair dryer and maybe more powerful than a small compressed air can.

Of course, it blows dust everywhere - so I just take the filthy machines outside and don't have to worry about the dirt blasting out and landing on something in the house.

Can't remember the price but it was only like £10.00 on ebay or something.

p.s. you don't get any moisture condensing with it either.

[tomos]

^ Well, I had the compressed air can in one hand and the hoover in the other to try and catch some of the dust clouds.
@ 11 euro a can (CCM "Spray Duster") I can see why you'd be looking for alternatives

[tomos]

Back on-topic:

After my computer spring-clean, I had one clean start, then one faulty (reboot shortly after desktop showed).
But this morning I couldnt boot properly at all - it just kept rebooting.

I tried reseating the memory - no difference.

Then I dug out the acronis boot disc -
First I tried to do an image of C partition - I got the message "MFT Bitmap corrupted on one of the partitions".  I presume they meant the source partition (C) but not fully clear from message. (I have yet to google that.)

So did a restore from before problems began and had a successfull booting experience - phew...

[worstje]

I take it you've vetted your hard drives, checked their S.M.A.R.T. status and have done a surface scan. Likewise, I hope/assume you have looked into giving your memory at least one full cycle of MemTest86(+) tests.

Sysinternals (or was it Winternals?) also has a NotMyFault utility. I can't find it on their website but it is somewhere in their download area. It is a tool to help test the stability of your drivers rather than your memory, so try all the options on it one by one. If it makes your PC crash you know drivers are likely the cause and that you ought to try updating those. Ignore NotMyFault. That one always crashes your PC as it is the entire purpose. I blame sleep for my own misunderstanding.

Also, test the voltages your power supply gives off, especially when being stressed. (Prime95 and some benchmarking tools are nice for that.) A flakey power supply is also a good culprit for instability issues like yours.

[tomos]

I take it you've vetted your hard drives, checked their S.M.A.R.T. status and have done a surface scan. Likewise, I hope/assume you have looked into giving your memory at least one full cycle of MemTest86(+) tests.
...
Also, test the voltages your power supply gives off, especially when being stressed. (Prime95 and some benchmarking tools are nice for that.) A flakey power supply is also a good culprit for instability issues like yours.

worstje - you're talking to a noob here - especially when it comes to hardware stuff i.e. I havent a clue how to do anything you list - apart from the mem test, probably.
I have described above what I have done and it unfortunately doesnt include anything on your list. Memtest was the only one already suggested (I think).

Now my problem is, after a seeming okay start this morning (my last post), it crashed again shortly later - without warning, and rebooted. I just switched the power off at that stage. So, it looks like I cant run windows on it.

If you, or anyone else, could give me a tip or two about how to proceed - maybe what to begin with, dont have to spell absolutely everything out, but roughly how & what.
Many thanks in advance


[edit] memtest86+ is running (couldnt get it to work from usb so took a while to get going) [/edit]

[tomos]

to summarise:

over the last month, windows often rebooted 'spontaneously' after having just started (usually shortly after the desktop & icons showed - also after start from hibernate). Usually it would then run okay.
Always during the reboot, it checked Partition X which is where the Temp folder is, also where the Page file is (I presume there is some significance to this but guess almost anything could be using the Temp folders...) Partition X is on a second drive. C/windows is on first drive.

Yesterday it escalated - now it either continuously reboots or reboots randomly/unexpectedly - with no errors bluescreen or warnings.

What I've done:

• I tried to create an image (acronis TI) but got message about "MFT Bitmap corrupted on one of the partitions"
• I did a system restore [image restore] to before the problem - restarted okay but crashed again shortly after. Then went into rebooting cycle so I turned off the power. I presume this rules out any of the software updates being the cause).
• Currently running memtest86+ from a CD - first pass is error free [second pass also error free]

edit/ HARDWARE is listed in post #5 above

[Stoic Joker]

If memtest86+ got that far without the screen turning red...chances are the memory is fine.

Run this next: Samsung HDD Tool

If the manufacturer's diag give the drives a green light, it's probably the power supply.

[tomos]

If memtest86+ got that far without the screen turning red...chances are the memory is fine.

Run this next: Samsung HDD Tool

If the manufacturer's diag give the drives a green light, it's probably the power supply.

Thanks SJ
I downloaded UBCD for windows earlier and see that that Samsung tool is on it.
I was thinking at this stage, to leave it till tomorrow and get an external drive and copy everything over before I test it. I have all the really important stuff backed up online, otherwise backups are from one HD to the other - and seeing they both bought at same time, they could even both be dodgy