BSOD caused by Ntsf.sys and ntoskrnl.exe

Toggle sidebar Toggle sidebar
C

CitizenKing

Honorable
Jul 31, 2013
27
0
10,530
I have been receiving blue screen errors at a seemingly random rate. I had two last week, but I lost their log files after performing a system restore. Just last night I recieved one with a different bug code check but seemingly the same driver.

Blue Screen View is showing the following.

Bug Check String: KERNEL_DATA_INPAGE_ERROR
Bug Check Code: 0x0000007a
Parameter 1: fffff6fc`40009890
Parameter 2: ffffffff`c000000e
Parameter 3: 00000001`0f86e860
Parameter 4: fffff880`01312748
Caused By Driver: Ntfs.sys
Caused By Address: Ntfs.sys+f2748
File Description: NT File System Driver
Product Name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File Version: 6.1.7600.16385 (win7_rtm.090713-1255)
Processor: x64
Crash Address: ntoskrnl.exe+75bc0

Can anyone please help me figure out whats wrong with my computer?
 
Sort by date Sort by votes
neieus

neieus

Distinguished
Dec 29, 2011
1,776
0
20,460
No that doesn't help at all. I need to see the same information for the other crashes like the one you posted originally. You may need to download "whocrashed" so you can see each of the dump files that were created.
 
Upvote 0 Downvote
C

CitizenKing

Honorable
Jul 31, 2013
27
0
10,530


After doing some research, I ran a verifier check on my drivers to see if any of my third party drivers might be the culprit.

The driver nvlddmkm.sys consistently caused a blue screen, marking it as the culprit. I ran the same verifier process without the nvlddmkm.sys checked and came upon no issues.

UPDATE: Argh, I went back to try and cause a BSOD again so I could get the error number, and now its working fine.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
-normally that error would indicate that the system had attempted to read data from its pagefile on the hard drive back into physical RAM and failed.

this can be caused by certain corruptions in the file system. Windows 8.x will do background repairs of your drives and might fix it over time. Or you can run chkdsk /r /f and do you own checking.
I would also check to make sure all of your system files are ok (not corrupt)
with the system file checker.

sfc.exe /scannow <--- restores corrupted system files from the local backup copy if corruption is found
if that fails (because the backup copy is corrupted)
then on window 8.x you run the dism command
dism.exe /online /check-image /restorehealth
(this command will get a trusted online copy of any corrupted file and repair both of your local copies)

-The error can also be caused by bugs in your driver for your SATA port (update your chipset drivers directly from the manufacture)
- the error can be caused by a bad connection with your SATA cable. Thermal expansion/contraction can cause a bunch of connections and disconnections of your port.
- the error can be cause by a bad port or BIOS setting for your SATA port (mostly not having hotswap enabled)
- the error can be cause by bugs with certain firmware versions in some Solid state drives
- the error can be caused by lazy writes being done to certain spinning hard drives where the drive cache does not write the data. (have to turn off lazy write to these drives before you shutdown the system)


 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom