New
#1
BSOD STOP error ntfs & ntoskrnl
Hi,
I build my own rig a month ago. And since than the amount of BSOD I've gotten kept growing. I ran all the stuff chdsk, sfc, hdd checkers, memtest and all said it was just fine. However Samsung HDD ESTOOLS gave me a RAM error. So I got the HDD replaced but my BSOD still occur, but less frequent.
System specs:
Windows 7 Ultimate x64
Retail version (disc has slight surface scratches, could this cause it?)
Age of system is a month I guess, OS is like 2 weeks old because of reinstall.
Symptoms @ bosd:
1. Nothing, system just bosd at random times.
2. PC starts, programs start to crash for no reason, than the aero peek also crashes and all apps just crash. This is a sign that a bosd is coming up really soon! And so it does BOSD after a random amount of time.
3. Maybe it has nothing to do with the BOSD, but I noticed that AVG is sometimes shutting down for no reason. I am sure I have no virus, I used the same installation disc for years and on my previous pc there were no problems with this stuff.
Tried solutions:
Seatools
Samsung ESTOOLS
sfc /scannow (The following file is always corrupted and will never repair C:\Windows\Help\mui\0413\diskmgt.CHM)
chkdsk /r
memtest (However, I read somewhere that it matters if you run memtest when the system has been off for a long time, I only ran it at the evening when I was done using my PC and ran it for 15 hours no errors)
I tried downloading other versions of w7 to get the diskmgt.chm file to replace it but it seems newer w7 ultimate x64 versions don't have that file. I also couldn't find the file on Google, could this be the problem? How to get it repaired because the file on the disc is marked by sfc as corrupt.
So whats wrong with my pc? Is it the sata cables? Is it the motherboard? Could the scratched installation dvd be the problem?
I will add in a zip, the bosd dumps & system file collection and the system health report.
In case the disc gets suspicious and is the only reason to bosd than I will get a new one from my neighbour and retry, but I would like to do this solution as last one.
Sorry for my bad grammar, I'm from Holland and even my Dutch grammar sucks.
Edit: new BSOD, never seen this one before. Attempt to write readonly memory.
After writing this story, I enabled the verifier.exe using the settings in the guide posted on this forum. Than I clicked repair all button in AVG to see if it would turn AVG back on. It came with an update which required me to reboot.
So I reboot and my PC just BOSD directly at powering on. Than I restarted my PC and it restarted while booting on after that restart it booted just fine.
New BOSD minidump will be in the attachments.
Last edited by Deman; 11 Jul 2011 at 09:06.