Windows 7: Various BSOD - 0x0000124 - 0x000000c5 etc...

Sunner · 02 Mar 2012

Hi guys!

Been here some times while i was searching solutions on google. And i thought it was my time after seen you guys helping each other like pros.
Im a swede so my english can be a bit wrong, i hope not!
Anyways..

It started a year ago when i bought my computer. It came damaged.. My front was crackled, the CPU-fan was on the edge towards the ram and the thing my HDD was in was a bit bent.

I did send it back and i guess they just straighted up the parts and then it was sent back to me.

So i was playing BFBC2 back then and yeah.. Got a bluescreen right away (20 minutes), happened a few times and then i just stopped played the game.

But after a while i was getting bluescreens in CS too. And then when i was rendering movies and some days ago i got some other ones when i didn't even use the computer extremly. Today i got two...

So im wondering what the hell is wrong.. Software? Hardware?

Thanks alot in advance!

*The .rar is called Minidumpfiler wich means minidump-files in swedish*

EDIT:
Forgot my hardware...
Intel Core i7 950, 3.06GHz
Asus P6T Deluxe V2
Corsair 6GB (3KIT) DDR3 1600MHz/CL9/1.65V/XMS3
1TB Western Digital Caviar Black 64MB SATA III
Gigabyte GeForce GTX 570 1280MB
Samsung SH-S223C 22X DL Svart
Cooler Master Hyper 212 Plus
Corsair HX 650W 80+

My Windows 7 is OEM.

Oh, and if you wanna know something, just ask!

JMH · 02 Mar 2012

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

Quote:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress

Some generic advice.

If you are overclocking STOP. Return to the default settings at least for now.
If you are running a RAID update its driver.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try

Sunner · 03 Mar 2012

Quote: Originally Posted by JMH

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

Quote:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress

Some generic advice.

If you are overclocking STOP. Return to the default settings at least for now.
If you are running a RAID update its driver.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try

Thanks for your answer. What means with overclocking STOP? What should i do?
I don't use RAID (i think..)

Now i did get another bluescreen

BAD_POOL_CALLER
0x000000c2

I attatch the file.

writhziden · 03 Mar 2012

Overclocking means setting hardware to run faster than it is intended to run. If you did not do so intentionally, you may have software that is doing so without your knowledge. If you do, your crash reports will indicate the software.

Possible out of date drivers:

Code:

yk62x64	fffff880`04699000	fffff880`046fc000	Mon Feb 23 08:02:27 2009 (49a2ba83)	0006049b		yk62x64.sys

yk62x64.sys
Update the above driver. I did not see any automated overclocking drivers installed, so you should be fine there.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Sunner\030312-111509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e00000 PsLoadedModuleList = 0xfffff800`0303de70
Debug session time: Sat Mar  3 03:14:23.093 2012 (UTC - 7:00)
System Uptime: 0 days 16:44:38.123
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, 9060001, fffffa80088ff1e0}

GetPointerFromAddress: unable to read from fffff800030a80e0
Probably caused by : ntkrnlmp.exe ( nt!IopDeleteFile+239 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000009060001, Memory contents of the pool block
Arg4: fffffa80088ff1e0, Address of the block of pool being deallocated

Debugging Details:
------------------


POOL_ADDRESS:  fffffa80088ff1e0 

FREED_POOL_TAG:  FOCX

BUGCHECK_STR:  0xc2_7_FOCX

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fa360e to fffff80002e705c0

STACK_TEXT:  
fffff880`035d2a18 fffff800`02fa360e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`09060001 : nt!KeBugCheckEx
fffff880`035d2a20 fffff800`03183729 : fffffa80`08238e20 fffffa80`0551fde0 fffffa80`4346744e fffffa80`08238e20 : nt!ExDeferredFreePool+0x11eb
fffff880`035d2ad0 fffff800`02e75754 : fffffa80`088ff1e0 00000000`00000000 fffffa80`0551fde0 00000000`00000000 : nt!IopDeleteFile+0x239
fffff880`035d2b60 fffff800`0315e325 : 00000000`00000000 00000000`000800a1 fffffa80`0be71010 fffffa80`000800a1 : nt!ObfDereferenceObject+0xd4
fffff880`035d2bc0 fffff800`02f97deb : fffffa80`0be71018 00000000`00000001 00000000`00000000 52375237`00000001 : nt!MiSegmentDelete+0xa1
fffff880`035d2c00 fffff800`02f9845d : 00000000`00000000 00000000`00000080 fffffa80`05506040 7c467c46`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`035d2cc0 fffff800`031106fa : f118f118`07d707d7 3ff53ff5`1ebc1ebc 87e187e1`22252225 597b597b`f984f984 : nt!MiDereferenceSegmentThread+0x10d
fffff880`035d2d40 fffff800`02e4eb46 : fffff880`009b2180 fffffa80`05537510 fffff880`009bd0c0 597b597b`f984f984 : nt!PspSystemThreadStartup+0x5a
fffff880`035d2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!IopDeleteFile+239
fffff800`03183729 e944ffffff      jmp     nt!IopDeleteFile+0x182 (fffff800`03183672)

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!IopDeleteFile+239

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0xc2_7_FOCX_nt!IopDeleteFile+239

BUCKET_ID:  X64_0xc2_7_FOCX_nt!IopDeleteFile+239

Followup: MachineOwner
---------

This crash usually points to an underlying driver problem. Proceed through the steps given for the STOP 0x124 that JMH gave the link for in her post.

After you have finished with the steps in the STOP 0x124 link, test by doing your normal routine to see if the system is more stable. If you continue to have crashes, upload any new crash reports, and run Driver Verifier to find any driver conflicts. 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. Run Driver Verifier

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 System Restore 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.

Additionally, I notice you do not have Service Pack 1 installed. Make sure you install all Windows updates. Alternatively, you can install Service Pack 1 with the subsequent steps.

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site

Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH

Sunner · 14 Mar 2012

Hi again guys.

Since i was here last time i have noticed some things.
I did remove my USB-drives from my computer which was mounted with TrueCrypt.
The week went on fine, no bluescreens, but suddenly i got one who pointed at yk62x64.sys which writhziden said was out of date.
Two days passed by and i got another who was basically the same.

Then this morning i got one who said something about Chrome.exe and eamonm.sys and i did see this link:
Bsod Bad_pool_Caller - TechSpot OpenBoards

I thought this sounded like my problem so i have just removed NOD 32 and did installed Microsoft Security Essentials.

So i hope this was the mean little devil, but you'll never know.. I will see what's happening. I don't wanna plug in my disks already though.. Who knows if a fast bluescreen will result in mashed up files etc...

My 0x00000124 on the other hand only happens when i play games. I've opened my side panel and my computers other side isn't very warm now. Nothing there since i've removed it in other words.. I think i should insert some more fans.

So, do you think NOD32 could trigger iaStor.sys and this yk62x64.sys file in any way? Is there any natural explanation if NOD32 is the cause?

EDIT: I remember i've had something like this with zonealarm one time some years ago now when i did face this..

writhziden · 14 Mar 2012

Antivirus software monitors both network and disk activity, so it would not be that surprising for it to cause the crashes. I will mention that ESET software is trusted almost as much as MSE for not causing crashes unless it is out of date. I suspect something else may be at work, but only time will tell if installing MSE results in stability.

Is your Marvell Yukon networking driver now up to date?

Sunner · 15 Mar 2012

Hi again! Got one this night again

This time it was iaStor.sys again (i did attach it).

How do i update the driver in the best way?
Should i get this Intel driver also?
What does causes my bluescreens do you think? :/

Sunner · 15 Mar 2012

Right! I also got one which pointed at NETIO.SYS some day ago.
I attach it.

writhziden · 15 Mar 2012

Code:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Sunner\031512-23181-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03063670
Debug session time: Wed Mar 14 19:50:29.387 2012 (UTC - 6:00)
System Uptime: 0 days 3:15:20.324
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {8, 2, 1, fffff80002fc9617}

Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+25fd8 )

Followup: MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80002fc9617, address which referenced memory

Debugging Details:
------------------


BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExAllocatePoolWithTag+537
fffff800`02fc9617 48895808        mov     qword ptr [rax+8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  rundll32.exe

TRAP_FRAME:  fffff880079ba080 -- (.trap 0xfffff880079ba080)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8009a8cde0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fc9617 rsp=fffff880079ba210 rbp=0000000000001000
 r8=0000000000000000  r9=fffff800030254e0 r10=fffff80003025348
r11=0000fffffffff000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExAllocatePoolWithTag+0x537:
fffff800`02fc9617 48895808        mov     qword ptr [rax+8],rbx ds:0008:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e9a1e9 to fffff80002e9ac40

STACK_TEXT:  
fffff880`079b9f38 fffff800`02e9a1e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`079b9f40 fffff800`02e98e60 : 00000000`0000b000 00000001`4005007f fffff880`0328c8e4 fffff800`030254e0 : nt!KiBugCheckDispatch+0x69
fffff880`079ba080 fffff800`02fc9617 : 00000000`0000bb20 00000000`00000020 fffff800`0304af40 00000000`00010000 : nt!KiPageFault+0x260
fffff880`079ba210 fffff880`01280fd8 : fffffa80`00000000 fffffa80`063b1a40 fffffa80`05d7cec0 00000000`00000000 : nt!ExAllocatePoolWithTag+0x537
fffff880`079ba300 fffffa80`00000000 : fffffa80`063b1a40 fffffa80`05d7cec0 00000000`00000000 fffffa80`00000001 : iaStor+0x25fd8
fffff880`079ba308 fffffa80`063b1a40 : fffffa80`05d7cec0 00000000`00000000 fffffa80`00000001 fffffa80`0a467e10 : 0xfffffa80`00000000
fffff880`079ba310 fffffa80`05d7cec0 : 00000000`00000000 fffffa80`00000001 fffffa80`0a467e10 fffffa80`00000000 : 0xfffffa80`063b1a40
fffff880`079ba318 00000000`00000000 : fffffa80`00000001 fffffa80`0a467e10 fffffa80`00000000 fffffa80`00000020 : 0xfffffa80`05d7cec0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+25fd8
fffff880`01280fd8 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  iaStor+25fd8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac65b7a

FAILURE_BUCKET_ID:  X64_0xC5_2_iaStor+25fd8

BUCKET_ID:  X64_0xC5_2_iaStor+25fd8

Followup: MachineOwner
---------

Loading Dump File [D:\Kingston\BSODDmpFiles\Sunner\031112-22682-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03053670
Debug session time: Sat Mar 10 19:57:22.333 2012 (UTC - 6:00)
System Uptime: 6 days 16:56:47.967
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
..............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {8, 2, 1, fffff80002fb9617}

Probably caused by : NETIO.SYS ( NETIO!WfpAllocFromNPagedLookasideList+47 )

Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80002fb9617, address which referenced memory

Debugging Details:
------------------


BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExAllocatePoolWithTag+537
fffff800`02fb9617 48895808        mov     qword ptr [rax+8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

TRAP_FRAME:  fffff880032ae7e0 -- (.trap 0xfffff880032ae7e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80093caa20
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fb9617 rsp=fffff880032ae970 rbp=0000000000001000
 r8=0000000000000000  r9=fffff800030154e0 r10=fffff80003015348
r11=fffff880032aed30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExAllocatePoolWithTag+0x537:
fffff800`02fb9617 48895808        mov     qword ptr [rax+8],rbx ds:e928:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8a1e9 to fffff80002e8ac40

STACK_TEXT:  
fffff880`032ae698 fffff800`02e8a1e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`032ae6a0 fffff800`02e88e60 : fffff880`032ae818 fffff880`032ae810 00020000`00020001 fffff800`030154e0 : nt!KiBugCheckDispatch+0x69
fffff880`032ae7e0 fffff800`02fb9617 : 00000000`00000001 fffff880`032aed00 00000000`00000001 fffff880`0100afa8 : nt!KiPageFault+0x260
fffff880`032ae970 fffff880`0100aa77 : fffffa80`00000000 fffff880`032aead0 fffff880`032aebd8 00000000`00000000 : nt!ExAllocatePoolWithTag+0x537
fffff880`032aea60 fffff880`01005646 : 00000000`00000000 fffffa80`0584fee0 fffff880`032aebd8 fffffa80`0ae6ddd0 : NETIO!WfpAllocFromNPagedLookasideList+0x47
fffff880`032aea90 fffff880`0100b11d : fffffa80`00000000 fffffa80`0b2070e0 fffffa80`0a471420 fffffa80`094e1a96 : NETIO!InsertFilterToMatchBuf+0xe6
fffff880`032aead0 fffff880`0100a94a : 5a22fa8e`00000001 00000000`00000000 00000000`00000000 fffffa80`0584fee0 : NETIO!IndexListEnum+0xe3
fffff880`032aeb40 fffff880`0100acdb : fffff880`032aefe8 fffff880`032aee50 00000000`00020003 00000000`00000001 : NETIO!FeEnumLayer+0xaa
fffff880`032aeba0 fffff880`0100b71d : fffffa80`0914e8c0 fffffa80`057cb7b0 fffffa80`0a458080 00000000`0000002c : NETIO!KfdGetLayerActionFromEnumTemplate+0x8b
fffff880`032aec50 fffff880`018a6e77 : 00000000`00000000 00000000`00000015 fffff880`032aefe8 00000010`00000036 : NETIO!KfdCheckAndCacheAcceptBypass+0x2d
fffff880`032aec90 fffff880`018a45ed : 00000000`00000000 00000000`00000000 fffffa80`05c119e0 00000000`00000000 : tcpip!CheckAcceptBypass+0x377
fffff880`032aeef0 fffff880`018a36fc : 00000000`00000000 fffffa80`0000002c 00000000`00000000 fffffa80`09426c80 : tcpip!WfpAleAuthorizeReceive+0x17d
fffff880`032af1d0 fffff880`018d99de : 00000000`00000000 fffff880`032af6b8 fffff880`032af640 00000000`00000011 : tcpip!WfpAleConnectAcceptIndicate+0x29c
fffff880`032af2c0 fffff880`018da619 : 00000000`00000000 00000000`00000000 00000000`0000eb14 00000000`00000000 : tcpip!ProcessALEForTransportPacket+0x5fe
fffff880`032af530 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpProcessInTransportStackIndication+0x7c9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!WfpAllocFromNPagedLookasideList+47
fffff880`0100aa77 ebd5            jmp     NETIO!WfpAllocFromNPagedLookasideList+0x1e (fffff880`0100aa4e)

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NETIO!WfpAllocFromNPagedLookasideList+47

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381

FAILURE_BUCKET_ID:  X64_0xC5_2_NETIO!WfpAllocFromNPagedLookasideList+47

BUCKET_ID:  X64_0xC5_2_NETIO!WfpAllocFromNPagedLookasideList+47

Followup: MachineOwner
---------

Points to your Intel SATA AHCI controller being corrupted.
Your Marvell Yukon networking driver is still out of date. I suspect it is the cause of this crash.

Uninstall and re-install your Intel SATA AHCI Controller.

To fully re-install the driver, use the following steps.

Click Start Menu
Right Click My Computer/Computer
Click Manage
Click Device Manager from the list on the left
Expand IDE ATA/ATAPI Controllers
Right click the Intel SATA AHCI Controller
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer
Install the latest driver for the device once Windows starts.

Alternatively:

Login as an adminstrative user.
Click Start Menu
Click Control Panel
Click Hardware and Sound
Click Device Manager (the last link under Devices and Printers)
Expand IDE ATA/ATAPI Controllers
Right click the Intel SATA AHCI Controller
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer
Install the latest driver for the device once Windows starts.

Also, could you follow the http://www.sevenforums.com/crashes-d...tructions.html to provide us with the full crash logs, reports, and system information. I have no idea what network adapter you are using, and it could be contributing to the NETIO.SYS crash.

Sunner · 15 Mar 2012

Thanks again for your replys writhziden!

Can you give me a directly link to the drivers you want me to update? Im always nervous to get the wrong ones.
Im running Windows 7 - 64 bit OEM.

And you mean this driver:

?

How should i do with the Marvell Yukon?

It's this one here:

?

Another question about:
"8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK".

What should i do with the dialog box then? X in right corner? (I assume it's a "please restart your computer" box you mean? Then there is coming another?

I have no idea what network adapter you are using, and it could be contributing to the NETIO.SYS crash.
I have my integreated networkcard in my ASUS-motherboard if that's what you mean(?)

But yeah, directly links so i don't take wrong driver whould be very nice!

Thanks in advance.

Windows 7: Various BSOD - 0x0000124 - 0x000000c5 etc...

Various BSOD - 0x0000124 - 0x000000c5 etc... problems?