I've been battling this one since I built this system in late October. Since then, the machine suffers a BSOD, approximately once every two days; although it has gone as long as nine days in between.
There is no obvious theme to what the machine is doing when the crash occurs. It has crashed at idle, in graphics intensive games, and while simply browsing the internet.
I've done what I feel I can, and now must seek your assistance.
The machine is running Windows 7 x64 Pro.
I began by using WhoCrashed 2.10 to analyze the minidumps after the first BSOD.
Sadly, all 22 dumps I've collected list ntoskrnl.exe as the cause, although for varying reasons; including 'CRITICAL STRUCTURE CORRUPTION' and 'KMODE EXCEPTION NOT HANDLED'.
I have run Memtest86+ to completion, with my RAM modules in their current positions.
I have NOT run Memtest86+ on the modules individually.
I have reinstalled several drivers, and I believe them all to be current.
I have attached my latest three minidumps.
The single most recent dump was created while 'verifer.exe' was active, monitoring all non-Microsoft drivers on the system; and running all tests except 'Low Resource Simulation'.
Oddly, after activating the driver verifier, it took a full nine days, and several reboots to actually suffer a BSOD; as opposed to the common two day interval.
I have never installed Alcohol 120% or Daemon Tools on the system.
It was running AVG for a time, but I replaced it with MSE a number of weeks ago.
Thank you for your time.
There is no obvious theme to what the machine is doing when the crash occurs. It has crashed at idle, in graphics intensive games, and while simply browsing the internet.
I've done what I feel I can, and now must seek your assistance.
The machine is running Windows 7 x64 Pro.
I began by using WhoCrashed 2.10 to analyze the minidumps after the first BSOD.
Sadly, all 22 dumps I've collected list ntoskrnl.exe as the cause, although for varying reasons; including 'CRITICAL STRUCTURE CORRUPTION' and 'KMODE EXCEPTION NOT HANDLED'.
I have run Memtest86+ to completion, with my RAM modules in their current positions.
I have NOT run Memtest86+ on the modules individually.
I have reinstalled several drivers, and I believe them all to be current.
I have attached my latest three minidumps.
The single most recent dump was created while 'verifer.exe' was active, monitoring all non-Microsoft drivers on the system; and running all tests except 'Low Resource Simulation'.
Oddly, after activating the driver verifier, it took a full nine days, and several reboots to actually suffer a BSOD; as opposed to the common two day interval.
I have never installed Alcohol 120% or Daemon Tools on the system.
It was running AVG for a time, but I replaced it with MSE a number of weeks ago.
Thank you for your time.
Attachments
Last edited: