System_Service_Exception

[VTV]

I have plenty of hard drive space and everything is enabled correctly. It is still not creating these files.

 

[VTV]

Ok, FINALLY got it.

I started getting three to four crashes in a row, and it was different this time. Previously when I was getting the BSOD's it would say it was starting the file, but it would be locked up right away. This time it was actually going through the countdown of percentage of the .dmp file that was done. Please tell me if this is the file you need. This problem is getting worse and I pay bills with money I make from my computer.

 

[Jonathan_King]

Hello again VTV, sorry to hear you're still getting BSODs after so long.

I found this entry:

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:

chkdsk /r

It will ask you to schedule the run for next reboot. When you do, report the results here.

Next:

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: www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Good luck with those, post if you need any help! If nothing helps, post back and we'll go from there.

 

[VTV]

Thanks so much for your help! Going to have one of my techie friends look into this so I don't mess it up.

This problem has been going on since I built this computer, but it has become more steadily severe. He did run Memtest on all of the RAM. So that should not be it.

 

[Jonathan_King]

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.

 

[VTV]

More BSODs.

Ok, so I am pretty much on board with needing to replace my hard drive. Got some fresh BSODs and wanted you to look at them to be sure. They are attached.

 

[VTV]

Problem is getting worse.

OK, so I got a new hard drive, as the testing program you reccomended failed my old one. I thought I was doing fine, did a fresh install of Windows 7 Ultimate completely legit. Then I go right back to the BSOD problem.

I should also point out that the computer before this was also behaving in a way I forgot to add. The BSOD used to be followed be a few others in rapid fire sucession every time I tried to reboot the computer, and then would suddenly be fine.

Then that developed into a new problem where the BSOD then leads to me needing to manually reset the computer several times for Windows to even boot successfully. Sometimes I get a black screen, sometimes I get a black screen with a few small colored dots. And sometimes it gets caught in this wierd min-restart loop where it starts, goes to the screen to ask me if I want to run startup repair, I pick to start windows normally or start up repair and then I am suddenly re-started at the very begining. I am going to try and get you the latest crash dump, but I cannot get the computer to boot successfully. It sits at "Starting Windows" (If I even get that far) and just pulsates until I physically reset it again.

 

[VTV]

Ok, latest BSOD.

There is still another file yet to be analyzed in this thread from BSOD's that happened before I swapped out the hard drive and re-installed Windows. This .dmp is after a new hard drive and fresh install of Windows 7 Ultimate.

 

[Jonathan_King]

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

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: http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

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

...Summary of the dumps:

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[VTV]

So another.dmp file reports hard drive errors? Is it possible that maybe the cord that goes to the hard drive is bad?

 

[Jonathan_King]

The DMP itself doesn't point to a hard drive issue; it suggests a generic hardware problem. I found that hard drive controller log in the Event Logs, and the rest is just coming from experience.

 

[VTV]

Well, here is the latest. This time I had to physically restart the computer about twenty times to get it to fully boot. When I boot it it either goes into that loop between restarting and asking me if I want to run start up repair or load normally, or it eventually goes to the Windows screen and just never loads entirely, just sitting there pulsating. Sometimes I get it to boot to desktop, and the sound is not working, but then I can restart using windows and the computer runs fine for a while.

 

[Jonathan_King]

I still see that old BIOS version showing; try flashing it to the latest found here: ECS Web Site

[FONT=lucida console]BiosReleaseDate = 05/20/2009[/FONT]

While I don't have high hopes for this fixing the problem, it should still be done: install the latest nVidia drivers from here: Drivers - Download NVIDIA Drivers

Well we did every RAM test we could find, including taking and putting one stick in the computer and running it at a time, no dice.

Was that the Prime95 test? Give Memtest86 a shot as well: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Dec 25 20:08:01.657 2011 (UTC - 5:00)
System Uptime: 0 days 5:24:10.000
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  swtor.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1
BiosReleaseDate = 05/20/2009
SystemProductName = P45T-A
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec 24 22:58:22.949 2011 (UTC - 5:00)
System Uptime: 0 days 13:33:40.208
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+40ed5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  swtor.exe
FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+40ed5
BiosReleaseDate = 05/20/2009
SystemProductName = P45T-A
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Dec 23 03:02:17.057 2011 (UTC - 5:00)
System Uptime: 0 days 4:39:19.750
Probably caused by : ntkrnlmp.exe ( nt!ExfReleaseRundownProtection+7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!ExfReleaseRundownProtection+7
BiosReleaseDate = 05/20/2009
SystemProductName = P45T-A
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Dec 22 22:11:54.677 2011 (UTC - 5:00)
System Uptime: 0 days 4:33:08.021
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiGetTopLevelPfn+65
BiosReleaseDate = 05/20/2009
SystemProductName = P45T-A
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[VTV]

Another point.

I do not know if this is relevant or not, but when I run Ubuntu on this machine it never has any problems at all. So whatever is wrong, it does not happen when I am using Linux.

I updated the driver for my motherboard. I guess we shall see if that helps at all.