Windows 7 CLFS.sys Blue Screen

Yesterday I installed Visual Studio 2013 which required a reboot. Immediately after rebooting the system I got a BSOD caused by clfs.sys with error 0x50 and the following message: PAGE_FAULT_IN_NON_PAGED_AREA. I tried LITERALLY everything I found online
(including related topics posted here) but none worked. At this point, I can't even boot to Windows. It immediately crashes on the loading logo.
So I gave up and decided to reinstall the OS. After inserting the bootable USB, I still get the same BSOD!!! I don't understand why this happens
when trying to install a clean version. This didn't make sense to me, so I used Bootable Partition Wizard and completely
wiped out and formatted my C: drive hoping it would at least let me reinstall Windows. Surprisingly that didn't help either. I still get a blue screen when booting into the installation disc.
I'm totally lost at this point. What is going on? How could this possibly happen when booting into the installation disc?? Do I have to do something with the master boot record? Any help would be greatly appreciated.

AM
Could be hardware, MBR/EUFI, a corrupt win 7 image, or many other things. So where are you now? Is there any bootible OS on the system? Have you tried booting into safe mode (F8)?
If you cannot boot you have a brick. If you are comfortable with it you may need to start pulling out hardware to see if you can it to boot in any manner, or perhaps take the HD to another computer, etc.
Should you ever get to where you can boot we need the DMP files to diagnose
We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded,
and what was responsible.
Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
If you have any questions about the procedure please ask
BCC 50 is usually a driver
Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced
Wanikiya and Dyami--Team Zigzag

Similar Messages

Atikmpag.sys blue screen

Hello there,so i got this atikmpag.sys blue screen appers in my laptop,i though i could fix it with a format ao i tried than,now not only it didnt got fixed but i cant run in safe mode anymore because windows have so install,any way to get rid of the blue screen?my laptop is G62-b90EV,
Thanks in advance
This question was solved.
View Solution.

@Telis13
Ok since you have managed to get into safe mode. You can try removing the the video driver and reinstalling the driver from the HP Support website.
HP G62-b90EV Notebook PC Drivers
Be sure to select the correct operating system for your notebook and download the updated driver. I am assuming that you will do this on another computer and transfer the driver to your computer using a flash drive or some other usb removable media.
After trying that then reboot the computer and see if the problem remains. IF it does then try the things from my previous post. If the system restore does not work for you, then I would recommend backing up the contents of your hard drive to another driver and then perform a a system recovery.
Performing an HP System Recovery (Windows 7)
Troubleshooting HP System Recovery Problems (Windows 7)
Malygris1
I work on behalf of HP
Please click Accept as Solution if you feel my post solved your issue, it will help others find the solution.
Click Kudos Thumbs Up on the right to say “Thanks” for helping!

IPod touch 4G causes windows 7 to blue screen when connecting to iTunes

Wife bought me a new iPod Touch 4G for Christmas. A few days ago it started to cause my Windows 7 (64bit) to blue screen randomly while connected or sometimes when I first connected it. Did a Windows re-install and crashes Windows each time I connect it. It is not the USB port as other devices work fine through all my USB ports. I do load various apps on the iPod several times a day. And it is also bluetooth'd to my wireless wifi switch (same network as my PC). ITunes program on PC is latest version. Anyone have a clue on this one?

Try here:
iPhone, iPad, or iPod touch: Windows displays a blue screen message or restarts when connecting your device

Anyone seeing a nwdelmdm.sys blue screen error connecting to a jetpack?

Anyone seeing a nwdelmdm.sys blue screen when connecting to a jetpack?

Jetpacks do not require any software unless you are referring to a USB connection. If so then your Jetpack USB drivers have become corrupted and should be reinstalled. Id assume NW in nwdelmdm.sys is referring to Novatel Wireless.
If you have any other USB modem connection software or drivers you might want to clean them up too.

Windows 7 Crash (Blue Screen) with Skype 6.18 on H...

Hi,
I think a lot of people are having the same problem with Skype 6.18 on HP Pavilion notebooks.
Windows 7 crashes during the auto-update or installation of 6.18
After about 3-4 hours of troubleshooting the Blue Screen / service exception error (in ks.sys) I discovered that it's caused by the HP HD Webcam [Fixed] driver (version is 6.0.1113.1 released 2012-11-20 (or 20-11-2012)).
The driver is written by Sonix and is unlikely to be updated. So you have the choice of going back to an older version of Skype or disabling the webcam / driver through Device Manager. As soon as you disable the driver / device Skype will install / start - but of course you won't be able to use video during Skype calls.
Hopefully Microsoft / Skype will fix the driver incompatibility in a future release.
Skype Support - the issue is with the HP / Sonix driver - file is snp2uvc.sys
There are similar issues reported with a previous version of the HP HD Webcam driver as well (SPUVCBv_x64.sys).
Please fix it. I'd like to use video in calls again!

The best working solution at this time is to download and install Skype 6.14 and disable updates. If you still get prompts to upgrade you can ignore them and the program should continue to function as it has not been retired as of yet. Hopefully there will be a resolution in a future Skype update or an updated driver from HP that might resolve the issue.
http://community.skype.com/t5/Windows-desktop-client/BSOD-on-startup-and-installation/m-p/3511645/hi...

Satellite A100 - sptd.sys blue screen error

Hello,
Hoping someone can be of help with this.
I have a Toshiba A100 with Windows XP Media Center Edition 2005.
When I try to boot up my computer, I get a message saying windows did not start successfully.
I am given the options of:
Safe Mode
Safe Mode with Networking
Safe Mode with Command Prompt
Last Known Good Configuration
Start Windows Normally
None of these options works. When I attempt Safe Mode, I get the following message:
multi(0)disk(0)rdisk(0)partition\Windows\system32. ...etc
This message repeats over and over again very fast, each time with a different .sys file at the end. Then, I get this message:
Press Esc to stop loading sptd.sys...
If I press escape, I get the following blue screen:
A problem has been detected and Windows has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: sptd.sys
The driver mistakenly marked a part of its image pagable instead of nonpagable.
I dont know what to do except for using the product recovery CDs and reformatting, but I cant afford to lose some of the data on my computer, and this would wipe it all.
Has anyone had experience with this? Any advice?
It would be much appreciated.

Hi
Seems the OS system or the partition, where the OS has been installed, is corrupt.
I have no idea why this happened but there are many different reasons for that
Anyway I think you have no other choice as to reinstall the OS using the recovery disk.
You would like to get access to the data on the HDD???
Well, you could remove the HDD from the notebook and could connect it as an external USB device to another computer. Then you should try to copy the data to another HDD.
That might help

Rthdaud.sys blue screens in boot camp

Hi all, have been playing around in boot camp (gaming for the most part) and twice now have, after a few hours of perfectly fine system running, been presented with a blue screen naming rthdaud.sys as the cause. As this is the realtek audio high-def driver, I assume it's part of the boot camp driver package and should be okay.
What would be the first thing to try? Should I reinstall the apple boot camp driver for this? Perhaps get the driver (updated version?) from realtek's website directly? Thanks in advance for any help.

Apple today introduced Boot Camp, new public-beta software for Mac OS X that lets users of Intel Macs boot directly into Microsoft Windows XP. While the move may contradict previous statements by Apple, the company said they still have no intention of fully supporting Windows on the Mac.
People who read this also read:
People Who Like This Also Like
Windows on Mac: What you need to know 21024159
WWDC: Microsoft kills Virtual PC for Mac 21015245
First Look: From the Lab: XP-on-Mac benchmarks 21024413
World Tech Update 21490391
TaskPaper 2.1 21486845
Will Apple's App Store change the desktop app market? 21484083
Recommendations by Loomia
After we released the Intel-based Macs we had a lot of customer requests asking if it’s possible to run Windows on those machines,” Brian Croll, Apple’s senior director of Software Product Marketing, told Macworld. “We decided we would help it along by creating Boot Camp.
The software, available today as a public preview version of a feature from the forthcoming Mac OS X Leopard, includes an assistant application to aid with drive partitioning and the installation of Windows drivers for Mac hardware.
mukesh
Camping-Camping

Igdkmd64.sys blue screen

How exactly do I trouble shoot what is causing this random blue screen igdkmd64.sys? Thanks!

Hi,
Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software or anti-virus services (buggy services).
The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case
some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).
To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that
a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
Microsoft - Help and Support
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see Microsoft Worldwide Home for regional support phone numbers.
http://www.microsoft.com/worldwide/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

NETIO.SYS blue screen

Hi,
I've a Windows Server 2008 SP2 Enterprise Edition member of a cluster, this node experiences a blue screen shortly after boot, I've inspected the memory.dmp file with windebug and this is the output:

5: kd> !analyze -v
*                        Bugcheck Analysis
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80001e87125
Debugging Details:
BUGCHECK_STR: 0x7f_8
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80001e651ee to fffff80001e65450
STACK_TEXT:
fffffa60`01cbaa68 fffff800`01e651ee : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffffa60`01cbaa70 fffff800`01e63a38 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`01cbabb0 fffff800`01e87125 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8
fffffa60`01cd6f70 fffff800`01e8769f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepMandatoryIntegrityCheck+0x15
fffffa60`01cd7010 fffff800`01e3817b : fffffa80`331e9350 fffffa80`30d567c8 00000000`00000001 00000000`00000000 : nt!SeAccessCheck+0xaf
fffffa60`01cd7100 fffffa60`00a0ac6e : 00000000`00000000 fffffa60`00a0b37b fffffa80`331c2de0 fffffa80`331dc010 : nt!SeAccessCheckFromState+0xf3
fffffa60`01cd7800 fffffa60`00a0b447 : 00000000`00000000 00000000`00000001 00000000`00000002 00000000`00001383 : NETIO!MatchValues+0x14e
fffffa60`01cd7880 fffffa60`00a0b4fb : fffffa80`31a54220 fffffa80`331d2590 00000000`00000000 fffffa80`31a54220 : NETIO!FilterMatch+0x77
fffffa60`01cd78c0 fffffa60`00a0c4e5 : 00000000`00000000 00000000`00000002 fffffa60`01cd7e30 fffffa60`01cd8270 : NETIO!IndexListClassify+0x4b
fffffa60`01cd7920 fffffa60`01278cd7 : 00000000`00000032 fffffa60`01cd7db0 00000000`00000000 fffffa80`32be2e40 : NETIO!KfdClassify+0xa35
fffffa60`01cd7c80 fffffa60`012792fe : fffffa60`01cd8790 00000000`00000003 fffffa60`0132bbc2 fffffa80`30c79320 : tcpip!WfpAleClassify+0x47
fffffa60`01cd7cc0 fffffa60`012799dc : 00000000`00000001 00000000`00000000 fffffa80`32b90080 fffffa80`30c79320 : tcpip!WfpAlepAuthorizeSend+0x5ce
fffffa60`01cd8190 fffffa60`01278987 : 00000000`00000000 00000000`00000000 00000000`0000003a 00000000`00000000 : tcpip!WfpAleAuthorizeSend+0x2ac
fffffa60`01cd83d0 fffffa60`012706f8 : 00000000`00000000 00000000`0000003a fffffa80`32be2e40 00000000`00000000 : tcpip!WfpAleConnectAcceptIndicate+0xd7
fffffa60`01cd84c0 fffffa60`012716ae : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!ProcessALEForTransportPacket+0x538
fffffa60`01cd8680 fffffa60`01273574 : 00000000`00000000 fffffa60`011d292d fffffa80`32150087 fffffa80`32b90000 : tcpip!WfpProcessOutTransportStackIndication+0x30e
fffffa60`01cd8930 fffffa60`0127a826 : fffffa80`32be2e40 fffffa60`01221afa 00000000`00000000 fffffa80`32b87970 : tcpip!IppSendDatagramsCommon+0x494
fffffa60`01cd8d50 fffffa60`01221790 : 00000000`00000002 fffffa80`32b90080 fffffa80`32b90000 00000000`00000000 : tcpip!IppSendDatagrams+0x26
fffffa60`01cd8d90 fffffa60`01309b50 : 00000000`00000001 fffffa80`32b88d30 00000000`00000000 fffffa80`32b90080 : tcpip!IppSendDirect+0x110
fffffa60`01cd8ec0 fffffa60`0124d9fc : fffffa80`32b88d30 fffffa80`32b90080 fffffa80`32a46620 fffffa80`32b87870 : tcpip!Ipv6pSendNeighborSolicitation+0x130
fffffa60`01cd8f70 fffffa60`0124cf1c : fffffa80`32a46620 00060000`0d000000 00000000`00000000 00000000`00000000 : tcpip!IppSendNeighborSolicitation+0x8c
fffffa60`01cd8fe0 fffffa60`01270e25 : 00000000`00000000 fffffa80`32a46620 00000000`00000000 fffffa60`01cd9500 : tcpip!IppResolveNeighbor+0x1ec
fffffa60`01cd9040 fffffa60`012743f8 : 00000000`00000000 fffffa80`333779b0 00000000`00000001 fffffa60`01267165 : tcpip!IppDispatchSendPacketHelper+0x575
fffffa60`01cd9140 fffffa60`0127385a : 00000000`00000000 fffffa60`00000006 fffffa80`00000028 fffffa80`00000000 : tcpip!IppPacketizeDatagrams+0x2e8
fffffa60`01cd9270 fffffa60`0125b32e : fffffa60`01cd9b50 fffffa60`0126b82d 00000000`00000000 fffffa60`01cd9950 : tcpip!IppSendDatagramsCommon+0x77b
fffffa60`01cd9690 fffffa60`01323975 : 00000000`00000000 fffffa60`012651f2 00000000`00000020 fffffa80`0000000e : tcpip!IpNlpSendDatagrams+0x3e
fffffa60`01cd96d0 fffffa60`012b6afb : fffffa60`013453e8 fffffa80`32ab15f0 fffffa80`32ab1738 00000000`00000000 : tcpip!IppSlowSendDatagram+0x45
fffffa60`01cd97d0 fffffa60`0126c1f8 : fffffa80`32ab15f0 fffffa80`32b1b901 00000000`00000000 fffffa80`333778b0 : tcpip! ?? ::FNODOBFM::`string'+0x3e89b
fffffa60`01cd9b10 fffffa60`0127b8ab : fffffa80`32ab15f0 00000000`00000f0d 00000000`00000005 fffffa60`01260000 : tcpip!TcpTcbHeaderSend+0x428
fffffa60`01cd9ca0 fffffa60`01253aed : fffffa80`30cd0f00 fffffa80`00000005 fffffa60`01cd9ef0 fffffa80`30d3c270 : tcpip!TcpFlushDelay+0x20b
fffffa60`01cd9d60 fffffa60`01253b99 : 00000000`00000000 fffffa80`33224ab0 00000000`00000000 00000000`00000000 : tcpip!IppDeliverListToProtocol+0x4d
fffffa60`01cd9e20 fffffa60`012531bb : fffffa60`013466d0 fffffa80`32b90080 00000000`00000000 fffffa60`01cd9ee0 : tcpip!IppProcessDeliverList+0x59
fffffa60`01cd9e90 fffffa60`0125250c : 00000000`00000030 fffffa80`30d3c270 fffffa80`32b90080 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x22b
fffffa60`01cd9f80 fffffa60`01251af4 : fffffa80`32b88d30 00000000`00000000 fffffa80`32b85601 fffffa80`00000001 : tcpip!IpFlcReceivePackets+0x8dc
fffffa60`01cda180 fffffa60`01261d03 : fffffa80`32b85610 fffffa60`01cda2b8 fffffa80`32b85610 fffffa60`00970001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x264
fffffa60`01cda260 fffffa60`009a90bc : fffffa80`32b86010 fffffa80`339f1d30 fffffa60`01cda400 fffffa80`313071a0 : tcpip!FlReceiveNetBufferListChain+0xd3
fffffa60`01cda2b0 fffffa60`009718c9 : fffffa60`01cda410 00000000`00000000 fffffa80`32a0f010 00000000`00000001 : NDIS!ndisMIndicateNetBufferListsToOpen+0xac
fffffa60`01cda300 fffffa60`0080e5c4 : fffffa80`313071a0 fffffa60`01cda898 00000000`00000001 00000000`00000001 : NDIS!ndisMDispatchReceiveNetBufferLists+0x1d9
fffffa60`01cda780 fffffa60`009a98a6 : fffffa60`00000001 fffffa60`00000103 fffffa80`339f1d30 fffffa60`01cda8a0 : NDIS!ndisMTopReceiveNetBufferLists+0x24
fffffa60`01cda7c0 fffffa60`04c69905 : fffffa80`33782ac0 fffffa80`33a2c830 00000000`00000001 00000000`0000006a : NDIS!ndisMIndicatePacketsToNetBufferLists+0x106
fffffa60`01cda860 fffffa60`04c6f99f : fffffa80`32a10520 fffffa80`33a2c830 fffffa80`32a10520 fffffa80`338bfb10 : netft!MaReceivePacket+0x65
fffffa60`01cda890 fffffa60`04c707aa : 00000000`00000000 00000000`00000000 fffffa80`33911938 00000000`00000001 : netft!TaReceivePacket+0x143
fffffa60`01cda8d0 fffffa60`053490a8 : 00000000`00000000 fffffa80`33988530 fffffa80`33988501 00000000`00000001 : netft!NetftReceiveDatagramHandler+0x106
fffffa60`01cda910 fffffa60`01243ee4 : fffffa80`33826800 fffffa80`32d72620 fffffa80`32d72470 fffffa80`32d72620 : afd!WskProTLEVENTReceiveMessages+0xb8
fffffa60`01cda970 fffffa60`012439fb : fffffa80`30d30000 fffffa80`338268e0 fffffa60`00000000 fffffa80`32282aac : tcpip!UdpDeliverDatagrams+0x164
fffffa60`01cdaad0 fffffa60`01253aed : fffffa80`32a2b080 fffffa60`00a070c2 00000001`32a10002 fffffa80`30d3be80 : tcpip!UdpReceiveDatagrams+0x1bb
fffffa60`01cdaba0 fffffa60`01253b99 : 00000000`00000000 fffffa80`32a12680 00000000`00000000 fffffa60`00971abd : tcpip!IppDeliverListToProtocol+0x4d
fffffa60`01cdac60 fffffa60`012531bb : fffffa60`0134c050 fffffa60`0134c050 00000000`00000011 fffffa60`01cdad20 : tcpip!IppProcessDeliverList+0x59
fffffa60`01cdacd0 fffffa60`0125250c : fffffa80`30d02a80 00000000`00000020 fffffa80`32a2b080 fffffa80`30d3c000 : tcpip!IppReceiveHeaderBatch+0x22b
fffffa60`01cdadc0 fffffa60`01251af4 : fffffa80`32940420 00000000`00000000 fffffa80`32a12601 fffffa80`00000002 : tcpip!IpFlcReceivePackets+0x8dc
fffffa60`01cdafc0 fffffa60`01261d03 : fffffa80`32a12680 fffffa60`01cdb0f8 fffffa80`32a12680 fffffa60`00970000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x264
fffffa60`01cdb0a0 fffffa60`009a90bc : fffffa80`32a17aa0 fffffa80`32b11490 fffffa60`01cdb200 fffffa80`313bf1a0 : tcpip!FlReceiveNetBufferListChain+0xd3
fffffa60`01cdb0f0 fffffa60`009718c9 : fffffa60`01cdb250 00000000`00000000 fffffa80`32a12a50 00000000`00000001 : NDIS!ndisMIndicateNetBufferListsToOpen+0xac
fffffa60`01cdb140 fffffa60`008066f7 : fffffa80`313bf1a0 00000000`00000002 fffffa60`01cdb760 fffffa60`05205ce7 : NDIS!ndisMDispatchReceiveNetBufferLists+0x1d9
fffffa60`01cdb5c0 fffffa60`0520456b : fffffa60`00000000 00000000`00000000 fffffa60`01cdb648 00000000`00000000 : NDIS!NdisMIndicateReceiveNetBufferLists+0x67
fffffa60`01cdb600 fffffa60`052069c0 : 00000000`00000000 00000000`0000ffff fffffa60`00000000 fffffa60`00000001 : vmswitch!VmsMpNicPvtPacketForward+0x27b
fffffa60`01cdb6a0 fffffa60`0520499b : 00000000`00000000 fffffa60`01cdb900 fffffa80`336abbc0 fffffa60`01cdb910 : vmswitch!VmsRouterPvtRoutePackets+0x200
fffffa60`01cdb8a0 fffffa60`009a90bc : 00000000`00000002 fffffa60`01cdcc60 fffffa80`31562600 fffff800`01e92304 : vmswitch!VmsPtNicReceiveNetBufferLists+0x27b
fffffa60`01cdbae0 fffffa60`00971a5c : fffffa80`31562670 00000000`00000000 fffffa80`328c3a50 00000000`00000000 : NDIS!ndisMIndicateNetBufferListsToOpen+0xac
fffffa60`01cdbb30 fffffa60`008066f7 : fffffa80`312d11a0 fffffa80`336abbc0 fffffa80`00000000 fffffa80`32189000 : NDIS!ndisMDispatchReceiveNetBufferLists+0x36c
fffffa60`01cdbfb0 fffffa60`050e1750 : fffffa80`336abbc0 fffffa80`32189000 fffffa80`3386c03f 00000000`00000000 : NDIS!NdisMIndicateReceiveNetBufferLists+0x67
fffffa60`01cdbff0 fffffa60`050e1368 : 00000000`00000000 fffffa80`32194b08 fffffa80`3386c000 fffffa60`00000000 : basp+0x11750
fffffa60`01cdc570 fffffa60`009a90bc : fffffa80`3270ea00 fffffa80`3129a1a0 fffffa80`32b11490 fffffa80`3270eaa0 : basp+0x11368
fffffa60`01cdc5c0 fffffa60`00971a5c : fffffa80`3270eaa0 00000000`00000000 fffffa80`3258b4a0 00000000`00000000 : NDIS!ndisMIndicateNetBufferListsToOpen+0xac
fffffa60`01cdc610 fffffa60`008066f7 : fffffa80`3129a1a0 fffffa60`011da0cf fffffa60`01cdcbc0 fffffa80`30a90300 : NDIS!ndisMDispatchReceiveNetBufferLists+0x36c
fffffa60`01cdca90 fffffa60`011da3a8 : 00000000`00000000 fffffa80`32b11490 fffffa80`32157010 fffff800`01e5dc7f : NDIS!NdisMIndicateReceiveNetBufferLists+0x67
fffffa60`01cdcad0 fffffa60`011da451 : fffffa80`32157010 00000000`00000000 fffffa80`32157458 fffffa60`01cdcb90 : bxnd60a+0xb3a8
fffffa60`01cdcb20 fffffa60`0101059b : fffffa80`30acb010 fffffa80`32159000 00000000`00000000 00000000`00000000 : bxnd60a+0xb451
fffffa60`01cdcb70 fffffa60`01010826 : fffffa80`30acb010 fffffa60`01cdcc88 fffffa80`30c93d58 fffffa60`01283ba3 : bxvbda+0x659b
fffffa60`01cdcbd0 fffffa60`01016778 : fffffa80`30acb648 00000000`00000000 fffffa80`30ace698 00000000`00000005 : bxvbda+0x6826
fffffa60`01cdcc50 fffffa60`01016b49 : fffffa80`30acb010 00000000`00010000 00000000`00010000 fffffa80`30c93c28 : bxvbda+0xc778
fffffa60`01cdccb0 fffffa60`01016d63 : fffffa80`30acb010 00000000`00000000 00000000`00000000 00000001`23d6b39a : bxvbda+0xcb49
fffffa60`01cdcce0 fffff800`01e69667 : fffffa80`30acea58 fffffa60`01cb8580 00000000`01cafdb4 fffffa80`30c93c28 : bxvbda+0xcd63
fffffa60`01cdcd10 fffff800`01e698e2 : fffffa60`01016cb4 fffffa60`01cb5180 00000000`00000000 fffffa60`01cbed40 : nt!KiRetireDpcList+0x117
fffffa60`01cdcd80 fffff800`02036860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!MatchValues+14e
fffffa60`00a0ac6e 84c0            test    al,al
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: NETIO!MatchValues+14e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 49e02e06
FAILURE_BUCKET_ID: X64_0x7f_8_NETIO!MatchValues+14e
BUCKET_ID: X64_0x7f_8_NETIO!MatchValues+14e
Followup: MachineOwner
any ideas?

Hello,
it seems that my post from yesterday wasn't saved correctly. So I try it once again.
I have a SBS 2008 SP2 Server an the KB Stop error message in Windows Server 2008, in Windows Vista, or in Windows Vista SP1: "0x000000D1"
doesn't fit for me because of SP2.
This is the output of my crash dump:
0: kd> !analyze -v
*                        Bugcheck Analysis
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa60010833b4, address which referenced memory
Debugging Details:
USER_LCID_STR: DEU
OS_SKU: 9
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c88080
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
tcpip! ?? ::FNODOBFM::`string'+5824
fffffa60`010833b4 488b01          mov     rax,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80002b41550 -- (.trap 0xfffff80002b41550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800caa8010 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800caa8011 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa60010833b4 rsp=fffff80002b416e0 rbp=fffffa800647f870
r8=fffffa800caa8010 r9=00000000013430a0 r10=fffff80001bd5580
r11=fffffa8006250340 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
tcpip! ?? ::FNODOBFM::`string'+0x5824:
fffffa60`010833b4 488b01          mov     rax,qword ptr [rcx] ds:5870:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001abb22e to fffff80001abb490
STACK_TEXT:
fffff800`02b41408 fffff800`01abb22e : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`02b41410 fffff800`01aba10b : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`0647f870 : nt!KiBugCheckDispatch+0x6e
fffff800`02b41550 fffffa60`010833b4 : fffffa80`066539e0 00000000`00000001 fffffa80`06495870 fffffa60`206c644d : nt!KiPageFault+0x20b
fffff800`02b416e0 fffffa60`00a10f18 : fffffa80`0647f870 00000000`01147050 00000000`00000000 fffff800`01a2b151 : tcpip! ?? ::FNODOBFM::`string'+0x5824
fffff800`02b41730 fffffa60`00a0ea3d : 00000000`00000000 00000000`00000000 fffffa80`06c727d0 00000000`00000002 : NETIO!NetioDereferenceNetBufferList+0x78
fffff800`02b41760 fffffa60`0103ed96 : fffff800`02b41850 fffffa80`0b6a1d00 00000000`00000000 00000000`00000001 : NETIO!NetioDereferenceNetBufferListChain+0x28d
fffff800`02b41820 fffffa60`01029824 : fffffa80`06c727d0 fffffa80`0c551c30 fffffa80`05bd6010 fffffa80`05bd44e0 : tcpip!IppCompleteAndFreePacketList+0xb6
fffff800`02b41850 fffffa60`01031c70 : 00000000`00000000 fffffa80`05bd6010 fffffa80`05bd44e0 fffffa60`01147050 : tcpip!IppCleanupMfe+0x44
fffff800`02b41880 fffffa60`010772bd : fffffa80`05bd44e0 fffffa60`0114b558 fffff800`02b41928 fffffa80`05bd6010 : tcpip!IppDereferenceMfe+0x20
fffff800`02b418b0 fffffa60`0107713a : fffff800`02b41ad8 00000000`00000000 fffffa80`05bd6028 fffff800`02b41ad8 : tcpip!IppMfeSetTimeOut+0x10d
fffff800`02b419d0 fffffa60`010773ea : fffffa80`0a72c500 fffff800`02b41ad8 00000000`00000000 fffff800`02b41cd0 : tcpip!IppCompartmentSetTimeout+0x9a
fffff800`02b41a40 fffff800`01abf3fd : fffff800`00000002 fffff800`01bd4e80 fffff800`01bd4cf0 00000000`00000002 : tcpip!IppTimeout+0x5a
fffff800`02b41a70 fffff800`01abe818 : fffff800`02b41cd0 fffffa60`02e6a702 fffff800`02b41cc8 00000000`00000001 : nt!KiTimerListExpire+0x30d
fffff800`02b41ca0 fffff800`01abefaf : 002555b1`b0642875 00000000`00000000 00000000`00000001 fffff800`01bd7a80 : nt!KiTimerExpiration+0x1d8
fffff800`02b41d10 fffff800`01abf8d2 : fffff800`01bd4680 fffff800`01bd4680 00000000`00000000 fffff800`01bd9b80 : nt!KiRetireDpcList+0x1df
fffff800`02b41d80 fffff800`01c8c860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`02b41db0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!NetioDereferenceNetBufferList+78
fffffa60`00a10f18 4885ff          test    rdi,rdi
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: NETIO!NetioDereferenceNetBufferList+78
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 49e02e06
FAILURE_BUCKET_ID: X64_0xD1_NETIO!NetioDereferenceNetBufferList+78
BUCKET_ID: X64_0xD1_NETIO!NetioDereferenceNetBufferList+78
Followup: MachineOwner
Any idea what this NetioDereferenceNetBufferList+78
means?
Thanx for your help.
Regards
lukas

[VIA] Kmixer.sys Blue Screen

Hi There
I have been experiening the dreaded blue screen such as other people have reported while playing games. The windows diagnostics program states that the failure was caused by Kmixer.sys.
I have gone through the suggestions on line testing/replacing and removing items but still get a blue screen with the report pointing to kmixer.sys
I have installed all the latest drivers and have flashed the motherboard with the latest bios.
The system is
AMP 3000 XP (Not over clocked)
MSI KT6 Delta motherboard with onboard cmedia sound
1GB PC2700 DDR RAM (Tested for 6 house with memtest86 with no failures) Also tested 512 PC3200 on its own with the same blue screen.
500W power supply. Upgraded from 300. Same blue screen with both.
New nvidia 6600 GT graphics car replacing the old nvidia MX400 card. Still same problem
300GB sata drive.
2 x 80 GB ATA drives
NEC DVD burner (blue screen with disconnected)
DVD standard drive (blue screen with disconnected)
Modem. (blue screen with it in or out.)
Floppy. (blue screen with it in or out.)
Windows XP (Problem still apparent with clean boot)
Norton Internet security.
Any suggestions to the solution?
Thanks

Hello!
Thank you for the informative post! Exemplatory!
Kmixer.sys seems to have to do with audio files.
Could you try disconnecting and unscrewing all not necessary parts, but mobo and processor, system hard disk, one stick of memory, and a CD device on a different flat cable from the hard disk, and then reinstall Windows.
Yes, I know it sounds like a lot of hard (ware) work, but if the reinstall doesn't help, at least troubleshooting will be much easier afterwards.

Windows XP displaying Blue screen of death!

I just bought an iPod Classic last week and installed iTunes 8.1.1.10 and have had nothing but problems since day 1. The software *****, it ***** up my processor, freezes, and suddenly started crashing my system. i'm getting the BSoD and I am NOT on Vista. I am running XP Pro. Now I'm getting windows popping up saying that my computer can't find vital system files. This all started when I installed iTunes 8. PLEASE HELP! I backed up all of my important information onto an external hard drive because I am scared to lose my data because of this crashing. It seemed to start happening after i cleared my library out a few times because it was uploading 2 versions of some songs because my playlists were store in My Music. I moved the playlists and tried to resync my 3,000+ song library and my computer got the BSoD. I got one error the first time that said KernelStack_InpageError. So I rebooted, cleared my library, then set it to reload my music library into iTunes. Worked ok, then started to resync my iPod and it crashed again. It seems to keep happening when I try to sync a large number of songs at once, so I tried doing 1-2 letters of the alphabet at a time, which worked for a while, syncing 1-300 songs at once. Then my computer crashed for maybe the third or fourth time when syncing the S's. I'm sick and tired of this blue screen and my computer crashing and I don't want to be afraid of losing my data or my laptop. I'd really appreciate ANY help anyone can offer me.
Extra specs:
iPod Classic black
about 99/120GB free (nowhere near being full)
both iPod and iTunes running the most up-to-date software
If you need any other info, let me know
last few times I tried to sync, iTunes malfunctioned and had to close

I have a similar problem, except I can't even get to a command prompt or any sort of stopping point b/c my computer keeps restarting after it hits the BSOD. My usb-based keyboard can't stop the process either for some reason, so I can't get into the bios or the safe mode. I can't do squat except watch the blue screen over and over until I just unplug the **** thing and swear a lot. This all started happening right after the reboot following the install of iTunes8, so I gather this is the culprit (and, besides, a ton of folks out there seem to have the same problem). I don't even have an iPod or iPhone, so it's not that synching issue. If this is a way to get people to throw out their Windows PCs in frustration to buy Macs, then that's just a really malicious move. The only other way I see it is that this is another terrible deployment of an iTunes software update for windows, so what happened to reliable beta testing? Either way it ***** ***** *****. Can I just have my computer back please?!
Any tips on how to break the cycle when the keyboard doesn't function; and then how to resolve the BSOD issue after that? I miss my turntable.

Windows 7 Crashes (Blue Screen Of Death) As Soon As My iPhone4 Connects

Ok, so I have Windows 7 with the latest version of iTunes and the latest software version for my iPhone4, everything was working fine until just the other day, whenever I plug my iPhone into my computer, as soon as it makes that little noise when it connects, I get a blue screen of death.
That's about all I know...

I updated Windows drivers (it said I had three updates to download) but still no luck.
This is the error report I receve upon reboot:
Problem signature:
Problem Event Name:    BlueScreen
OS Version:    6.1.7601.2.1.0.768.3
Locale ID:    4105
Additional information about the problem:
BCCode:    1000007e
BCP1:    FFFFFFFFC0000005
BCP2:    FFFFF8800F4249F2
BCP3:    FFFFF88003292918
BCP4:    FFFFF88003292170
OS Version:    6_1_7601
Service Pack:    1_0
Product:    768_1
Files that help describe the problem:
C:\Windows\Minidump\011213-18985-01.dmp
C:\Users\Gumballthechewy\AppData\Local\Temp\WER-44444-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Windows 7 Ultimate Blue Screen of Death (BSOD)

Hello,
I have Windows 7 Ultimate and very recently I have started experiencing this BSOD with an automatic restart.
I took a photo of the BSOD but I'm not sure how to attach it to this post. I even downloaded that Nirsoft BlueScreenView program but it doesn't show up on there. Should I change some setting?
The message says:
STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF80002AC32C2, 0xFFFFFFFFFF880009A9230)
I ran the CheckDisk program and there were no errors. I ran MemTest86 (2 passes) and there were no errors with the memory. I have an NVidia GTX-295 that I downloaded drivers for and it was working fine until a couple of days ago.
I did however install my old ATi Radeon X1900XTX along with the other card and downloaded the drivers for that. It worked fine for a couple of days and then it crashed (BSOD) a couple of times. I have 2 monitors so I removed the ATi card (pulled it out) and deleted every single file related to ATi in the Program Files folder (forgot to "uninstall" the drivers before physically pulling out the card). Connected both monitors to my NVidia GPU and things were back to normal. A few days later, I got the BSOD while playing Call of Duty: Modern Warfare 2 (through Steam) and then it started happening when I was just surfing the Internet. Now it happens more often and it is extremely frustrating.
I spent several thousand dollars on a BRAND NEW custom SYSTEM BUILD and I am now faced with this BSOD problem.
PLEASE HELP ME!!
I have an ASUS P6T7 WS Supercomputer Mobo and the release version of the BIOS; have not updated it because I was told I could ruin the whole computer if I screwed something up.
Have 2 SLC SSDs (G-Skill) for my OS drive in RAID-0. This is where Windows 7 Ultimate is installed.
My mouse driver (Logitech MX20 Laser cordless) is from 2006 but I am unable to update it even through the Logitech website. Not sure why.
Every other driver is up to date (or it says 'best version currently installed').
PLEASE HELP!!
Thanks in advance.

Hello Suzerain,
First of all, upgrade BIOS to the latest version, remove all unnecessary hardware devices from the computer and try entering Windows safe mode to test whether it is a third-party software/hardware compatibility issue. If so, please download and run Windows 7 Upgrade Advisor to check the reason for the issue. If the issue is caused by some incompatible driver, you might go to Device Manager, right click your hardware device in the list and select Update Driver Software; then click Search automatically for updated driver software.
If you still get the BSOD error after installing the latest driver, please understand that Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services).
The system goes to a blue screen because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).
To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for regional support phone numbers.
I hope the problem will be resolved soon. Thanks!
Andy

Windows 7 (64) Blue Screen of Death at Start up after installing iTunes 10

I just got a brand new computer a week ago and decided to install iTunes 10 this evening. The install finished successfully and a message prompted me to restart to complete the installation. So I did. Now my machine will not boot. Each time it does, I get a blue screen of death. Attempting to restore the system fails.
I was able to start Windows in Safe Mode once but I wasn't able to uninstall programs while in safe mode so I couldn't remove itunes 10. And now I can no longer start my machine in Safe Mode.
Has anyone else experienced this? Any ideas to solve it?
Message was edited by: BrianCoker

Windows 7 64 bit core i7
BSOD while updating to iTunes 10 with suspended installation of Apple Mobile Device Support. Network drivers no longer working as a result. Attempted fix by downloading from a different machine and competing install via files transferred over on flash drive. No dice. Attempted removal of iTunes, QuickTime, Apple Mobile Device Support, Apple Application Support, Apple Software Update to see if this would fix. Followed this up with a restart. This seems to have improved matters as system is starting up faster. No dice. Try reinstall network drivers from Sony ViaoCare disk. Installed and restarted. No dice. Next, try Widows 7 Network and Sharing diagnostics. No dice. Next try manual removal & reinstall of network driver using Device Manager, restart. Can't seem to re-install Network Controller. Still trying to solve this.

Windows 8.1 Blue Screen of Death "Critical process died" after Windows update

Hey there, my Envy laptop has the "Critical Process Died" blue screen of death error after doing 3 things today:
1. A BIOS update through HP Support Assistant.
2. An x64 windows process update (optional) through the Control Panel.
3. An NVIDIA update.
What can I do to fix this error? I'm okay with a complete system wipe. Please help.
*Windows 8.1 64bit

The only option that worked for me was to "reset" my PC, as in a complete wipe. it's working properly again, when I read reviews of windows 8.1 I didn't really believe the people who said stay away from it, but since I've had more problems than I'd wish to, I'm too afraid to go back to it. Thanks anyways guys.

Windows 7 CLFS.sys Blue Screen

Similar Messages

Maybe you are looking for