ntoskrnl.exe BSOD

[moieu]

I'm attaching everything from the DM Log Collector here. Yesterday I got my first BSOD. It bothered me because I have had plenty of these before and they've all been ntoskrnl.exe BSOD's. So to take the precautionary measures I uninstalled a lot of things I don't use that could be conflicting with other programs, I ran a Malwarebytes full scan and an Avast full scan. I also went through my verifier.exe and set the custom settings I've needed to use before (force pending i/o requests, irp logging) and checked all of my drivers that aren't from Windows. I let my computer run for a good 10 minutes after restarting it with verifier on and no BSOD's came up so I cleared the settings. Today I got another one, which is the one you're going to see in the DM Log Collector (I CCleaned my computer yesterday just to free up some space and it cleared my dmp logs). I'm going to do ram tests tonight but I can almost guarantee you it isn't my ram. I've replaced my ram 3 times and the stick I have has been tested 2 times before with memtest and windows memory diagnostic. I also ran my CrystalDiskInfo and everything is coming back as good with the normal values. The only thing I've noticed that I hadn't noticed before (but it could've been happening, maybe I just wasn't paying attention) is that speccy is showing my cpu running from 55C to 60C. Once it hits 60C it turns orange on speccy so I'm guessing that's when it starts to get a bit too hot. I clean out my case at least once a month and use q-tips for my fan blades. I also have an aftermarket fan on my cpu and I'm not overclocking it. That's basically all I can think of telling you right now that would be important. All my specs should be in the dxdiag but if not I'm running a 660 gtx nvidia on latest update, phenom black x2 amd quad core cpu, I think a 600w psu, 8gb ddr3 ram, and a 1tb hdd. I have one case fan and a rosewill aftermarket cpu fan set to the highest rpm it can go.

EDIT: I almost forgot, something I noticed today is that I will get slight audio crackles when closing programs, opening programs, logging into my user on windows, etc. It doesn't happen all the time and it's not frequent, but it wasn't happening before.

EDIT 2: Seems like my cpu is running below 55C now so extend that range. 50C-60C. I've not seen it hit 61C yet.

EDIT 3: Ok so the sound crackling led to another issue I now have no sound in my headphones. To be sure it wasn't the headphones, I tried my front headphone port and tried another pair of headphones. I'm getting nothing except the nasty frequency interference from the front port, on the actual mobo port I get no sound at all. Sound IS playing on my computer though, I can look at my mixer and see the green bar which indicates there is supposed to be sound. Also my speakers are still my default playback device and I tried the test that windows has for your playback devices (the little ringing to make sure your device is working) and I'm getting no sound on that. I'm going to restart my computer and see if it gets fixed.

 

[essenbe]

Hello moieu, I will try to help with your problems. Unfortunately, your dump file didn't leave us very much information about the cause of the crash. However, all references were to the NTFS file system and filter manager which both, obviously, deal with your hard drive. You explained your situation very well and I appreciate it. CrystalDiskInfo is a good program and I use it too, but it is not a comprehensive test. I would like you to run Seatools for DOS, both the short and the long test. (SeaTools for DOS | Seagate ) The DOS version will be the better test because it will boot from the media you select and the hard drive will not be in use. If you can't boot from the media, I may be able to help or you can run the Seatools for Windows which installs as a program and will run for inside the OS. I would also like you to run Check Disk. http://www.sevenforums.com/tutorials/433-disk-check.html.

If you are going to run memtest, this is the proper way.

Please Run Memtest86+

   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​

When that is complete, please open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Please let us know how those go, and upload the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html if you get another BSOD, and please don't run CCleaner or any disk cleanup tools until we get this sorted out.

If you have any questions, please feel free to ask them. You may also look on your Motherboard's web site for your board and see if they have any new driver for your board, particularly the Chipset and audio drivers.

 

[moieu]

Just got another BSOD, here's the dump. I'm going to run seatools now.

 

[essenbe]

Here is what the dump file says

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {1884c8, 2, 1, fffff80003264929}
Probably caused by : [COLOR=red]memory_corruption[/COLOR] ( nt!MiRestoreTransitionPte+109 )
Followup: MachineOwner

That may or may not be the case, but it is what the files are blaming it on. There were still references to NTFS, so I believe, I would start on running the Hard Drive tests then run memtest by the directions listed above.

 

[moieu]

Short test on SeaTools for Windows ran short and long tests fine. Short test on SeaTools DOS ran fine. I was about 80 percent into the long test on DOS when this green box cam up and in black text it said "thanks for using seatools" and had a short guide on how to access your log file from the scan. It looked like a glitch though, like it shouldn't have came up like that. I couldn't click on anything so I had to turn off my comp and turn it back on. I got the windows startup repair on restart and it's still attempting repairs. Like I said I don't know if the long test was glitched or not. I may have pressed a bad key when i was moving my keyboard out of the way cause that's when it happened. Or it could have just been the hdd. I'm going to run memtest soon after this startup repair goes away. I'm typing from my laptop right now btw.

EDIT: Going to run a chkdsk first, then I'll do memtest.

EDIT 2: Ok so something really weird happened. I went to run chksdk and the standard stuff popped up, like it was about to run. Then it said "The volume is clean." and didn't scan at all, just brought windows up and brought me to my user login screen. I'm going to try it again.

EDIT 3: Running the chkdsk now, a ton of corrupted files. I haven't ran a chkdsk in forever haha. It's at 12% completed so far. I'll still run the memtest after just to be sure.

 

[essenbe]

OK, But work on getting the hard drive straightened out if you can, then use this for memtest86+

Please Run Memtest86+

   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​

 

[moieu]

Memtest ran fine no errors and I did the long test again on seatools dos and it was fine also.

 

[essenbe]

Did you also run Check disk http://www.sevenforums.com/tutorials/433-disk-check.htmlf you get another BSOD please run the BSOD Posting instructions again and upload them in a new post.

 

[moieu]

Yes when I ran the disk check it said it was fixing a ton of corrupt files and it took like 3 hours to do. I haven't got a bsod since then.

 

[essenbe]

Try running sfc /scannow, open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[moieu]

Alright ran the sfc /scannow 3 times. In between each time I restarted my computer. After the third time it was still saying it had corrupt files that it couldn't fix. I'm going to go ahead and attach the CBS.Log, not sure if it will be useful to you or not. Also I should mention that the audio cutting out on me happened once again. I've restarted my computer about 6 times since my last tests and it's only happened once so it's not frequent. Also some of my icons have started turning into blank pages. I know how to fix that but I wasn't sure if that could be files in my hdd getting corrupted.

 

[essenbe]

Try running Check Disk again. I assume you know you are in danger of a clean install. I would back up all my personal files. We have a couple of other things we can try first though.

 

[moieu]

Yeah I figured it might end up being a clean install. I'll run a check disk soon.

 

[essenbe]

I've asked for help reading the CBS files.

 

[moieu]

Alright sweet, get back to me if you can get any info out of them. Going to run the check disk soon just got to finish up some course work.

 

[essenbe]

I'm sure you will hear from them, but I'll still be around.

 

[NoelDP]

Here's the summary from the SFC log

 Line 43201: 2014-10-15 17:56:08, Info                  CSI    00000320 [SR] Repairing 1 components
 Line 43202: 2014-10-15 17:56:08, Info                  CSI    00000321 [SR] Beginning Verify and Repair transaction
 Line 43203: 2014-10-15 17:56:08, Info                  CSI    00000322 [SR] Cannot repair member file [l:32{16}]"stobject.dll.mui" of Microsoft-Windows-stobject.Resources, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 43204: 2014-10-15 17:56:08, Info                  CSI    00000323 [SR] Cannot repair member file [l:32{16}]"stobject.dll.mui" of Microsoft-Windows-stobject.Resources, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 43205: 2014-10-15 17:56:08, Info                  CSI    00000324 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"
 Line 43210: 2014-10-15 17:56:08, Info                  CSI    00000326 [SR] Repair complete

I'll post a fix protocol for it later - gotta get to work now.

 

[moieu]

I did a check disk and it went through fine. Sfc /scannow still is saying it can't verify certain files. But I haven't had a bsod in about 4 days.

 

[essenbe]

I guess, if it ain't broke, don't fix it. You had some bad files, but as I understand it, nothing serious. So, unless you have problems, just keep using it. If you start having problems, just post back here in a new post.

 

[NoelDP]

Sorry about the wait - too must to do in real life


I've uploaded a file - miuaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\miuaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\miuaa
or
DIR E:\miuaa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\miuaa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply