BSODs persist after clean install

I deleted all partitions on the HDD. I installed the latest drivers for the ASRock Mboard. I have installed little else. The info regarding crashes prior to new installation are uploaded herewith. And ditto with the latest crash. Also a speccy report. I would be grateful for some help.

I have been trying to migrate to linux on this box due to the grief of instability, but I couldn't make dual boot work at all and weird stuff affected startup. Even now, after refreshing the HD the machine stops on boot to display: 'remove disks or othe' (yes, really: 'othe') even though there is no DVD etc in the optical drive.

Help!

The one single dump in your log is a 0xC5 which indicates a driver is corrupting the system pool, there's no driver listed in the dump at all however.

Code:

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002dc9b15, address which referenced memory

Diagnostic Test

 DRIVER VERIFIER

Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable

Enable Driver Verifier but only enable these options:

• Standard settings and IRP logging step 3.
• Don't enable Force Pending I/O Requests

   Warning

Make a System Restore point before enabling Driver Verifier.

   Note

Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Post any resulting dump files.

You also need to run all rounds of Windows Updates, your missing a lot of Hotfixes.

Speccy text removed for your protection - as it contained your complete COA details

The DV dump has shown a driver, your Intel USB 3.0 eXtensible Host Controller driver. It's pretty old and needs updating, check here for an updated version. I did check the Gigabyte support page for your motherboard but it lists an Etron USB 3.0 driver and no Intel driver, could you post a screenshot of Device Manager with USB Controllers expanded please.

Code:

BugCheck E6, {f, 3, fffff88003d0e000, 0}

*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
Probably caused by : iusb3xhc.sys ( iusb3xhc+37c43 )

Followup: MachineOwner
---------

0: kd> lmvm iusb3xhc
start             end                 module name
fffff880`058a2000 fffff880`05967000   iusb3xhc T (no symbols)           
    Loaded symbol image file: iusb3xhc.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Mon May 21 08:21:40 2012 (4FB9ED04)
    CheckSum:         000CA061
    ImageSize:        000C5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You've updated the driver?