ntoskrnl.exe BSOD

Page 1 of 9 123 ... LastLast

  1. Posts : 101
    Windows 7 Home Premium 64 bit
       #1

    ntoskrnl.exe BSOD


    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.
      My Computer


  2. Posts : 26,861
    Windows 11 Pro
       #2

    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. Disk Check.

    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 Blue Screen of Death (BSOD) Posting Instructions 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.
      My Computer


  3. Posts : 101
    Windows 7 Home Premium 64 bit
    Thread Starter
       #3

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


  4. Posts : 26,861
    Windows 11 Pro
       #4

    Here is what the dump file says

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {1884c8, 2, 1, fffff80003264929}
    Probably caused by : memory_corruption ( 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.
      My Computer


  5. Posts : 101
    Windows 7 Home Premium 64 bit
    Thread Starter
       #5

    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.
    Last edited by moieu; 14 Oct 2014 at 17:14.
      My Computer


  6. Posts : 26,861
    Windows 11 Pro
       #6

    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
      My Computer


  7. Posts : 101
    Windows 7 Home Premium 64 bit
    Thread Starter
       #7

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


  8. Posts : 26,861
    Windows 11 Pro
       #8

    Did you also run Check disk Disk Check you get another BSOD please run the BSOD Posting instructions again and upload them in a new post.
      My Computer


  9. Posts : 101
    Windows 7 Home Premium 64 bit
    Thread Starter
       #9

    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.
      My Computer


  10. Posts : 26,861
    Windows 11 Pro
       #10

    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.
      My Computer


 
Page 1 of 9 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About 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 06:41.
Find Us