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 ntoskrnl.exe-7f1c0 while idling

09 May 2012   #1

Windows Home premium 64bit
BSOD ntoskrnl.exe-7f1c0 while idling

I have been getting a BSOD in my newly installed system

and ive included the files in this post as you asked for before posting :)

I am running Win 7 x64 OEM i bought it together with the parts for my system which you can see in my signature. it is only nearly 4 weeks old, i did put the system together myself for the first time .

hopefully i can get some help here :)

Btw the OS is installed on my Corsair SSD.

My System SpecsSystem Spec
09 May 2012   #2

Windows Home premium 64bit

And i runned a memtest today also and My ram Passed The test :)
My System SpecsSystem Spec
09 May 2012   #3

Windows 7 Pro-x64

wininit.exe caused the check code. The problem may be your disk or corrupt drivers. Run sfc /verifyonly from an elevated command prompt (Run as Administrator) and report back any messages you receive.

A process or thread crucial to system operation has unexpectedly exited or been
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.

Here's a tutorial on sfc if you've never used it. Use Option 3 in the tut.
SFC /SCANNOW Command - System File Checker
My System SpecsSystem Spec

09 May 2012   #4

Windows Home premium 64bit

I have now runned the sfc /verifyonly and it came up good with no errors !
My System SpecsSystem Spec
09 May 2012   #5

Windows 7 Pro-x64

Download and install Crystal Disk Info from here: CrystalDiskInfo - Software - Crystal Dew World
Watch and read the options when installing. There may be extras that you don't want installed through OpenCandy. Pay attention to the default check boxes and uncheck any extras. !!!!

Run the program and select the disk that contains your system files. Then expand the window (click and drag the bottom) so that all of the S.M.A.R.T. info is shown. Take a snipit of the window and post it.

It should look something like this:
My System SpecsSystem Spec
10 May 2012   #6

Windows Home premium 64bit

Here is a screenie of the stuff you asked for :)
My System SpecsSystem Spec
10 May 2012   #7

Windows 7 Pro-x64

Nothing unusual there except for the three power losses. Did any of these occur around the BSOD? I think the best thing to do is accumulate a few more dumps to try and identify a pattern. It may help eliminate the shotgun approach to debugging. Your memory checks out and your system files check out. There's not much left but motherboard and power supply. A few more dumps might help to narrow the search. In the mean time, check to make sure you have the most current BIOS (v10.5) for your motherboard. It should be available from MSI at the link below.

MSI Global ? Mainboard - Z77A-GD65
My System SpecsSystem Spec
20 May 2012   #8

Windows Home premium 64bit
A couple more Dmp.s

I havent yet updated my bios due to the lack of knowledge of how to. and storage usb devices to do it with

so i just had some BSOD's i think it could be caused by my lack of bios updates
My System SpecsSystem Spec
22 May 2012   #9

Windows 7 Home Premium 64 Bit

The crashes could be related to your out of date BIOS, as you say. Since you are running an SSD, that is the first thing you should probably check. Disable Verifier prior to flashing the BIOS; Verifier can cause crashes during a BIOS flash and any interruption of the BIOS flash will leave your system unable to function.

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.

  • 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
26 May 2012   #10

Windows Home premium 64bit
have been testing

I have now runned numerous test

I have updated bios to newest bios, boot drive is newest firmware. i have run malware bytes, sea tools(long and short term test) etc, sfc /scannow, memtest(both memtest86+ and windows memory test) bot all test are passed, and still i get the occasional BSOD
My System SpecsSystem Spec

 BSOD ntoskrnl.exe-7f1c0 while idling

Thread Tools

Similar help and support threads
Thread Forum
bsod driver_power_state_failure ntoskrnl.exe+7f1c0
My wife's Sony Vaio (VPCEE41FD) laptop has been acting up over the last few nights. It would hang up on shutting down, taking sometimes over an hour+ Just tonight it decided to BSOD stating driver_power_state_failure ntoskrnl.exe+7f1c0 If I recall, I think this happened about a month ago as...
BSOD Help and Support
BSOD in ntoskrnl.exe+7f1c0 on new Laptop Win 7 64 bit
Hello, I'm having blue screen errors on my Laptop which is only a couple weeks old and otherwise running fine. The BSODs aren't that many, maybe once a week while using the computer daily. Once it apparently was caused by me plugging in my USB mouse. Already did a memtest and chkdsk without...
BSOD Help and Support
BSOD without reason? ntoskrnl.exe 7f1c0
My computer working always good most 1 bsod coming without reason? on a day i seeing not reason for this pc have not many load ram test with memtest working over 8 houres without problems here bsod logs anybody have idea?
BSOD Help and Support
new laptop, BSOD caused by ntoskrnl.exe+7f1c0?
Hello, i recently got a new HP Pavillion dv6-6c50us about a week ago. Intel Core i5-2450M 6GB DDR3 RAM (1 x 2GB, 1 x 4GB) 750GB 5400RPM Hard Drive - x86 (32-bit) or x64 ? - Windows Home Premium 64bit - the original installed OS on the system? - Yes
BSOD Help and Support
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...
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 07:59.
Twitter Facebook Google+