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: BSOD twice in 5 days (ntoskrnl.exe/ntkrnlmp.exe and ntfs.sys)


19 Jun 2012   #1

Windows 7 Ultimate x64
 
 
BSOD twice in 5 days (ntoskrnl.exe/ntkrnlmp.exe and ntfs.sys)

I got a BSOD twice in the last 5 days. According to WhoCrashed, the first one came from ntfs.sys and the next one from ntoskrnl.exe/ntkrnlmp.exe. Apparently most likely a driver/memory error.

The OS is Windows 7 x64 Ultimate Professional retail. The PC is slightly less than 2 years old and so is the Windows installation (never have reinstalled it). The only newer parts are a PSU and 2 extra RAM sticks (identical to the other two and installed in the correct positions) to go from 4 to 8gb. Both of those came about a month ago.

Any ideas?

My System SpecsSystem Spec
.

19 Jun 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
My System SpecsSystem Spec
19 Jun 2012   #3

Windows 7 Ultimate x64
 
 

Thanks, I'll try that out, see how it goes.
My System SpecsSystem Spec
.


19 Jun 2012   #4

Windows 7 Home Premium 64 Bit
 
 

You're welcome. Look forward to finding out if that resolved it.
My System SpecsSystem Spec
23 Jun 2012   #5

Windows 7 Ultimate x64
 
 

That wasn't it, got another one today. Apparently win32k.sys has come into play as well.

Adding an updated zip including the newest crash.
My System SpecsSystem Spec
24 Jun 2012   #6

Windows 7 Home Premium 64 Bit
 
 

Problematic Software:
Code:
Start Menu\Programs\ASRock Utility	Public:Start Menu\Programs\ASRock Utility	Public
Start Menu\Programs\ASRock Utility\InstantBoot	Public:Start Menu\Programs\ASRock Utility\InstantBoot	Public
Start Menu\Programs\Spybot - Search & Destroy	Public:Start Menu\Programs\Spybot - Search & Destroy	Public
Remove the above.
  • Spybot Search and Destroy is not the best malware/spyware utility. Take a look at Good and Free system security combination. for better options.

  • Recommend removing your ASRock utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability.


The driver pcouffin.sys should be looked at; yours is from 2006 and may be causing conflicts. That link provides instructions on how to handle problems related to that driver.


Crashes are pointing to memory problems or driver conflicts. If the above steps do not resolve the crashes, proceed through the next steps:
  • If you are overclocking any hardware, please stop.

  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
    warning   Warning
    Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

    For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
    Once these steps have been followed, it is safe to remove and replace components within your computer.

  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. In Windows 7:
    • Click the Start Menu
    • Type verifier in Search programs and files (do not hit enter)
    • Right click verifier and click Run as administrator
    • Put a tick in Create custom settings (for code developers) and click next
    • Put a tick in Select individual settings from a full list and click next
    • Set up the individual settings as in the image and click next
      Attachment 218057
    • Put a tick in Select driver names from a list
    • Put a tick next to all non-Microsoft drivers.
    • Click Finish.
    • Restart your computer.

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

    When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
    verifier /reset
    -> Restart your computer.
My System SpecsSystem Spec
24 Jun 2012   #7

Windows 7 Ultimate x64
 
 

Alright, I got rid of pcouffin.sys and the related software, as well as ASRock's InstantBoot and Spybot. I updated my security according to that post and am running scans right now.

Also, I actually ran Memtest86+ yesterday, since I noticed that the trend was either memory or driver issue, on which you seem to agree. I left it on overnight and for a bit today, 10 passes later, no errors found. I'll run the Windows Memory diagnostic tonight and report back on that too, then use the PC normally for a week or so and see how it goes.

Since you mentioned ASRock's overclocking utilities, I actually do have Turbo UCC enabled (which takes my 1055T's 6 cores from 2.6 to 3.2GHz, but I'm not really sure if it actually is responsible for any software/driver within Windows). It feels silly that I forgot to mention that earlier. Anyway, I kinda like it, so I'll try all other things first, but if I still get BSOD's then that's the next one to go.

Driver Verifier is the last resort, I guess.

Thanks again for being so helpful.
My System SpecsSystem Spec
24 Jun 2012   #8

Windows 7 Home Premium 64 Bit
 
 

You're welcome.

The problem with software based overclocking is the voltages are not properly set up to handle the overclock. It is much safer/more stable to apply overclocking via the BIOS. If you want steps for how to do so from experts who can give you specific information: Overclocking and Case Mods - Windows 7 Forums

Make sure if you start a thread in the overclocking forum that the person answering is a Seven Guru or that the person is backed up by a Seven Guru. Overclocking is not something you want to get wrong because it can damage hardware, so you need someone who has the experience to do it right.
My System SpecsSystem Spec
04 Jul 2012   #9

Windows 7 Ultimate x64
 
 

...and 2 weeks later we have another one. I uploaded the new report just in case someone can figure something out while I'm following this thread, trying to fix that same error so I can do a backup and proceed with the verifier.
My System SpecsSystem Spec
05 Jul 2012   #10

Windows 7 Home Premium 64 Bit
 
 

Backup Error 0x81000019:
Backup Error 0x81000019 - Fix may help with the backup issue.
Analysis:
Your most recent crash indicates hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.
  • If you are overclocking any hardware, please stop.

  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk).
    For any drives that do not give the message:
    Windows has checked the file system and found no problems
    run disk check again as above. In other words, if it says:
    Windows has made corrections to the file system
    after running the disk check, run the disk check again.

  • Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
    SeaTools for Windows

    SeaTools for DOS
  • 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.

  • Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.

  • Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.

  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
    warning   Warning
    Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

    For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
    Once these steps have been followed, it is safe to remove and replace components within your computer.
My System SpecsSystem Spec
Reply

 BSOD twice in 5 days (ntoskrnl.exe/ntkrnlmp.exe and ntfs.sys)




Thread Tools



Similar help and support threads for2: BSOD twice in 5 days (ntoskrnl.exe/ntkrnlmp.exe and ntfs.sys)
Thread Forum
Solved BSOD ntoskrnl.exe and ntkrnlmp.exe BSOD Help and Support
Solved How to fix BSOD caused by ntoskrnl.exe and ntkrnlmp.exe BSOD Help and Support
BSOD probably caused by Ntfs.sys, ntkrnlmp.exe, win32k.sys BSOD Help and Support
[HELP] ntoskrnl.exe & ntkrnlmp.exe & fltmgr.sys BSOD Issue BSOD Help and Support
Frequent BSOD, ntoskrnl.exe, ntkrnlmp.exe BSOD Help and Support
BSOD ntoskrnl.exe, ntkrnlmp.exe BSOD Help and Support
Random BSOD with ntoskrnl.exe and ntkrnlmp.exe 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 05:54 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33