TechSpot

BSOD several times with Win 7 X64

By MartyMarty
May 18, 2010
  1. I am at my wits end here. Please someone help! I have tried everything that different sites have suggested with no help. I will paste the crash dump analysis from "who crashed" Software below but first let me tell you what I have done so far.

    1. Replaced memory boards, before this was the main cause of BSOD
    2. Ran Memtest86t several times, all tests passed
    3. Ran Seagate Disk Tools to make sure HDD was ok
    4. Verified that NVIDIA Drivers were up to date
    5. Changed Paging File Size to 200M rebooted then set Paging File Size to 8000 MB, because I read somewhere to set it twice the size of memory installed. Thus creating a new paging file

    I also called Microsoft Tech Support ... OMG that's two hours of my life I will not get back again! The only help they did was turn me on to the program called Who Crashed.

    Below is the Crash Dump Analysis from the software "Who Crashed"

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.


    On Sat 5/8/2010 1:42:31 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA80012F9529, 0x1, 0x45)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    Dump file: C:\Windows\Minidump\050810-20281-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Sat 5/8/2010 12:39:37 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFFA80064CFB60, 0x0)
    Error: DRIVER_VERIFIER_DETECTED_VIOLATION
    Dump file: C:\Windows\Minidump\050810-19500-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Sat 5/8/2010 12:38:36 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Dump file: C:\Windows\Minidump\050810-22390-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Fri 5/7/2010 1:28:26 AM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x50 (0xFFFFFAA001E5A668, 0x0, 0xFFFFF80002C7901F, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\050710-15984-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Wed 4/28/2010 7:08:39 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFFA8006870B60, 0x0)
    Error: DRIVER_VERIFIER_DETECTED_VIOLATION
    Dump file: C:\Windows\Minidump\042810-19921-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Wed 4/28/2010 6:08:16 PM your computer crashed
    This was likely caused by the following module: ntfs.sys
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF8, 0x0, 0xFFFFF8800124AA99, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\042810-24203-01.dmp
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Wed 4/28/2010 7:24:57 AM your computer crashed
    This was likely caused by the following module: ntfs.sys
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006D317B8, 0xFFFFF88006D31020, 0xFFFFF88001300922)
    Error: NTFS_FILE_SYSTEM
    Dump file: C:\Windows\Minidump\042810-17171-01.dmp
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Tue 4/27/2010 1:32:19 AM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x50 (0xFFFFFA800954AA70, 0x1, 0xFFFFF80002B555A7, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\042710-15406-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Tue 4/27/2010 11:55:56 PM your computer crashed
    This was likely caused by the following module: fltmgr.sys
    Bugcheck code: 0x50 (0xFFFFFA8008FFC320, 0x0, 0xFFFFF880010A9728, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\042710-17531-01.dmp
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Filesystem Filter Manager
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Tue 4/27/2010 10:58:43 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x50 (0xFFFFFAA012ABE338, 0x0, 0xFFFFF80002B6BCC3, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\042710-17046-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Mon 4/26/2010 5:08:52 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0xA (0x34E5F, 0x2, 0x0, 0xFFFFF800028886FB)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Dump file: C:\Windows\Minidump\042610-19953-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Sun 4/25/2010 12:03:03 AM your computer crashed
    This was likely caused by the following module: klbg.sys
    Bugcheck code: 0x50 (0xFFFFFAA0021F8A60, 0x1, 0xFFFFF880010E5CBD, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\042510-21890-01.dmp
    file path: C:\Windows\system32\drivers\klbg.sys
    product: Kaspersky Anti-Virus
    company: Kaspersky Lab
    description: Kaspersky Lab Boot Guard Driver



    On Sun 4/25/2010 12:01:23 AM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    Dump file: C:\Windows\Minidump\042510-24937-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Thu 4/22/2010 7:27:55 PM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x50 (0xFFFFF8FEC333127C, 0x1, 0xFFFFF960002AC649, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\042210-24781-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Mon 4/19/2010 9:33:58 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    Dump file: C:\Windows\Minidump\041910-19843-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Tue 4/13/2010 11:37:39 PM your computer crashed
    This was likely caused by the following module: ntfs.sys
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008973D98, 0xFFFFF880089735F0, 0xFFFFF880012334E0)
    Error: NTFS_FILE_SYSTEM
    Dump file: C:\Windows\Minidump\041310-17562-01.dmp
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Sun 4/11/2010 9:57:17 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x50 (0xFFFFF50008E33A08, 0x1, 0xFFFFFA80012D2E77, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\041110-19796-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Sun 4/11/2010 9:22:05 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    Dump file: C:\Windows\Minidump\041110-21328-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Tue 5/18/2010 9:23:35 PM your computer crashed
    This was likely caused by the following module: win32k.sys
    Bugcheck code: 0x50 (0xFFFFF8FEC083DE34, 0x1, 0xFFFFF9600020C649, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\051810-29500-01.dmp
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Mon 5/17/2010 5:22:02 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x1, 0xFFFFFA8003C5B170, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\051710-16953-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Fri 5/14/2010 2:30:44 PM your computer crashed
    This was likely caused by the following module: fltmgr.sys
    Bugcheck code: 0x50 (0xFFFFFA800B9F88E0, 0x0, 0xFFFFF88001144728, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Dump file: C:\Windows\Minidump\051410-19093-01.dmp
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Filesystem Filter Manager
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Wed 5/12/2010 1:03:12 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Dump file: C:\Windows\Minidump\051210-15812-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Tue 5/11/2010 4:36:44 AM your computer crashed
    This was likely caused by the following module: fltmgr.sys
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800115C2D6, 0xFFFFF88006A34D10, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    Dump file: C:\Windows\Minidump\051110-13234-01.dmp
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Microsoft Filesystem Filter Manager
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


    Thanks in advance for your help.
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 12,167   +37

    Please give us your hardware specs including make and model of your motherboard, make of RAM and how much is installed, video card, harddrive, etc. Also include the OS you are running as well as security software.

    How many Passes did you run memtest for?

    What harddrive tests did your run?

    Also, give us your five most recent minidumps.

    How to find and post your Minidump Files:

    My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

    It is these files that we need (not the folder). Attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip; if you only have one or two you don’t need to zip them, just attach as is. Please do us a favor and don’t Zip each one individually.
     
  3. MartyMarty

    MartyMarty TS Rookie Topic Starter

    Answers

    I ran the mem test for at least 7 or 8 passes. Additionally, I may have forgot to note that replacing the memory was the first thing I did. So this memory is only a few months old. Patriot PC2-6400 (5-5-5-12)

    I ran chkdisk /f /s several times (More than 10 times) on all drivess. Contacted Seagate and the tech said that their disk tools tested more than windows chkdisk does. I ran Seagate Disktools (free download from seagate) for many many passes, basically I let it run all thru the night..


    Attached are the minidump files, last five.
     

    Attached Files:

  4. Route44

    Route44 TechSpot Ambassador Posts: 12,167   +37

    Two minidump files specifically cited the Kaspersaky driver klif.sys as the cause of your system crashes. Update Kaspersky and see if it rectifies the issue.
     
  5. MartyMarty

    MartyMarty TS Rookie Topic Starter

    Still having BSOD

    OK,

    I contacted Kaspersky.... They were very helpful, had me email them my minidump files and they reported the problem wasn't Kaspersky but Roxio 2010. I contacted Roxio about the problem. They were not so helpful. They recommended to uninstall Roxio Creator 2010 which I did. They provided guidance to insure there was a "clean" unininstall. Even had me remove references in the register. I decided not to reinstall right away. Good thing because I had several BSOD's this afternoon just minutes after uninstalling. Back to square one. An IT friend of mine suggested it may be one of the Hard Drives. Help please! The last five dump files attached.
     

    Attached Files:

  6. MartyMarty

    MartyMarty TS Rookie Topic Starter

    What Kaspersky Said

    Below is the statement I got from Kaspersky Tech Support:


    After reviewing all of your files, they show that Kaspersky is not the cause of the crash. Reviewing the mini dump files, it shows that the file at the root of the crash is “fltmgr.sys: which relates to hard drives. This file is “Microsoft Windows File System Filter Manager.” The crashes you are experiencing happen immediately after this error: “A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 12 service to connect.” In this case, it appears to be the Roxio program that is causing the crashes for you, not Kaspersky.
     
  7. MartyMarty

    MartyMarty TS Rookie Topic Starter

    I forgot to give you all the specs on the pc.

    OS Windows 7 x64
    Motherboard: ASRock N61P-S
    CPU: AMD Athlon 64 X2 Dual Core Processor 6000+
    Display Adaptor: NVIDIA GeForce 8600 GT
    Hard Drives
    C: Barracuda 7200.12 500GB
    D: Barracuda 7200.11 1.5TB
    RAM: Patriot Memory PC2-6400 800MHZ (2 x 2GB)
     
  8. Route44

    Route44 TechSpot Ambassador Posts: 12,167   +37

    Two of your errors specifically cite nvstor.sys as the cause of your issue and this is a Nvidia driver that controls your SATA ports. Two of the other errors cite NTFS.sys which is a Windows OS driver but has to do with your ntfs system and harddrives.

    Here are three suggestions based on what I have found. Do as you see fit:

    1. Update your chipset drivers.

    2. Update your BIOS. One person found this to work who was experiencing the very same issues you are.

    3. Go to Seagate's website and download their SeaTools harddrive diagnostic utility. Burn it to a CD and set your CD drive as first bootable. Insert the CD in your drive and reboot. Almost immediately the SeaTools will engage.

    On both drives run these tests: S.M.A.R.T., Short, and especially the Long. This is going to take a lot of time especially the Long test but don't skip it.

    I run Seagate harddrives in two systems and love them (7200.8) but their 7200.11 and 7200.12 versions have had catastrophic fails, especially the 11 series (and the 10 weren't that great either). This is NOT to say your drives are bad but to not diagnose them would be the wrong thing to do especially in light of your error code reads.

    If they are good, so much the better, you did a sound diagnostic step, and you have a free utility to use it whenever you want to.
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.