System_Service_Exception

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:

Code:

chkdsk /r

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.

Memtest86 is a great tool and we use it frequently in BSOD analysis, but its results should not be taken as Bible. It does tend to pass faulty RAM a lot, so it can't be relied upon too heavily. Prime95 is another tool, that, while not perfect, should also be run on systems experiencing possible hardware trouble.

Interesting to see hard disk controller errors reported on a fresh installation with a new hard drive.

Code:

Event[338]:
  Log Name: System
  Source: Disk
  Date: 2011-12-16T23:14:04.250
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Neil-PC
  Description: 
The device, \Device\Harddisk1\DR2, has a bad block.

Let's file that away for the time being.

Run each of the three Prime95 tests: Hardware - Stress Test With Prime95

Also, flash the latest BIOS for your motherboard: ECS Web Site

...Summary of the dumps:

Code:

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec 17 18:33:33.594 2011 (UTC - 5:00)
System Uptime: 0 days 8:12:00.000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BiosReleaseDate = 05/20/2009
SystemProductName = P45T-A
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``