BSOD driver detected a controller error

[Pendejo11]

Hello everyone,

Today I was just playing some call of duty and suddenly my pc froze and I received a bsod. It was rather fast and couldn't write down the numbers displayed on screen.
After I checked my event viewer I found this:

Log Name: System
Source: Disk
Date: 12/5/2010 9:58:56 PM
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Rodje2k10
Description:
The driver detected a controller error on \Device\Harddisk2\DR2.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Disk" />
<EventID Qualifiers="49156">11</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-12-05T20:58:56.843851200Z" />
<EventRecordID>5856</EventRecordID>
<Channel>System</Channel>
<Computer>Rodje2k10</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Harddisk2\DR2</Data>
<Binary>0E01800001000000000000000B0004C003010000000000000000000000082D0000000000000000001C0E090000000000FFFFFFFF0600000058000000000000000000061208000010000000003C000000000000000000000040B84A0880FAFFFF0000000000000000601C340480FAFFFF0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

I assume the error was caused by one of my harddrives. Since the error I have not encountered any other hiccups, but would like to know what really caused this error and what to do if it returns (or possibly prevent it from re-occuring).

My system has just had an upgrade. I swapped my old WD 500Gb drive for an OCZ Vertex 2 120Gb SSD.

System Specs:
Asus Maximus II Formula
Intel Q6600 @ 3.2Ghz
Corsair 800 Mhz DDR2
OCZ vertex 2 120Gb
WD 500Gb (storage)
ATi 4850

Do any of you know what could have caused this BSOD and how can I prevent it from happening again?

Many thanks,

P.R

 

[kikireeki]

This is a generic (error) and it has nothing to do with your recent crash. System crashes are labeled with (critical) so you should check the event viewer again for that one.
You can also download BlueScreenView which can read system crash logs directly from Windows minidump files http://www.nirsoft.net/utils/blue_screen_view.html

 

[Pendejo11]

This is a generic (error) and it has nothing to do with your recent crash. System crashes are labeled with (critical) so you should check the event viewer again for that one.

Hi thanks for your response. I did check the eventviewer again and found 1 critical error:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2010-12-05T22:09:25.398408600Z" />
<EventRecordID>6693</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Rodje2k10</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">80</Data>
<Data Name="BugcheckParameter1">0xfffff900c2812000</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0xfffff9600013b409</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Any ideas?

 

[kikireeki]

Sounds like your OC is not stable, try to stress test your system using prime95.
according to my experience (Kernel-Power) crashes indicate that the CPU is not getting enough power. You can try to raise the Vcore voltage (CPU Voltage Control) a bit or reset your CPU to its default clocks.

 

[Pendejo11]

Hmm ok, I ran p95 and after 6 hours core 3 crapped out on me. So i upped the vcore a bit (from 1.25 to 1.25625) and running p95 naow again. Hopefully stable . Will let you know how it turns out.
Thanks for pointing me in the right direction!