So fired up my PC today in excitement, but got a bluescreen instead. Got an error I haven't heard of before, KMODE_EXCEPTION_NOT_HANDLED. BlueScreenView blames it on a NETIO.sys. Microsoft lists this as a common problem though, so should I be worried? And if so, what should I do?
Other than that, my system hasn't bluescreened since then, so that's nice.
Edit: added dump.
Last edited by AutSamurai; 30 Jan 2014 at 20:24.
Looks like it's more than just a GPU issue.
Just got another BSOD. MEMORY_MANAGEMENT. Looking in Windbg, it points to a "tcpip.sys" driver. According to the reference table, it's network related.
So, uh, what do? Does this have anything to do with that NETIO issue i had earlier? Does it have anything to do with my wireless card? What do you guys think?
I don't know about the other members, but I can no longer help you if you insist on only sending an incomplete SF_Diagnostic with only the .dmp in it.
2. Download and run the SF_Diagnostic_Tool.exe file to use the Grab All button as instructed in the tutorial link below.
Blue Screen of Death (BSOD) Posting Instructions
Also, chkdsk just automatically ran when i restarted my computer, fixed some errors, and recovered a lot of "orphan files."
That's okay, what you don't realize, and I should have mentioned in my last post.
That at least for me and possibly other members of the BSOD team; is after helping with the BSOD .dmps I delete them to clear up the clutter on my desktop. If I'm helping you and two other members it can get junked up real quick with tens if not hundreds of MB sitting in the recycle bin, I'll even do a re-boot to clear out my memory and temp file / folders when I walk away from my machine.
Thank you for the full report, I did find something in the MISINFO32 report that I'll touch on later.
The chkdsk run can usually be attributed to bad sectors on the HDD, due mostly to unclean shutdowns or BSOD's. It requires something to have actually corrupted critical data such as overclocking, ram malfunction, or as noted earlier, hard drive bad sectors before it fails and starts losing data. If the OS picks up on them it can run automatically depending on settings.
The MISINFO report has two drivers that are missing:
You should look into them, the ethernet one could be part of the tcpip problem.Code:Ethernet Controller PCI\VEN_8086&DEV_153B&SUBSYS_153B1849&REV_04\3&11583659&0&C8 The drivers for this device are not installed. Universal Serial Bus (USB) Controller PCI\VEN_8086&DEV_8C31&SUBSYS_8C311849&REV_04\3&11583659&0&A0 The drivers for this device are not installed.
I'm still leaning towards the memory sticks as being involved here as mentioned earlier about the chkdsk, at the least, make sure their seated properly, you could even switch 'em around.
Okay, I downloaded and installed the USB and Ethernet drivers.
However, I got another bluescreen, which will, as always, be available for download below. WinDbg blames it on a cdd.dll, which from not much reading, points to driver or memory issues, like the rest of my problems. I'm going to try running memtest with single sticks tonight and tomorrow, and if I can't get any errors to come up, then it's a fresh install of Windows 7.
Feel free to take a look at the dump though.
And just my luck, the computer won't boot up without both sticks of ram. So unless I can get my hands on another 8 GB of ram, I'm basically out of luck.
That cdd.dll relates to: STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes:
Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
See expanded version of causes and resolving the problem at the above link, below all the KB articles, the not just ram part could mean you have a bad video card. Have you tried a Video Card - Stress Test with Furmark?
Also:
A few things come to mind and changes my train of thought:A vulnerability in Microsoft Canonical Display Driver (cdd.dll) caused by improper parsing of information copied from user mode to kernel mode, could be exploited to execute arbitrary code remotely and gain system access.
While memory randomization makes it unlikely for successful code execution, an attacker could instead cause the system to stop responding and automatically restart before successfully exploits this vulnerability.
Source: Microsoft Canonical Display Driver (cdd.dll) Vulnerability
Are you sure your OS is up to date, including MSE?
- I'd re-run Windows Updates just to make sure.
Are you sure your OS is malware free?
- Is the mbam you list just an on-demand scanner?
- Do you have MSE's real-time protection turned on?
- Do you run the Windows Malicious Software Removal Tool every month?
- You could run either Windows Defender Offline or Microsoft Safety Scanner but Defender offline requires a d/l'd from a known virus free machine, the Security Scanner doesn't.
You could try a creating a new user account and logging in with it to see if it will make a difference.
If you need both sticks okay, have you tried swapping those sticks to different slots?
How are you doing with the video card drivers, do you feel that has settled down?
So of course, I got a blue screen. That was the only one today though, and it wasn't on startup, so i guess that's nice.
Anyways, I was running memtest last night for another 9 passes with no errors.
Since then, I've downloaded all the Windows Updates that wren't useless, like Bing crap, switched the slots of my RAM, ran a HDD diagnostic with Western Digital's tool (which returned no errors), and ran FurMark for about an hour with no artifacts. Hm.
Anyways, dump below.
Quote