Different BSODs playing mostly every game. Latest: 0x0000001e

Thanks for the file, I'm just downloading it now, it may take some time (slow Internet connection )

If you have any problems or questions with any of the steps within the troubleshooting guide, then just ask me or Arc.

Appreciating all the effort!
As to the troubleshooting guide, I've already ran the GPU and CPU stresstests, aswell as the memcheck. GPU and memory seems fine. The CPU stresstest is the one causing instant trouble. The last time, it seemed promising for 15 seconds, then Microsoft Security Essentials crashed, and right after stresstest crashed. No BSOD this time though.

I did the SFC.exe /scannow fix prior to the stresstest aswell, no solution there.

Tomorrow I will check the drivers as described in the guide, and if that doesn't work either, I'll pop an old CPU in the system and run more tests with that.

Really hoping you'll find something in that dump file though! I've spent months trying to fix this rig now.

Code:

BugCheck 101, {19, 0, fffff88003365180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Code:

Usual causes:  Device driver, BIOS bug, hardware defect

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05ad0000 fffff880`06578000   nvlddmkm   (export symbols)       nvlddmkm.sys
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Feb 09 23:13:08 2013 (5116D804)
    CheckSum:         00A90CB0
    ImageSize:        00AA8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This driver version seems to be a possible cause too, I would suggest trying a different driver version.

Code:

0: kd> lmvm iaStor
start             end                 module name
fffff880`01013000 fffff880`013b7000   iaStor     (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Thu Feb 02 00:15:24 2012 (4F29D59C)
    CheckSum:         0008B2F8
    ImageSize:        003A4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Intel Rapid Storage driver seems to be a possible cause, it seems to always cause problems, I would recommend removing the driver completely from your system, and then rebooting to allow Windows to use it's own msahci.sys driver.

Code:

0: kd> lmvm e1c62x64
start             end                 module name
fffff880`06578000 fffff880`065f4000   e1c62x64   (no symbols)           
    Loaded symbol image file: e1c62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
    Image name: e1c62x64.sys
    Timestamp:        Thu Feb 21 05:14:02 2013 (5125AD1A)
    CheckSum:         0008277C
    ImageSize:        0007C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Intel(R) 82579V Gigabit Network Connection driver seems to be a possible cause, are you running any Internet security programs, these can often cause the network drivers to be blamed.

Code:

0: kd> lmvm intelppm
start             end                 module name
fffff880`04cef000 fffff880`04d05000   intelppm   (no symbols)           
    Loaded symbol image file: intelppm.sys
    Image path: \SystemRoot\system32\DRIVERS\intelppm.sys
    Image name: intelppm.sys
    Timestamp:        Tue Jul 14 00:19:25 2009 (4A5BC0FD)
    CheckSum:         0000F4EC
    ImageSize:        00016000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Intel chipset driver seems to be a possible cause, check for any updates from here - https://downloadcenter.intel.com/Default.aspx

x BlueRobot said:

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05ad0000 fffff880`06578000   nvlddmkm   (export symbols)       nvlddmkm.sys
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Feb 09 23:13:08 2013 (5116D804)
    CheckSum:         00A90CB0
    ImageSize:        00AA8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This driver version seems to be a possible cause too, I would suggest trying a different driver version.

This is an Nvidia driver? Because I just rolled back to a previous version of the drivers, and now I'm left wondering, are there any Nvidia drivers that actually work...? Guess I'll roll it back further.

Your Intel Rapid Storage driver seems to be a possible cause, it seems to always cause problems, I would recommend removing the driver completely from your system, and then rebooting to allow Windows to use it's own msahci.sys driver.

Is it sufficient to just remove the file itself manually? I couldn't find any advice on how to remove it.

Your Intel(R) 82579V Gigabit Network Connection driver seems to be a possible cause, are you running any Internet security programs, these can often cause the network drivers to be blamed.

I'm using Microsoft Security Essentials, as recommended here.

Your Intel chipset driver seems to be a possible cause, check for any updates from here - https://downloadcenter.intel.com/Default.aspx

Okey, found the drivers, goind to install them now.

For the Intel Rapid Storage driver, go to Device Manager, and then expand Disk Devices, you should see the driver listed, simply then remove the driver and reboot the computer.

The CPU is still questionable here.

Okey, so I stopped the driver and rebooted. Had no option to remove it that I could see.

After updating the chipset, I haven't had any more BSOD. I've run my Men of War and Arma 2 for hours, and they usually either crashed or CTD'd after a few minutes prior. Arma 2 still crashes after some time, but at least it doesn't bring the computer down with it anymore.

The CPU is indeed still at question. The stresstest can run for maybe 45 seconds now, before the program crashes. No more instant bluescreens there either at least.

Okey, I forced another BSOD with the stresstest now. It ran for maybe a minute. Before it died the program reported an error in one of the workers, but that was all I could read before it crashed. CPU temp was then at just above 90 degrees.
From the results file:

Code:

[Fri Jun 21 17:14:17 2013]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

I'll try running it a few more times.

Edit:
Ran the stresstest one more time. Ran a bit longer, got a different BSOD, but got the same result first; error in worker 3.
Attached the freshest minidump.

Thanks, I'll have a look now.

Code:

BugCheck 3B, {c000001d, fffff800030bbf7d, fffff8800a183df0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpReleaseResourceForThreadLite+d )

Code:

2: kd> !error c000001d
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

Did you run the Small FFTs test? It seems your CPU is faulty.

Yes, that was the small FFTs test.