After 20 crashes in 5 days - and 4 more today - I think there might be something wrong<BG>

Prior to restoring to my oldest restore point today - unfortunately, in the middle of the crash season,- I:-
(1) Checked Device Manager for problems and rolled back recently installed drivers, except that for the Radeon 8500 video adapter.
(2) Ran chkdsk and the manufacturer's diagnostic programme.
(3) Ran Memtest (extended), in addition to several short runs.
(4) Ran HD Tach
(5) Ran sfc /scannow
(6) Did 2 virus sweeps and an Ad Aware sweep.
(7) Defragged.
No problems were found.

The minidumps initial BUCKET_ID diagnoses were:-
Hardware (7)
Win32k.sys (4)
VETEFILE. SYS (4)
Others(no duplication) (5)

Taking only the 7 initial hardware BUCKET_ID's, !analyze -v broke them down into:-
CPU_CALL_ERROR (4)
IP_MISALIGNED (3)

BUGCHECK_STRING anlysis:-
0x8e (5)
0xD1 (1)
0x24 (1)

The EXCEPTION CODES were all different, apart from access violation
0xC0000005.

Today's quota comprise win32k.sys; VETEFILE.SYS; MEMORY_CORRUPTION and hardware.

Frankly, even with a whole day's experience in examining these beasts<g>, I'm lost. With the strong possibility of a terminal crash in the offing, there isn't time to Google every error, before Old Bessie dies, so would some expert please take a look at the minidumps attached and advise me. Thanks.

Attached Files

	Mini112606-01.zip (23.6 KB, 6 views)
	Mini112706-02.zip (22.1 KB, 2 views)
	Mini112706-04.zip (22.0 KB, 2 views)
	Mini112806-03.zip (25.8 KB, 2 views)
	Mini112906-01.zip (21.6 KB, 2 views)

Hi,

Three minidumps are crashed with CPU_CALL_ERROR. Probably the culprit is either m/b or video card. Post your problem at hardware forum and ask for the diagnostic technique to trouble shoot m/b and video card.

Many thanks. Will do.