BSOD ntoskrnl.exe-7f1c0 while idling

natteulven33dk · May 9, 2012

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.

natteulven33dk · May 9, 2012

And i runned a memtest today also and My ram Passed The test

carwiz · May 9, 2012

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.

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
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.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S

natteulven33dk · May 9, 2012

I have now runned the sfc /verifyonly and it came up good with no errors !

carwiz · May 9, 2012

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:

natteulven33dk · May 10, 2012

Picture

Here is a screenie of the stuff you asked for

carwiz · May 10, 2012

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

natteulven33dk · May 20, 2012

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

writhziden · May 22, 2012

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 http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html (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 http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html 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 http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html 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 http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 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

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. :warn: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.

natteulven33dk · May 26, 2012

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

writhziden · May 26, 2012

Alright, let's check for driver conflicts.

An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. In Windows 7:
- Click the Start Menu
- Type verifier in Search programs and files (do not hit enter)
- Right click verifier and click Run as administrator
- Put a tick in Create custom settings (for code developers) and click next
- Put a tick in Select individual settings from a full list and click next
- Set up the individual settings as in the image and click next
  View attachment 213761
- Put a tick in Select driver names from a list
- Put a tick next to all non-Microsoft drivers.
- Click Finish.
- Restart your computer.
If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
verifier /reset
-> Restart your computer.

If we are unable to find a driver, you may need to replace the SSD with an HDD and see if you still have problems. It may be an incompatible piece of hardware is conflicting with your SSD, as well.

carwiz · May 27, 2012

It appears you're disk system is causing the error. Please run a check disk using this tutorial.
Use Option one and follow steps 1-5. Because this is your system disk, jump to number 11 to finish.

Also, be sure all your disk drive connections are tight including the power cable.

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error.

If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.

Arguments:
Arg1: fffff6fc500223e8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000007731d880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00447d08e, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

BUGCHECK_STR: 0xF4_IOERR
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The required data was not placed into memory because of an I/O error.

natteulven33dk · May 27, 2012

carwiz

have runned check disk at it came up with no errors at all :S so am now running verifier as writhziden above is saying, or at least i think i am, cant seem to see if it is running or not .

but have found my SSD's serial number so im rdy if i need to make an RMA at the company

writhziden · May 27, 2012

To determine whether you are running Verifier:

Open a command prompt via Start Menu -> All Programs -> Accessories -> Command Prompt
Type
verifier /query

You should get a list of drivers being verified if they were enabled.

natteulven33dk · May 27, 2012

it makes a list but does it save that list, cant possible get to read it hehe it goes FAST

writhziden · May 27, 2012

You're the second person to say that within the last 24 hours... Not sure what configuration you and the other person are running that causes that. Anyway, the fact that it makes a list means it is enabled. Otherwise, you would get a short message saying no drivers are currently verified.

natteulven33dk · May 27, 2012

okey

thx for taking time to answer my questions

and btw where will verifier put logs from crashes ? and new BSOD ?

writhziden · May 27, 2012

You're welcome.

The Verifier enabled crashes will be in the same place as before for the .dmp files. Just follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html again and we will analyze them.

Just thought of something else. Is your SSD set to turn off during idle? See http://www.sevenforums.com/tutorials/140592-hard-drive-turn-off-hard-disk-after-idle-never.html and see if setting it to never turn off helps. You may want to disable Verifier for the time being to test. And no, setting it to never is not bad for the SSD. It actually allows it to do its garbage collection.

natteulven33dk · May 27, 2012

i will try that but cant i choose which to never turn off ?? i have a SSD and a normal HDD ?

writhziden · May 27, 2012

I do not think there is a way to distinguish between the two. We should cross that bridge when we get to it, though. Let's see if this works, first.

BSOD ntoskrnl.exe-7f1c0 while idling

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer