New
#21
I have plenty of hard drive space and everything is enabled correctly. It is still not creating these files.
I have plenty of hard drive space and everything is enabled correctly. It is still not creating these files.
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.
Hello again VTV, sorry to hear you're still getting BSODs after so long.
I found this entry:It may or may not be relevant to your problem, but we should definitely pursue that. Start by running SeaTools: SeaTools for Windows | SeagateCode: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.
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.Code:chkdsk /r
Next: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.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.
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.
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.
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.
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.
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.
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.
Interesting to see hard disk controller errors reported on a fresh installation with a new hard drive.Let's file that away for the time being.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.
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 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
So another.dmp file reports hard drive errors? Is it possible that maybe the cord that goes to the hard drive is bad?