Windows 7: BSOD error code Help NTOSKRNL.EXE AND NCIP.SYS

Hello, i'm new to this and my computers being having some problems

There seems to be a BSOD problem on my new cpu, its being happening for a while now but i have been ignoring it because of how it only happens when i boot the computer up the first time, it loads, lets me login in and usually after about 5 minutes or so blue screens on me.

i have updated ALL drivers, even going back to the default ones and still having these problems. i've ran all of the tests i could do to try to resolve this with my limited knowlegde of solving these bugs.

i will try to attach the .dmp files and if their not here please tell me how to do so....
also i have Norton V5 and was wondering if i went to security essentials would that help?

CPU: Intel i7 2600k
RAM: 4x 4gb 1333MhZ
PSU: 850watts Generic Brand
Motherboard: Asus Z68 Pro 3 Gen 3
Graphics Card: Asus Twin Frozer GTX 560
HardDrive: Western Digital 1TB

thanks, bryce

here are the .dmp files thanks

Just a forewarning, a generic brand PSU is never a good idea. They are built with very unreliable parts and have a very short life span or are commonly bad immediately on arrival. When you purchase a PSU, you are not purchasing for performance but rather reliability, and the more money you spend towards a better brand and model, the less your worries will be. A bad PSU has the propensity to cause malfunctioning and even permanent damage to the rest of your PC hardware, so it is not a risk that anyone should be willing to take.

The crashdumps are inconclusive because there's a pretty wide pattern they're displaying, which means something (hardware or software) is on the loose. To make sure this isn't software, use Driver Verifier as instructed. Make sure to read the instructions in their entirety. In addition to what's instructed about which checks to select, also do not select Force Pending I/O Requests and IRP Logging. Make sure to restart the PC immediately after everything is set up. Provide any new crashdumps from any BSODs that may occur after DV is on.

thanks for the information, im going to try it when i get some spare time and post the info up and the power supply isnt a generic one, its just me being to lazy to open the case as its hidden awau behind many tangled cables

so i went through doing what the thread said, and it gave me a bsod for the non microsoft programs, but as also said i didnt get any information on what caused it as the minidump file is unfindable. what i did manage to although was run the verifier and check some windows drivers that bluescreen viewer had highlighted as being problematic, then i tested the ntosknrl.exe and that gave me a blue screen upon start up and gave me a minidump file, then restored and tested the wdf01000.sys and that gave me bsod upon login which i then restored to find no new dumpfiles from it.

hope that one helped in some way or it time to start removing programs or starting them up to see if they cause problems, starting with norton?

It is not advisable to run the tests on Windows drivers as it can frequently cause false positives.

The one crashdump you provided is most likely just that. It looks like it's that a driver was in violation of an IRP STATUS_PENDING check. I believe this is caused by selecting the Force Pending I/O Requests check. Is this true? Remember, do not select that check, nor Low Resource Sim, nor IRP Logging in your list of DV checks.

If you still wanna go after this, it blames your Daemon Tools drive emulation driver (dtsoftbus01.sys). It's dated from January so find and update. You may even need to end up uninstalling it and switching to another solution for your drive emulation needs, as Daemon Tools has been known to cause driver conflicts and eventually BSODs for a number of people. Though honestly, this may very well be a false positive and not the cause of your crashes.

Given that minidumps are not being produced from the 'legit' bluescreen crashes, this most likely means a disk I/O issue of some sort or the driver was loaded very early during Windows startup. I recommend some hardware tests just to get them out of the way, though starting with Seatools preferably since this seems more conducive of drive problems.


RAM: Memtest86+ - 7+ passes
CPU: Prime95 - Torture Test; Large FFTs; overnight (9+ hours)
GPU: MemtestCL - Run twice (if any of the tests work on your GPU; ATI cards will need to install the ATI APP SDK as it requires OpenCL)
Drives: Seatools - All basic tests aside from the Fix all or the advanced ones.

All of these (excluding MemtestCL) are included in the UBCD if you prefer a Live CD environment (which is the best environment to test hardware on). Note that Prime95 currently does not work on the UBCD. Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load.

okay i'll do that also, one other i did was test a few programs drivers individually through the driver vertifier method and got bs out of norton, so thats now gone and replaced with ms security essentials and seems to run a bit smoother. it cames up with some bs error code of fneturpx.sys or something like that

fneturpx.sys is the FNet Turbo HDD USB driver, which also is on Asus brands as part of their "XFastUsb" package. I recommend you go and uninstall all software associated with your motherboard. Motherboard software is extremely buggy and is very prone to creating BSODs that report unusual hardware behavior, when it's really just the software going foul. You will want to uninstall all of it, and leave only device drivers that are absolutely necessary for the use of your motherboard components. USB is hosted by a standard driver made by Microsoft and does not need - nor is it recommended to use - any special drivers for it. For Asus boards, their XFast stuff is also not good, so make sure to get rid of anything associated with it.

it's all ways been buggy with the xfast stuff on there, thanks for telling me about that, i know that normally software like that slows it down but never thought of removing it because its made by them for my motherboard.

hey im back, the only thing i have been unable to test to date is the ram, everything else has come back 100% clean and working. attached with this will be the new bsod errors im getting after removing all xfast and lucid virtu, along with the 30 min idle and 30 under load while torture testing, if you want me to add a 30 min of me putting the graphics card under stress ill just play crysis2 on max with dx11 tesselation setup.
other wise in the mean time ill try to find something that can burn .iso files, some bsod errors may be before removing xfast stuff, but after that all i got where ntosknrl.exe errors and ncipis.sys or some thing like that