Yes, that’s what bothers me, but it seems off that it performs perfectly in Safe Mode with Networking.
I’ve been wondering if it was something as simple as needing the SATA cables of memory sticks re-seating.
The machine is normally left on permanently and hence quite warm all the time, but we’ve been away for a week in Prague; with no central heating in our house, it would have got quite cold and just started to heat up again when it crashed. (It was a suffix 0x000008 stop, by the way- I never did get much more from the video, as it was on screen so briefly and I was only recording at 30 fps)
However I seem to be having a bit of success. Blue Screen Viewer pointed to one of the RAID drivers, but not the one which actually makes the RAID array visible to Windows.
I downloaded a slightly later version from Biostar’s website and forced an upgrade of them all from Safe Mode Device Manager.
System obviously then needed a re-start and with baited breath, I let it.
Seems to be a normal re-boot, albeit with a previous restore point activated, though only from just before I turned it off when we went away last week.
Only trouble is that there are now 3 Windows updates still in the queue to be installed.
I think I might wait until we have the next holiday planned, so that’s set to Notify, but not Download or Install ;D
Next one is to give the thing a good workout with MemTest and risk re-installing Avast.
Do you have any idea why it seemed to prevent Crash Memory MiniDumps?
A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers.
This is the 08 cause, so a RAM check with memtest may be in order. Although as you have updated a RAID driver (low level) that may be the culprit
As for the memory dumps I have no idea as I can force a crash on my system and they work perfectly well
The odd point about the dump is that it now quotes the latest version of the relevant driver i.e. 10.1.0.28
That’s the one I’ve just updated to; when the crashes occurred, it was running 10.1.0.15 and was then recorded as such by Blue Screen Viewer, so that might be one to watch out for.
Any thought on why I can’t disable auto re-boot on a stop error?
Now looking seriously at getting an SSD reasonably promptly and getting XP out of this RAID array when I’ve proved the rest of this hardware.
Yes, they were bought as a matched pair.All still seems quite stable at the moment, so I’ve just ordered a 250GB Samsung SSD. They seem to be the most reliable ones as far as I can tell.
A job for after the holiday I think though
The offending drive, whilst it was loaded with the RAID drivers ,is actually one of the motherboard drivers anyway, so would have been loaded regardless.
Thanls for your assistance and ideas, back to planning the holiday for a while now.
