Solved BSOD STOP error ntfs & ntoskrnl

[Deman]

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.

 

[MvdB]

Hello Dman, welcome to SF!

You seem to have multiple problems that could still be HW and or drivers.

What I don't understand from your story is the statement that you replaced the harddrive while the testsoftware indicated RAM. Is this a mistake in your (otherwise fine) English?

Do you have BSOD's when you run the system in Safe Mode?

Can you de-install AVG, reboot and download latest? Its driver is not installed correctly. (the AVG AVI loader driver)

Please have a look at: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

and check your system for Malware, to be sure... : Malwarebytes : Malwarebytes Anti-Malware PRO removes malware including viruses, spyware, worms and trojans, plus it protects your computer

 

[Deman]

What I don't understand from your story is the statement that you replaced the harddrive while the testsoftware indicated RAM. Is this a mistake in your (otherwise fine) English?

Yes thats the weird part This samsung ESTOOLS hdd checker program that works in DOS is bugged I think. When you google the RAM error (some people think RAM error refers to cache error in the HDD) you see lots of people complain about it even though their HDD is just fine.
Although people say that the new ESTOOLS version fixed it, but I still get that error. So I think ESTOOLS is maybe a bugged program released by samsung.

I will do the steps you posted and will edit this post with results.

Also about running the system in safe mode I have no idea. Should I just do all your steps and run w7 idle in safe mode overnight? The very few times I used safe mode there were no problems.

 

[MvdB]

OK, thx.

Be sure to go through these steps if you haven't already...http://www.sevenforums.com/tutorials/63072-troubleshooting-7-a.html

Go ahead and let it run on safeboot during the night, should not be a problem.

I do not believe the W7 disc is a problem. If scratches cause problems... you'll be told when it is read / installing. No error message = no disc read problem.

 

[Deman]

Avg uninstalled and installed again. It won't really make a difference because it just corrupts because of all the BOSD's.
I did sfc scan once again and as it does all the time it just can't repair this: "C:\Windows\Help\mui\0413\diskmgt.CHM"
Malwarebytes had no results, did full scan so that's sorted.

Looking @ the trouble shooting guide.
Bios is fully updated.
Temps ain't a problem.
Dust same.
Seatools windows version had good results no errors.
Memtest from the previous 15hour session no errors.
About the conflicting IRQ things I have no idea. I think it looks fine but you can take a look yourself.

Any upcoming suggestions? I'll let it run idle in safe mode tonight to see if it bosd's. However, the BOSD happening is completely random, sometimes it never BOSD's no matter if it is on for over 24 hours. And the next time it BOSD's randomly or when the pc shows random crashes.

Dont forget to watch the new memory dump I edited in my first post. It's one I have never seen before. The write readonly memory.

 

[MvdB]

Please rename "C:\Windows\Help\mui\0413\diskmgt.CHM"
to "C:\Windows\Help\mui\0413\diskmgt.CHM.old"

and reboot.

 

[Deman]

After renaming it it didn't recreate on reboot. So I did sfc again.
However since the file is corrupt since install it wont fix.

2011-07-11 19:58:21, Info CSI 000005fe [SR] Cannot repair member file [l:22{11}]"diskmgt.CHM" of Server-Help-CHM.diskm_v.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"nl-NL", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-07-11 19:58:21, Info CSI 00000600 [SR] Cannot repair member file [l:22{11}]"diskmgt.CHM" of Server-Help-CHM.diskm_v.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"nl-NL", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-07-11 19:58:21, Info CSI 00000601 [SR] This component was referenced by [l:240{120}]"Server-Help-Package.ClientUltimate~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.Server-Help-Package.ClientUltimate-Update"
2011-07-11 19:58:21, Info CSI 00000604 [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\Help\mui\0413"\[l:22{11}]"diskmgt.CHM"; source file in store is also corrupted

But the question is, could this possible be the BSOD culprit or is it just an unimportant file?

 

[MvdB]

After renaming it it didn't recreate on reboot. So I did sfc again.
However since the file is corrupt since install it wont fix.

2011-07-11 19:58:21, Info CSI 000005fe [SR] Cannot repair member file [l:22{11}]"diskmgt.CHM" of Server-Help-CHM.diskm_v.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"nl-NL", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-07-11 19:58:21, Info CSI 00000600 [SR] Cannot repair member file [l:22{11}]"diskmgt.CHM" of Server-Help-CHM.diskm_v.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"nl-NL", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-07-11 19:58:21, Info CSI 00000601 [SR] This component was referenced by [l:240{120}]"Server-Help-Package.ClientUltimate~31bf3856ad364e35~amd64~nl-NL~6.1.7601.17514.Server-Help-Package.ClientUltimate-Update"
2011-07-11 19:58:21, Info CSI 00000604 [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\Help\mui\0413"\[l:22{11}]"diskmgt.CHM"; source file in store is also corrupted

But the question is, could this possible be the BSOD culprit or is it just an unimportant file?

If i'm not mistaken it is important. Can you do a repair install with your W7 disc?

 

[Deman]

I already tried that but for some reason its corrupted. I also even tried pulling the file from w7 downloads but they don't even have that file.
Could it work if I pull it from my laptop which is a 32bit and home edition? Or should it be the exact same windows?

Do you have w7 ultimate 64bit? Maybe you could give me the file because I just cant find it anywhere.

 

[MvdB]

I already tried that but for some reason its corrupted. I also even tried pulling the file from w7 downloads but they don't even have that file.
Could it work if I pull it from my laptop which is a 32bit and home edition? Or should it be the exact same windows?

Do you have w7 ultimate 64bit? Maybe you could give me the file because I just cant find it anywhere.

This is very strange. This file is not something special. All it is is an automated HTML file.. a help file about diskmanagement. Not critical at all. Except if it was infected by malware... I would not even expect sfc to have a problem with it...

You still have the .old don't you? What size is it? should be 85kB. If you rename it to original (diskmngmnt.chm) do you get the correct icon?
View attachment 164626

If yours looks identical to this, and when scanned, is clean... double click and check if you get a help file?

 

[Deman]

I already tried that but for some reason its corrupted. I also even tried pulling the file from w7 downloads but they don't even have that file.
Could it work if I pull it from my laptop which is a 32bit and home edition? Or should it be the exact same windows?

Do you have w7 ultimate 64bit? Maybe you could give me the file because I just cant find it anywhere.

This is very strange. This file is not something special. All it is is an automated HTML file.. a help file about diskmanagement. Not critical at all. Except if it was infected by malware... I would not even expect sfc to have a problem with it...

You still have the .old don't you? What size is it? should be 85kB. If you rename it to original (diskmngmnt.chm) do you get the correct icon?
View attachment 164626

If yours looks identical to this, and when scanned, is clean... double click and check if you get a help file?

No virus, old file is same as the new one ofcourse since he gets it from the same location. Exact size is 86,1kb displayed in the column as 87kb.

I also had a new BSOD today. Same ntfs.sys crap. NTFS_SYSTEM_FILE 0x00000024.
The amount of BSOD's start stacking. Now I have at least one a day. I think my pc will die again soon.

It's like the BSOD starts once a week, than it starts to do twice a week until a few times a day and than it wont boot windows any more.

New dump included

 

[Deman]

K, since no suggestion has been made yet I will try one of my many thousands try's
Reading this:

a test on the system the first thing in the morning (when the system is cold) and then another after the system has run for an hour or two. If it doesn't run in Windows, run the memory test for ½ hour, then shut down and start it over. This is because we've been seeing some issues with test results that differ when the system is cold and when it's warm.​

Shows me that running memtest on usb in the evening for 15 hours ain't good enough. I will now try to run memtest tomorrow when I wake up.

Edit: I found this, http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=308
I5 2500k is P67/H67 right? So if my memory is fine when I start my pc cold than I could try updating firmware.

 

[MvdB]

I'm not sure yet. Is you MOBO the B3 version or not?

If it is.. I'd only download latest drivers from here: GIGABYTE - Motherboard - Socket 1155 - GA-PH67A-UD3-B3 (rev. 1.1)

 

[Deman]

I already upated my bios to te max. It was quiet a hassle since they made a version which could only be updated with crappy @bios program. My motherboard rev is 1.0.
I think the hdd firmware update will fix it, what do you think about it?

 

[MvdB]

I already upated my bios to te max. It was quiet a hassle since they made a version which could only be updated with crappy @bios program. My motherboard rev is 1.0.
I think the hdd firmware update will fix it, what do you think about it?

mmm not sure yet. But in my previous post I was not talking about firmware or BIOS but normal system drivers that you need to update from the link I provided (if mobo = a B3 version, there is a similar page there to download drivers from in acse you have the older non-B3).

 

[Deman]

I already upated my bios to te max. It was quiet a hassle since they made a version which could only be updated with crappy @bios program. My motherboard rev is 1.0.
I think the hdd firmware update will fix it, what do you think about it?

mmm not sure yet. But in my previous post I was not talking about firmware or BIOS but normal system drivers that you need to update from the link I provided (if mobo = a B3 version, there is a similar page there to download drivers from in acse you have the older non-B3).

Ok, I'll do that. Should I install the sata raid driver? No clue what it is. Something about my hdd but thats all I know. There is some preinstall and a normal driver. What to do? Both? Or only the normal one and not the preinstall?

 

[MvdB]

Yes, the normal one.

 

[Deman]

I installed all the others except the sata raid driver.
The sata raid driver says my computer does not meet the minimum requirements for this installation.

Do I need the preinstall? Or is it just not compatible with my pc?

Edit: I have GA-PH67A-UD3 (rev. 1.0)

 

[MvdB]

Thats why I needed the version of your mobo. It is not B3 so you need the other link:
GIGABYTE - Motherboard - Socket 1155 - GA-PH67A-UD3 (rev. 1.0)

These intel sata drivers should be fine.

 

[Deman]

They aren't I tryed them, I installed all the drivers for the correct motherboard but the sata one doesnt works.

Edit: Wait I'll reboot pc. Nope, reboot didn't fix it. It keeps saying I don't have the minimum requirements. What are the minimum? :'(

Anyway, should I resort to the pre driver? Maybe the pre driver is needed for the normal one.
Do I even have sata raid? In device management I see my HDD as an ata.
According to my dad I don't have a raid setup, it'll be in the future though because I have two 1tb hdd's. But I first wanna solve the bsod before I put the next one in.
So I guess I should update the hdd firmware?