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 f4, ntoskrnl.exe-7f1c0


01 Jun 2012   #1

Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
BSOD f4, ntoskrnl.exe-7f1c0

I have been getting a BSOD in my fresh Windows install, I'm running Windows 7 Pro x64 (MSDNAA).

I had done a clean install after I got a couple of BSOD f4 but now I'm still getting the same BSOD! I've already collected some dump with and without running Driver Verifier.

Before clean install I updated my BIOS, I updated SSD firmware and I runned a memtest: my ram passed the test.

sfc /scannow report: "Windows Resource Protection did not find any integrity violations."

When I runned Windows_NT6_BSOD_v3.03_jcgriff2_.exe I got a BSOD because of HIDCLASS.SYS

Hopefully i can get some help here

PS: sorry for my poor English


My System SpecsSystem Spec
.

01 Jun 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Problem Devices:
Code:
ehdrv	ROOT\LEGACY_EHDRV\0000	This device is not present, is not working properly, or does not have all its drivers installed.
epfwwfp	ROOT\LEGACY_EPFWWFP\0000	This device is not present, is not working properly, or does not have all its drivers installed.
Network Controller	PCI\VEN_168C&DEV_0023&SUBSYS_3071168C&REV_01\5&D93DF5B&0&0800E6	The drivers for this device are not installed.
Security Processor Loader Driver	ROOT\LEGACY_SPLDR\0000	This device is not present, is not working properly, or does not have all its drivers installed.
Was the crash report jcgriff2 executable run in Safe Mode? Make sure the above drivers get installed to provide system stability. If you need help with the drivers, fill in your system specs in your profile and not in a post in this thread: System Info - See Your System Specs


What kind of memtest did you run? How many passes?

Your crashes primarily indicate 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 the short and long tests with SeaTools for 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, uninstall it in device manager and see if the system performs better.

  • 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
02 Jun 2012   #3

Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Quote:
ehdrv ROOT\LEGACY_EHDRV\0000 This device is not present, is not working properly, or does not have all its drivers installed.
epfwwfp ROOT\LEGACY_EPFWWFP\0000 This device is not present, is not working properly, or does not have all its drivers installed.
Solved: uninstalled Nod32

Quote:
Network Controller PCI\VEN_168C&DEV_0023&SUBSYS_3071168C&REV_01\5&D93DF5B&0&0800E6 The drivers for this device are not installed.
Solved: Installed wireless network card driver

Quote:
Security Processor Loader Driver ROOT\LEGACY_SPLDR\0000 This device is not present, is not working properly, or does not have all its drivers installed.
What is it? I reinstalled ATI driver but I don't know if the problem is solved...

Quote:
Was the crash report jcgriff2 executable run in Safe Mode? Make sure the above drivers get installed to provide system stability. If you need help with the drivers, fill in your system specs in your profile
The crash happen while I wasn't in Safe Mode, it run fine in Safe Mode.
I filled my system spec.

Quote:
What kind of memtest did you run? How many passes?
Memtest86+ v4.20 - 6 passes

Quote:
Run Disk Check
No problems

Quote:
Run the short and long tests with SeaTools for HDDs.
The HDD pass all tests
My System SpecsSystem Spec
.


03 Jun 2012   #4

Windows 7 Home Premium 64 Bit
 
 

All problem devices solved. Nice work!!!

Did you find any viruses or malware?

Is everything up to date for the SSD?
Uninstall the jmicron controller from IDE ATA/ATAPI controllers in Device Manager.
  1. First, download the Intel driver. Then do the next steps.
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Find the device you are trying to uninstall by expanding the appropriate set of devices
  7. Right click the device
  8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  10. Restart your computer only if Windows asks you to.
  11. Install the Intel driver for the device.

Alternatively:
  1. Login as an adminstrative user.
  2. First, download the Intel driver. Then do the next steps.
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Find the device you are trying to uninstall by expanding the appropriate set of devices
  8. Right click the device
  9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  11. Restart your computer only if Windows asks you to.
  12. Install the Intel driver for the device.

The following may also be helpful info: SSD controller?
My System SpecsSystem Spec
03 Jun 2012   #5

Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

No viruses or malaware and SSD firmware is up to date!

Yesterday no BSOD happened during HDD test and suddenly I've got a lot of BSOD while posting the result here. (I updated the attached file 3-4 times)

EDIT: new BSOD because of DXGKRNL.SYS

EDIT 2: jmicron RAID controller replaced
My System SpecsSystem Spec
03 Jun 2012   #6

Windows 7 Home Premium 64 Bit
 
 

You had a 0x7A BugCheck code. For that Bugcheck:
Quote   Quote: Originally Posted by Windows Dev Center - Hardware
Cause

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:
  • 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.

  • 0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.

  • 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.

  • 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.

  • 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.

These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).

Another common cause of this error message is defective hardware or failing RAM.

A virus infection can also cause this bug check.

Resolution

Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.

If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.

Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.

Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer.

Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error.

Make sure that the latest Windows Service Pack is installed.

If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error.

Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.
The above was taken from Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR.


Yours says a device that does not exist was specified. I am thinking your SSD is disappearing from the system.

Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.
  1. Power off the system.
  2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
  3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
  4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
  5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
  6. Let the computer remain in the BIOS for 20 minutes.
  7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
  8. Leave the drive disconnected for 30 seconds to let all power drain from it.
  9. Replace the drive connection(s) and then do steps 4-8 again.
  10. Repeat steps 1-4.
  11. Start your computer normally and run Windows.

The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community

While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.
My System SpecsSystem Spec
06 Jun 2012   #7

Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

No BSOD in the last 48 hours (after jmicron controller replacement). I've done the SSD power cycle.

I mark this thread as solved (can I reopen it if I get a new BSOD?)

Thank you very much for your help.
My System SpecsSystem Spec
06 Jun 2012   #8

Windows 7 Home Premium 64 Bit
 
 

You're welcome. I'm glad I was able to point you in the right direction. You did the work, and you did a great job!

Happy to see it solved.
My System SpecsSystem Spec
Reply

 BSOD f4, ntoskrnl.exe-7f1c0




Thread Tools



Similar help and support threads for2: BSOD f4, ntoskrnl.exe-7f1c0
Thread Forum
Solved BSOD Caused By Driver ntoskrnl.exe (+7f1c0) BSOD Help and Support
Solved bsod driver_power_state_failure ntoskrnl.exe+7f1c0 BSOD Help and Support
Solved BSOD in ntoskrnl.exe+7f1c0 on new Laptop Win 7 64 bit BSOD Help and Support
BSOD : Caused by address : ntoskrnl.exe+7f1c0 BSOD Help and Support
BSOD without reason? ntoskrnl.exe 7f1c0 BSOD Help and Support
Solved new laptop, BSOD caused by ntoskrnl.exe+7f1c0? BSOD Help and Support
BSOD ntoskrnl.exe-7f1c0 while idling 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 04:59 AM.
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