4 Replies Latest reply on Mar 15, 2012 2:30 PM by Hayton Branched to a new discussion.

    Blue screen shutdown

      What should I do. I need some suggestions. I am having problems with my pc shutting down.For no reason even If I am not using my pc it shuts off with a blue screen. When I push the power button it powers up like it had no problems. I have a HPE-580t, .i7cpu  6 gb of ram installed.I  have owned this custom pc for 1 year still under warranty. I am the only one who uses it. My other pc that everone in the family uses has no problems.   HP thinks Mcafee may be the problem.I need some help with this. This is the crash Dump analysis Please help.

       

      Thanks Bob R

       

       

       

      Crash Dump Analysis


       

      Crash dump directory: C:\Windows\Minidump

       

      Crash dumps are enabled on your computer.

       

      On Tue 3/13/2012 7:25:29 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\031312-14476-01.dmp
      This was probably caused by the following module: mfehidk.sys (mfehidk+0x21732)
      Bugcheck code: 0x19 (0x20, 0xFFFFF8A00BDC06E0, 0xFFFFF8A00BDC09B0, 0x52D0053)
      Error: BAD_POOL_HEADER
      file path: C:\Windows\system32\drivers\mfehidk.sys
      product: SYSCORE
      company: McAfee, Inc.
      description: McAfee Link Driver
      Bug check description: This indicates that a pool header is corrupt.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
      A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
      Google query: mfehidk.sys McAfee, Inc. BAD_POOL_HEADER


       

      On Tue 3/13/2012 8:49:11 AM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\031312-14820-01.dmp
      This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
      Bugcheck code: 0xBE (0xFFFFF8A00B60029C, 0x3B9000003D11E121, 0xFFFFF88009D86020, 0xB)
      Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
      file path: C:\Windows\system32\ntoskrnl.exe
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT Kernel & System
      Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
      The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

       

      On Fri 3/9/2012 8:33:52 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030912-17955-01.dmp
      This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
      Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003412B05, 0x0, 0xFFFFFFFFFFFFFFFF)
      Error: KMODE_EXCEPTION_NOT_HANDLED
      file path: C:\Windows\system32\ntoskrnl.exe
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT Kernel & System
      Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
      The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

       

      On Thu 3/8/2012 8:04:33 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030812-17596-01.dmp
      This was probably caused by the following module: fileinfo.sys (fileinfo+0x9D35)
      Bugcheck code: 0x19 (0x20, 0xFFFFF8A0045EC3E0, 0xFFFFF8A0045EC500, 0x512011D)
      Error: BAD_POOL_HEADER
      file path: C:\Windows\system32\drivers\fileinfo.sys
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: FileInfo Filter Driver
      Bug check description: This indicates that a pool header is corrupt.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
      The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

       

      On Fri 3/2/2012 8:28:27 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030212-19609-01.dmp
      This was probably caused by the following module: mfehidk.sys (mfehidk+0x2DC83)
      Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880012D4C83, 0xFFFFF88008A53A90, 0x0)
      Error: SYSTEM_SERVICE_EXCEPTION
      file path: C:\Windows\system32\drivers\mfehidk.sys
      product: SYSCORE
      company: McAfee, Inc.
      description: McAfee Link Driver
      Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
      A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
      Google query: mfehidk.sys McAfee, Inc. SYSTEM_SERVICE_EXCEPTION


       

      On Wed 2/29/2012 10:15:18 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\022912-14071-01.dmp
      This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x307F)
      Bugcheck code: 0x50 (0xDCC88000, 0x1, 0x74D730, 0x8)
      Error: PAGE_FAULT_IN_NONPAGED_AREA
      file path: C:\Windows\system32\drivers\dxgkrnl.sys
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: DirectX Graphics Kernel
      Bug check description: This indicates that invalid system memory has been referenced.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
      The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

       

      On Tue 2/28/2012 10:57:35 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\022812-17191-01.dmp
      This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
      Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000329C646, 0xFFFFF8800C1FCB20, 0x0)
      Error: SYSTEM_SERVICE_EXCEPTION
      file path: C:\Windows\system32\ntoskrnl.exe
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT Kernel & System
      Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
      The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

       

      On Sat 2/25/2012 2:08:29 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\022512-23493-01.dmp
      This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
      Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x953, 0x95600001209)
      Error: MEMORY_MANAGEMENT
      file path: C:\Windows\system32\ntoskrnl.exe
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT Kernel & System
      Bug check description: This indicates that a severe memory management error occurred.
      This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
      The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

       

      On Fri 2/24/2012 11:43:04 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\022412-16832-01.dmp
      This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
      Bugcheck code: 0x4E (0x2, 0x12E8D0, 0x26FFFF, 0x2)
      Error: PFN_LIST_CORRUPT
      file path: C:\Windows\system32\ntoskrnl.exe
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT Kernel & System
      Bug check description: This indicates that the page frame number (PFN) list is corrupted.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
      The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

       

      On Thu 2/23/2012 11:32:18 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\022312-17628-01.dmp
      This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
      Bugcheck code: 0x1A (0x3452, 0x13F000, 0xFFFFF70001080550, 0x819000008B5B8800)
      Error: MEMORY_MANAGEMENT
      file path: C:\Windows\system32\ntoskrnl.exe
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT Kernel & System
      Bug check description: This indicates that a severe memory management error occurred.
      This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
      The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

       

      On Sat 2/4/2012 5:51:33 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\020412-14492-01.dmp
      This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
      Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50013D30, 0xFCB00001F5E669FA, 0xFFFFF8A0007FBDA9)
      Error: MEMORY_MANAGEMENT
      file path: C:\Windows\system32\ntoskrnl.exe
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT Kernel & System
      Bug check description: This indicates that a severe memory management error occurred.
      This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
      The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

       

      On Sat 1/28/2012 9:19:28 PM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\012812-16972-01.dmp
      This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
      Bugcheck code: 0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF80003284C10)
      Error: UNEXPECTED_KERNEL_MODE_TRAP
      file path: C:\Windows\system32\ntoskrnl.exe
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT Kernel & System
      Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
      The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

       

      On Tue 1/24/2012 10:22:13 AM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\012412-15490-01.dmp
      This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
      Bugcheck code: 0x19 (0x20, 0xFFFFF8A00D310BD0, 0xFFFFF8A00D310C60, 0x5090302)
      Error: BAD_POOL_HEADER
      file path: C:\Windows\system32\ntoskrnl.exe
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT Kernel & System
      Bug check description: This indicates that a pool header is corrupt.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
      The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

       

      On Tue 1/24/2012 10:22:13 AM GMT your computer crashed
      crash dump file: C:\Windows\memory.dmp
      This was probably caused by the following module: ntfs.sys (Ntfs+0x9D368)
      Bugcheck code: 0x19 (0x20, 0xFFFFF8A00D310BD0, 0xFFFFF8A00D310C60, 0x5090302)
      Error: BAD_POOL_HEADER
      file path: C:\Windows\system32\drivers\ntfs.sys
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT File System Driver
      Bug check description: This indicates that a pool header is corrupt.
      This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
      The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

       

      On Tue 1/24/2012 12:18:23 AM GMT your computer crashed
      crash dump file: C:\Windows\Minidump\012312-14695-01.dmp
      This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
      Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xBA7F, 0xBF2800017409)
      Error: MEMORY_MANAGEMENT
      file path: C:\Windows\system32\ntoskrnl.exe
      product: Microsoft® Windows® Operating System
      company: Microsoft Corporation
      description: NT Kernel & System
      Bug check description: This indicates that a severe memory management error occurred.
      This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
      The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

       


      Conclusion

      17 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

      mfehidk.sys (McAfee Link Driver, McAfee, Inc.)

      If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


      Read the topic general suggestions for troubleshooting system crashes for more information.

      Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

       

      Message was edited by: bobr183 on 3/13/12 4:14:48 PM CDT

       

      Message was edited by: bobr183 on 3/13/12 4:15:22 PM CDT

       

      Message was edited by: bobr183 on 3/13/12 4:15:57 PM CDT

       

      Message was edited by: bobr183 on 3/13/12 5:49:02 PM CDT

       

      Message was edited by: bobr183 on 3/13/12 5:50:30 PM CDT

       

      Message was edited by: bobr183 on 3/13/12 5:52:53 PM CDT
        • 1. Re: Blue screen shutdown
          Hayton

          A serious problem, judging by what you've posted. It's an HP machine, and I know that McAfee has had big problems with HP drivers in the past. Now it's HP's chance to turn the tables and point to a McAfee driver ....

           

          Let's deal with mfehidk.sys first. The version you have may be out of date or corrupt. This is a McAfee Link Driver, and should be digitally signed by McAfee and countersigned by Verisign. Search for the filename starting from c:\windows : there should be only one instance of it. Check the Properties and get the version number, file size, creation date, modification date. Click on Digital signatures and check the signature details - signer name, signing time, countersigner. View the certificate and make sure it's valid (and not expired) and click Install to import it. Then at least you know the file is what it's supposed to be, and with the information above we can find out if it's the latest version. Mine is v.14.4.0.478 and has a signing time of 23 October 2011.

           

          Then run MVT and check your installed McAfee files and registry settings - you never know, something might be missing or need replacing.

           

          You have several crashes involving memory problems. I know that HP (if that's who it was) say that RAM is less likely to be the cause than a faulty driver, but you can't rule out hardware problems. If you haven't got it already, Speccy will give you a detailed picture of your hardware and OS components and it saves a lot of time hunting through specs for the information. And Memtest86 or Memtest86+ - if you have got x86 architecture - will find any problems in your 6Gb of RAM. Expect it to take a while to run. Full details are (amazingly) to be found in Wikipedia, with links for the alternate versions on the page.

           

          Other steps depend in part on what OS you've got, and which version (if applicable), and which McAfee program and version you've got - you didn't say, and we'll need to know. I'm assuming that both McAfee and your OS are up to date, as well as all the important stuff like Java, Flash, Reader and so on.

           

          If you can post back with the mfehidk info, MVT findings, Memtest result (if you run it) and OS & McAfee details we'll do our best to start the fault-finding process. At some point you may need to be bumped up to Tech Support for a detailed investigation, but they'll ask all of this stuff anyway so you save a bit of time.

           

          Message was edited by: Hayton on 14/03/12 16:48:23 GMT
          • 2. Re: Blue screen shutdown
            Hayton

            This has vanished from view after I branched a post.

             

            Should now re-appear, or it's a site bug to report.

            • 3. Re: Blue screen shutdown

              Hayton Looks like my problem may be fixed. I looked at the crash report and remembered that  I had a problem with mcafee after an update. I had to uninstall Mcafee the reinstall Mcafee back in January. This is when my pc started to shut down with the blue screen. But I did not connect the problem I had wnth the blue screen issue.

               

              I ran the MVT scan like you said. Sure enough it found 2 problems in the registry with mcafee. After the scan It said click to fix the problems. It fixed the registry problems.

               

              My pc has been running since 5 am yesterday morning with no crashes. Looks like my problem may be fixed.

               

              Thanks

               

              Bob R

              • 4. Re: Blue screen shutdown
                Hayton

                Okay, but come back and let us know if the crashes come back. And in any case if you downloaded Speccy and memtest you've now got a couple of useful tools for your toolbox.