Solved Multiple BSOD New custom Build ntfs.sys ntoskrnl.exe

[tunaktu86]

I recently rebuilt my computer with almost all new parts except the 2 160GB HDD's which have all of my old data. I am getting multiple BSOD's but they usually refer to the driver ntfs.sys as the culprit from what I can find.

My previous system was receiving ntoskrnl.exe BSOD's but they were fairly rare. My new machine is getting them sporadically but usually a couple a day. It BSOD's once I ran the SF_Diagnostic Tool.

I have attached the dump files it created.

My PC Specs are in my "System Specs" portion of my profile

3.5Ghz FX-6300
8GB GSKILL Ripjaw X
1x Samsung M 120Gb SSD
1x WD Blue 1TB
GigaByte GA-970A-UD3

 

[YoYo155]

Hello , The file you uploaded is corrupt, try running the SFDT again using the Grab All option.

Seeing how old the drives are I would recommend testing them.

   Warning

This method should NOT be performed on an SSD!

Testing the HDD:

1. Perform a Disk Check | http://www.sevenforums.com/tutorials/433-disk-check.html
2. Then Post the results following | THIS METHOD
3. Download SeaTools for Windows if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

 

[tunaktu86]

OK. I will attempt to get the whole file once I get back home. I will run the Disk Check on my other hard drives and see if it finds any errors.

 

[YoYo155]

Keep us posted .

 

[tunaktu86]

Alright, I got the full dump created. The checkdisk is still running on one of the drives.

The checkdisk completed on both of my old drives and it didn't find any errors

 

[YoYo155]

Thanks .

First of all test your RAM.

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
2 errors : !nt (fffff80003535c04-fffff80003535c3c)
fffff80003535c00  2c  db  d8  ff *ed  5f  ff  ff  ff  49  8b  cd  e8  53  30  d5 ,...._...I...S0.
...
fffff80003535c30  89  70  18  48  89  78  20  41  54  48  83  ec *22  48  83  22 .p.H.x ATH.."H."

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Testing the RAM:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

*When you're done post a picture of results.

---

Install Service Pack 1:

[COLOR=Red][U][B]Windows 7 Kernel Version 7600[/B][/U][/COLOR] MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532

• Learn how to install Windows 7 Service Pack 1 (SP1)
• Service Pack Center - Microsoft Windows

---

Outdated Drivers:

- Razerlow.sys Mon Nov 07 08:33:11 2005

• Driver Reference Table - Razerlow.sys

- lmimirr.sys Wed Apr 11 01:32:45 2007

• Driver Reference Table - lmimirr.sys

- LMIRfsDriver.sys Mon Jul 14 19:26:56 2008

• Driver Reference Table - LMIRfsDriver.sys

Update, remove if possible, LogMeIn and Synapse 2.0.

---

Installed Physical Memory (RAM)    8.00 GB
[COLOR=Red][U][B]Page File Space    1.50 GB[/B][/U][/COLOR]

Reset your Page File:

Start Menu> RUN> "control.exe system" (without the qoutes)
On the Left hand side you'll see

click it.
In this windows
Choose click the settings for Performance.
Then Advanced once more
Then "Change"

Deselect
Choose "No paging file" Click the "Set" button.

Confirm all the windows, restart the PC, reverse the procedure and restart again to take effect.

---

Once that is done enable Driver Verifier:

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.

 

[tunaktu86]

• I ran MemTestx86+ for 6 hours which equated to 4 passes with 0 errors.
  
• Service Pack 1 installed
  
• Razer Driver updated
  
• Synapse 2.0 removed
  
• Pagefile size set to system managed

I did have one strange occurrence. Previously before I got to this forum I found Memtestx86 (no +) and ran that. It errored out quickly and rebooted my machine. I unseated my ram switched around locations of the sticks and then ran memtextx86+

I am going to leave the computer on for the day to see if it gets any BSOD.

 

[YoYo155]

Thanks for the update .
Four passes in not enough unfortunately but it's PC, if it gets BSOD's again I ask you to test the RAM thoroughly.

