BSOD I think It's the new McAfee 2012


  1. Posts : 3
    Windows 7 64 bit
       #1

    BSOD I think It's the new McAfee 2012


    Hi All,

    Newbie here seeking to identify the cause of new BSOD, appreciate this forum and any assistance greatly!

    I have a Dell XPS 1640 with Windows 7 Home user premium. Bought it retail through my university in Jan 2010. Haven't had any crash issues until yesterday. There are 3 distinct possibilities I can think of, McAfee Total Protection 2012, Adobe Flash, or the 12 Windows updates that installed last evening. I'm attaching the files as instructed in the BSOD posting instruction thread and will detail the 3 issues here:

    1. Flash Player - I use Firefox Beta and have been experiencing flash player crashes a lot in the last few days. I went to the adobe site and downloaded/reinstalled flash on 13 Feb 2012

    2. McAfee Total Protection 2012. My 2011 license expired 20 Jan 2012. Instead of renewing, I purchased a new license through Dell for the 2012 total protection suite. I downloaded, installed, entered the new key and thought I was OK. On 13 Feb when I experienced the Flash Player issues I decided to look at my McAfee Panel for clues. I saw the status: License: 0, Expired 1/20/2012, however the software said I was up to date and needed to take no actions. I referred to McAfee website, which explained that some people experienced issues with purchasing new 2012 software instead of renewing the 2011. The site had a 'clean up tool' to download and a process by which you deleted all McAfee products from your system, ran the 'cleanup tool' and then reinstalled the 2012 product. Since doing that I occasionally get pop up messages that will say my system is unprotected and at risk, but as soon as I click it and go to the home panel of the security suite it says I'm protected and no action is needed.

    3. Last night I checked my updates since I hadn't seen any on the typical Tuesday and my first pass showed no updates available. I checked a few other system tools, then suddenly the update pop up appeared with 12 updates available . I downloaded and installed the updates. I had to leave my office for about 9 hours, when I returned I was at the startup screen for windows. Thought that was odd since I left the computer open on some tasks.

    When I logged in I had the 'windows recovered from an unexpected error' message. I did not do anything at that time to check the error. I got the BSOD and shutdown/auto restart today at 10:30 am and began a few diagnostics. The system was really slow and I found that the prefetch had stopped. I restarted it and restarted my system. I use PCMAtic so I decided to run a full scan/diagnostic. Started it at 12:30.

    It was still running at 3pm and another BSOD/restart interrupted that process. So I set PCMATIC to do a quick scan (more to check registry etc). It fixed 2 startup items only. I haven't had a BSOD since the 3pm event, but things randomly run extremely slow and are unresponsive. I continue to receive the conflicting McAfee messages.

    I think the issue is the McAfee all things considered, and perhaps the Windows updates don't like McAfee in it's present state.

    BSOD analysis files attached, anyone care to take a stab at it?

    Thanks :)
      My Computer


  2. Posts : 1,782
    Windows 7 Home Premium 64bit
       #2

    Two things going on here. One of them isn't McAfee.

    The first problem is that your Intel WiFi driver is causing power state failures. Updating the driver should solve that problem
    Code:
    NETw5s64.sys Tue Sep 15 15:40:39 2009 (4AAFEDB7)
    http://downloadcenter.intel.com/conf...ws+7+(64-bit)*

    The other problem you're having is that three of the crashes stated that there was an error with disk hardware (see below)

    Please run these hard drive scans
    Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests
    Disk Check


    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Mon Feb  6 13:22:12.241 2012 (UTC - 5:00)
    System Uptime: 1 days 2:19:51.864
    Probably caused by : pci.sys
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9F_3_NETw5s64_IMAGE_pci.sys
    BiosReleaseDate = 11/19/2009
    SystemManufacturer = Dell Inc.
    SystemProductName = Studio XPS 1640
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz"
    MaxSpeed:     2530
    CurrentSpeed: 2527
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Fri Feb  3 21:59:56.191 2012 (UTC - 5:00)
    System Uptime: 0 days 2:34:08.814
    Probably caused by : pci.sys
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9F_3_NETw5s64_IMAGE_pci.sys
    BiosReleaseDate = 11/19/2009
    SystemManufacturer = Dell Inc.
    SystemProductName = Studio XPS 1640
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz"
    MaxSpeed:     2530
    CurrentSpeed: 2527
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Wed Feb  1 22:37:47.350 2012 (UTC - 5:00)
    System Uptime: 0 days 22:47:37.833
    Probably caused by : pci.sys
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9F_3_NETw5s64_IMAGE_pci.sys
    BiosReleaseDate = 11/19/2009
    SystemManufacturer = Dell Inc.
    SystemProductName = Studio XPS 1640
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz"
    MaxSpeed:     2530
    CurrentSpeed: 2527
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sat Jan 28 07:32:58.021 2012 (UTC - 5:00)
    System Uptime: 3 days 14:51:53.519
    Probably caused by : pci.sys
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9F_3_NETw5s64_IMAGE_pci.sys
    BiosReleaseDate = 11/19/2009
    SystemManufacturer = Dell Inc.
    SystemProductName = Studio XPS 1640
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz"
    MaxSpeed:     2530
    CurrentSpeed: 2527
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Thu Feb 16 09:36:41.155 2012 (UTC - 5:00)
    System Uptime: 0 days 11:23:33.778
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+37bba )
    ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
    DISK_HARDWARE_ERROR: There was error with disk hardware
    BUGCHECK_STR:  0x7a_c0000185
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+37bba
    BiosReleaseDate = 11/19/2009
    SystemManufacturer = Dell Inc.
    SystemProductName = Studio XPS 1640
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz"
    MaxSpeed:     2530
    CurrentSpeed: 2527
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Thu Feb 16 15:11:18.065 2012 (UTC - 5:00)
    System Uptime: 0 days 3:12:59.688
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+37bba )
    ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
    DISK_HARDWARE_ERROR: There was error with disk hardware
    BUGCHECK_STR:  0x7a_c0000185
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+37bba
    BiosReleaseDate = 11/19/2009
    SystemManufacturer = Dell Inc.
    SystemProductName = Studio XPS 1640
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz"
    MaxSpeed:     2530
    CurrentSpeed: 2527
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Wed Feb 15 14:59:22.228 2012 (UTC - 5:00)
    System Uptime: 0 days 8:28:53.852
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+37bba )
    ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
    DISK_HARDWARE_ERROR: There was error with disk hardware
    BUGCHECK_STR:  0x7a_c0000185
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+37bba
    BiosReleaseDate = 11/19/2009
    SystemManufacturer = Dell Inc.
    SystemProductName = Studio XPS 1640
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz"
    MaxSpeed:     2530
    CurrentSpeed: 2527
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  3. Posts : 3
    Windows 7 64 bit
    Thread Starter
       #3

    Thank you! Ran the chkdsk overnight and several sectors required attention.

    I have already recommended this forum to others, wonderful to receive knowledgeable and prompt assistance in a forum of very helpful people
      My Computer


  4. Posts : 1,782
    Windows 7 Home Premium 64bit
       #4

    Ok. Makre sure you run the chkdsk a couple more times until it reports no errors and also make sure you update that driver
      My Computer


  5. Posts : 3
    Windows 7 64 bit
    Thread Starter
       #5

    updated that driver first off, will run chkdisk again later today once I'm able to dislodge my butt from work ;0)

    Thanks again :)
      My Computer


 

  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 07:15.
Find Us