Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Regular BSOD, was from ntoskrnl.exe, now ntfs.sys

27 Dec 2014   #1
ForgedSalvation

Alabama
 
 
Regular BSOD, was from ntoskrnl.exe, now ntfs.sys

My computer reformatted itself about a month or so ago and I had to reinstall windows a couple of times. I initially installed a cracked version of windows but moved to a legitimate copy as soon as I figured out that I could. Considering my laptop is custom, all of the drivers had to me installed individually. However, when I found my reinstallation and driver discs that came with my computer, I reinstalled everything a third time. All three times, there have been BSODs.


My System SpecsSystem Spec
.
27 Dec 2014   #2
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Hello ForgedSalvation, I'll try to help with your problem. I have looked at the lase several dump files and a little unsure, so I am going to ask you to do something for me. First
Please fill out your System Specs

information   Information
Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

Your dump files seem to indicate that you may have more than one problem. The one that concerns me the most is the last one.

Code:
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc40009970, ffffffffc000000e, 78b13860, fffff8800132e780}
GetPointerFromAddress: unable to read from fffff80002ec0278
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
If that is your problem then all the other dump files are not valid, most likely. If memory is the problem, almost anything and everything will be blamed, even though they are not at fault.
Please Run Memtest86+

information   Information
Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask.
.
My System SpecsSystem Spec
27 Dec 2014   #3
ForgedSalvation

Alabama
 
 

done. sorry about that
anything else you need?
My System SpecsSystem Spec
.

27 Dec 2014   #4
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

That's fine. Just I know your OS id Windows Home Premium. Now, if you will run memtest for me. It has to be run 8 passes all at the same time, each pass is a different test. You are not running the same test 8 times. It will take quite a few hours to run. With 16 GB of ram you are looking at between 16-20 hours. A much of a pain as that is, it is necessary. Believe me, I've been there more times than I care to count, so I understand what I am asking you to do. Please let me know the results when you are finished.
My System SpecsSystem Spec
27 Dec 2014   #5
ForgedSalvation

Alabama
 
 

Absolutely, thank you
My System SpecsSystem Spec
28 Dec 2014   #6
ForgedSalvation

Alabama
 
 

Sitting here at 25hrs on this scan.. Where will the results from this be?
My System SpecsSystem Spec
28 Dec 2014   #7
vaf

Windows 7 Home Premium 64 bit
 
 

essenbe would be looking for any red errors to show up on the screen

This kind of this is good


This is bad


If it has errors then it will look pretty obvious.

MemeTest runs forever. Hit ESC key to stop the test once your happy that it has done a "Pass" or two. 25 hours is more than enough!
My System SpecsSystem Spec
28 Dec 2014   #8
ForgedSalvation

Alabama
 
 

This is what I'm looking at
My System SpecsSystem Spec
28 Dec 2014   #9
vaf

Windows 7 Home Premium 64 bit
 
 

Yep. Your RAM has reported 2 errors in 6 full tests.

It's not a large number, but given your "memory_corruption" error as per essenbe's post you should get the RAM replaced.

RAM has a lifetime warranty so it won't cost anything, however depending on the place of purchase/manufacturer it may take a while to replace so you might have to buy a replacement while you wait for them.

Your system is pretty full on and OTT for 99% of users - what sort of work/play are you doing?!?!?!
My System SpecsSystem Spec
28 Dec 2014   #10
ForgedSalvation

Alabama
 
 

How do I know which stick to replace? I have 4
My System SpecsSystem Spec
Reply

 Regular BSOD, was from ntoskrnl.exe, now ntfs.sys




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Address:ntoskrnl.exe+75bc0; dxgmms1.sys,ntoskrnl.exe,Ntfs.sys
Hi, to make things easier for you,below is the Bug Check String, Driver, and crash address SYSTEM_SERVICE_EXCEPTION___dxgmms1.sys___ntoskrnl.exe+75bc0 MEMORY_MANAGEMENT_______ntoskrnl.exe____ntoskrnl.exe+75bc0 SYSTEM_SERVICE_EXCEPTION___ntoskrnl.exe____ntoskrnl.exe+75bc0...
BSOD Help and Support
Regular BSOD with NTFS.sys with windows 7 x64 clean install
Hello, I would like to ask if anybody knows how to fix the following issue: I have performed a clean install of windows 7 x64. My PC was performing fine but after about a week it started giving me regular BSOD with the descritpion ntfs.sys. I have tried fixing the disks using chkdsk /R...
BSOD Help and Support
BSOD ntoskrnl.exe and NTFS.sys
I recently formatted and did a full clean install of Windows 7 because of BSOD trouble, and now it is back to haunt me. For that reason, I think it is a hardware issue. I attached the 7 forum diagnostic tool report. Please help
BSOD Help and Support
BSOD - ntoskrnl.exe and ntfs.sys
Hello, I am having BSOD randomly and it can occur even when I am not doing anything. I am using a toshiba satellite laptop and run on an ssd vertex3 ocz operating on windows 7 ultimate. There are two different stop codes, the one that occurs most frequently is 0x000000f4 and the other is...
BSOD Help and Support
Regular BSOD , ntfs.sys common
Ok this is my third attempt at writing a thread about my BSODS before being rudely interrupted by said BSODS :cry: so i'll keep it short for now and exapand in between resets. Regular BSOD, usually within one hour of reboot. No specific task causing it (anything really, browsing net, playing...
BSOD Help and Support
Regular BSOD's, caused by ntoskrnl.exe?
Hello, I have installed Windows 7 Home premium x64 on a system I built myself, and keep getting regular bluescreens. When I looked at the dumps with Bluescreenview, it always has ntoskrnl.exe highlighted in red. Help please?
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:57.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App