Memtest86+ and Memtest86 are two different groups, we here find 86+ to be more reliable.
Keep us posted.

 

[tunaktu86]

After my last post I turned on Driver Verify as suggested in the troubleshooting. The computer started up fine, the desktop and icons showed up, then the screen went all cross-hatched and showed the cursor as working and frozen in the center of the screen. It was similar to the picture below but i could still make out the basics of what was on the screen. Very jumbled and cross hatched but it could still be seen.

The computer never went BSOD. It just stayed on that screen, probably for about 15 minutes before I restarted.

 

[YoYo155]

First components that might be causing this are the GPU / Monitor(less likely).
Since you don't have an integrated GPU do you have a spare GPU to test with?

 

[tunaktu86]

Well I tried to reply to this thread that I was still having issues. I have not tried swapping my video card, but the BSOD's have been getting more frequent. One interrupted my posting of the SF Dump.

 

[YoYo155]

Hi sorry for the late reply, life intervened.

The new dumps are similar to the first batch, failing on the reading the file system and the RAM.
The exception being the dumps related to the graphics card.
So please follow the set of test to their full extent.

• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

   Warning

This method should NOT be performed on an SSD!

Testing the HDD:

1. Perform a Disk Check | http://www.sevenforums.com/tutorials/433-disk-check.html
2. Then Post the results following | THIS METHOD
3. Download SeaTools for Windows if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

Testing the RAM:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

*When you're done post a picture of results.

 

[tunaktu86]

I swapped video cards as requested and ran verifier. It ran for 6-10 hours before it BSOD while playing a steam game (DOTA2). I just ran Prime 95, and all of my temperatures were good, CPU 128 degrees. high of 131 low of IdleView attachment 286102

View attachment 286103.

I attached the previous dumps from when verifier was running. I'll attach the other dumps in the next comment.

 

[tunaktu86]

This is the dump from when running Prime95. Max temp I saw on CPU was 130F

 

[YoYo155]

Please don't disregard my questions and suggestions if you wish to continue to receive help.

You're bugchecks are showing increased storage and file system activity.

• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

• Samsung SSD | Samsung Semiconductor Global Website

Does this BSOD happen only while playing DOTA2 on steam?
Please test other games in an attempt to induce the bugcheck.





Driver Verifier wasn't enabled, http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[tunaktu86]

Attached is the image of the Memtest run. 28 Hrs, 15+ passes.

SSD Firmware: I checked the Samsing Magician app as samsung's site suggests and it says I am up to date.
BIOS: I am currently one version behind and the new update is for "Modify setting compatibility of wake up timing" I will update after this post
Chipset Driver: updated with the most recent at build time, checked Gigabyte site to confirm.
SATA AHCI Drivers: Windows said up to date but updated with version on Mobo Site
No IDE ports on board

The Dump was run with verifier turned on.

 

[tunaktu86]

I started DOTA2 again to play a round and got an immediate BSOD. Attached is the dump.

It also BSOD'd as I was typing this post up the first time that one was a page fault in non paged area.

 

[tunaktu86]

I checked the Firmware of the SSD and it is up to date as best as I can find. Samsung magician says it is most updated, and the bootable ISO said the version on the samsung site was not the newest version.

FW version: EXT0AB0Q

 

[YoYo155]

The file you uploaded last doesn't contain any new dumps.
Please verify that Driver Verifier is configured correctly-

Run and elevated command prompt and type in verifier /query.

Start Menu> CMD - right click and Run as administrator.
type verifier /query hit Enter and post a screenshot of the window.

If Samsung Magician states you're up to date than we can trust that you are.
Do you see a pattern with the timing of the BSOD meaning do they happen with regards certain applications
i.e. games / benchmarking / folding / boinc?

Do they happen only when you play DOTA2?

 

[tunaktu86]

It BSOD even when I am doing nothing. It has BSOD when I start windows and sometimes just when chrome is up and also when DOTA 2 is running.

I will check verifier when I get back home. I'm at work right now.