Hello again VTV, sorry to hear you're still getting BSODs after so long.
I found this entry:
Code:
Event[1918]:
Log Name: System
Source: Disk
Date: 2011-10-12T03:25:44.162
Event ID: 7
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: i-d-ten-t
Description:
The device, \Device\Harddisk0\DR0, has a bad block.
---
Event[4230]:
Log Name: System
Source: Ntfs
Date: 2011-10-04T23:15:09.243
Event ID: 130
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: i-d-ten-t
Description:
The file system structure on volume C: has now been repaired.
It may or may not be relevant to your problem, but we should definitely pursue that. Start by running SeaTools:
SeaTools for Windows | Seagate
If it fails, replace the drive - no questions asked. SeaTools failures don't leave much room for beating around the bush, because they rarely go wrong.
If it passes, open a command prompt and run:
It will ask you to schedule the run for next reboot. When you do, report the results here.
Next:
Code:
Event[1828]:
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 2011-10-12T19:05:26.009
Event ID: 219
Task: N/A
Level: Warning
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: i-d-ten-t
Description:
The driver \Driver\kbdhid failed to load for the device HID\VID_045E&PID_00DB&MI_00\7&13e48b85&0&0000.
Keyboard/mouse
drivers tend to be pretty stable, so we may be looking at a physical keyboard problem here. If you have another keyboard, give it a try by all means. If not, try uninstalling the keyboard drivers in Device Manager and uninstalling any keyboard control programs you may have installed.
Other than that, I can only suspect a RAM/motherboard problem. Run each of the three Prime95 tests:
Hardware - Stress Test With Prime95
Good luck with those, post if you need any help! If nothing helps, post back and we'll go from there.