Solved Several different BSOD appearing randomly over last 8 month

[knokkeldoomed]

Hi,

During the last 8 month my computer has had around 15 - 20 BSOD out of the blue so to speak, 6 happened in May 2014, so I desperate to find a solution

I have not been able to identify a single task/program that triggers the problem - so I can't reproduce, just sit down and wait for it to happen again - very frustrating.

Sometimes it happens when i'm programming in Visual Studio, other times when the system is idle, and I'm working on my second pc. I have a feeling, that the NVIDIA Graphics is a part of the problem, because upgrading the driver often causes af BSOD shortly after, so i've downgraded to an earlier version.

The following drivers has been involved in the crashes in may according to my BSODviewer: fltmgr.sys, ntfs.sys, ntoskrnl.exe, nvlddmkm.sys

But I really don't know how to proceed.

Thanks for reading this far, hope someon can point me in the right direction

-- Nicholai

NB: There is also a build-in graphics card on the mootherboard, but i'm using the NVIDIA.

 

[koolkat77]

Welcome to the forum knokkeldoomed,

The errors seem to be Hard drive related. But scattered so hard to say something for sure.

Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Wed May 21 20:00:17.347 2014 (UTC + 6:00)
System Uptime: 0 days 6:37:38.534
BugCheck 50, {fffffa809a57725c, 1, fffff880012149dc, 5}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDecrementCloseCounts+2c )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Thu May 15 23:01:36.172 2014 (UTC + 6:00)
System Uptime: 0 days 10:26:06.894
BugCheck 24, {1904fb, fffff88007943008, fffff88007942860, fffff88001250f00}
Probably caused by : Ntfs.sys ( Ntfs!NtfsSnapshotScbInternal+160 )
BUGCHECK_STR:  0x24
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Thu May 15 12:29:29.347 2014 (UTC + 6:00)
System Uptime: 0 days 0:03:18.533
BugCheck 4E, {99, 62e822, 0, 62e8a2}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  devenv.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun May  4 17:28:37.673 2014 (UTC + 6:00)
System Uptime: 0 days 17:49:45.469
BugCheck A, {0, 2, 1, fffff800032a2128}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+38 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  psia.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Fri May  2 20:07:34.600 2014 (UTC + 6:00)
System Uptime: 0 days 23:45:17.936
BugCheck A, {536b, d, 0, fffff800032e64a7}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu May  1 20:21:35.131 2014 (UTC + 6:00)
System Uptime: 0 days 8:58:45.317
BugCheck 3B, {c0000005, fffff80003275704, fffff8800c3826f0, 0}
Probably caused by : memory_corruption ( nt!MiDeletePteList+1aa )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wbengine.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

If you have an SSD, make sure the firmware is up to date.

Reduce items at start-up:

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot:

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Post a screenshot of your Hard Drive(s) using Crystal Disk Info software:

• CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test:

• http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html


If that does no provide stability,

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

 

[knokkeldoomed]

Thank you very much for you reply

I have now had time to perform some of the actions you suggest.

1) It turned out, that I had a SSD with some old firmware - it's now updated using Samsung Magician software. But when I look at the properties of my HD through Windows Device Manager, the driver still seems to be some old MS stuff from 2006. I thought 'firmware' was 'the driver' - but maybe it's just the software that the driver talks to?

2) I have run Seatools - and both "Samsung SSD 840 ATA" and "ST1000DM003-1CH162 ATA" passed "SMART-check", "Short Drive Self Test", "Short Generic" and "Long generic". Neihter was exposed to the advanced test.

3) I have also performed a complete 'chkdsk' on both HD without finding any errors

4) Windows "Memory Diagnostic" tools reports no error

5) My 32GB RAM passed Memtest86+ 15 times without any errors turning up

6) Finally i've deactivated the build-in graphicscard on the motherboard and updated the NVIDIA driver through Windows Update.

7) CrystalDisk reports that both HD is "100% good"

8) Speccy shows no critical temperatures in my opinion - it's just a little above the room temperature.

---

I have not yet reduced the items at startup nor perform a cleanboot - because the PC can work fine for weeks before the BSOD suddenly appears. So I really dont know whether or not it makes a difference if I deactivate some programs / services.

---

I hope it was the outdated 'firmware' that triggered the BSOD this time, but I still have a strange feeling, that it will turn up in the near future (as usual). But at least it's been stable for the last 6 days or so

Thank you very much for your help

regards Nicholai


NB: i've uploaded the screenshots from Crystal Disk, Speccy ect.

 

[koolkat77]

Thanks for the update.

 

[knokkeldoomed]

Hi again,

Once again my pc was hit by the BSOD - but this time a new error I've never experienced before
So unfortunately my previous attemps to solve the problem failed

I've upload the files from the SF-Tool and will be grateful if someone will take a look and 'translate' the info into something more helpfull than just "DRIVER_IRQL_NOT_LESS_OR_EQUAL"

It seems like it's often caused by driver 'ntokrnl.exe' and the same address - but I guess thats the OS system and that doesn't make much sense to me.

regards Nicholai

 

[knokkeldoomed]

Damn , while I was writing the post above, another BSOD just happened. Once again I was not using the pc for anything special - actually just copying the zipfile for the post above.

Here's the new Sf diagnostic zip-files.

Any help would be appreciated.

Nicholai

 

[Arc]

5) My 32GB RAM passed Memtest86+ 15 times without any errors turning up

Memtest86+ is counted by passes. You need to run at least 8 consecutive passes to decide anything about the RAM. Have you done it? If not, please do.

If at least 8 consecutive passes are passed, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[knokkeldoomed]

Thanks for your reply.

I'll take at look at the "Driver Verifier" link straight away

Regarding the "at least 8 consecutive passes". I had it running for 5 full passes, then I turned it of, because of a heavy thunderstorm hit my area. Later I started all over again at had it running for 40+ hours and it passed additional 10 times without errors turning up. I guess that the last 10 times counts as 8 consecutive passes ?

 

[Arc]

Not times, but passes. You may consider your RAM free from errors for the time being.

Let us know how Driver Verifier reacted.

 

[knokkeldoomed]

Hi Again,

I activate 'Driver Verifier' the other night, and the pc has been turned on since (1,5 day approx.).

I've done my normal pc-work without any problems at all, no BSOD. IE reacted slowly, and frooze a couple of time, but thats about it ! Just deactivated the program again.

I've been looking a little into the latest BSOD - it seems to involve "nvlddmkm.sys" which as far as I can tell is related to my Geforce Graphics Card. I'm wondering whether some of the other dumpfiles also indicates that this piece of hardware is involved. But I can't figure out how to dig deeper into the dumpfiles. I using Nirsoft Blue Screen viewer and it more or less always hightlights "fltmgr.sys", "nfts.sys" and "ntoskrnl.exe". I guess "nfts.sys" was related to the outdated SSD firmware - so hopefully this one is out of the picture by now, because the firmware has been updated.

What role is 'fltmgr.sys' playing - something I could remove somehow ?

Or maybe I should remove my Geforce Card and try using one on the motherboard instead ?

Any other suggestions ?

regards Nicholai

 

[knokkeldoomed]

Nice beginning of a new working day - another BSOD

A new one called "KMODE_EXCEPTION_NET_HANDLED" in "ntoskrnl.exe" and "raspptp.sys". The last driver have never caused problems before. I have not yet removed the Graphics Card, so nothing has change on the pc the last coupled of days.

any ideas ?

 

[Arc]

Do two things now.

Download Win7 and Server 2008 R2 Auto Installation Program (the first one in the list) in Realtek
Install the driver following a guide included in the downloaded zip.

Update the BIOS to Version F7 from GIGABYTE - Motherboard - Socket 1150 - GA-Z87-HD3 (rev. 1.x) .... you may use @BIOS to update the BIOS, which is available under Utilities in the download listing.

Let us know how the computer is running after doing these two.

 

[knokkeldoomed]

Hi,

Before I read your post above, I decided to remove the Geforce graphicscard, just to have that piece of hardware removed from the equation for the next period of time.

I have now installed the new realtek driver AND also the new BIOS version. It all went ok, and the pc is up running again. I guess there is nothing else to do now, that just start to use the upgraded system, and hope for the best. For the time being I will leave the NVIDIA Card in it's box, and if the system appears stable for a couple of week, I try to install the card again.

Thank your very much for your advice. It's such a good feeling actually to be able to "do something" in order to try to solve the problem. Seeing the BIOS being upgraded from F2 to F7 gives me hope, that somewhere along the road I will at last find a solution.

I'm very grateful for your help - thank you.

regards Nicholai

 

[Arc]

Good news.

Let us know for any further issue.

 

[knokkeldoomed]

Hi Again,

The last 6 weeks the system has been stable while being used intensively, so I have decided it's time to put my NVIDIA Card back in business Hopefully no BSOD will turn up

 

[Arc]

OK, let us see.

 

[knokkeldoomed]

Nearly 2½ month has gone since I put back the Graphics Card, and not a single BSOD

I think the problem was solved with the updated BIOS - I am very grateful for all the help I have received .´

Regards Nicholai

the happy owner of a 'new' computer that I now actually enjoys working on