Printable View
Dear esteemed members of Antionline community,
Yet again I'm in dire need of your expertise to solve a crisis which Microsoft has caused maybe for world domination.
Whenever I run bittorrent, after few minutes my laptop crashes and shows blue screen saying blah blah! NETIO.SYS blah blah! I can't read all and then reboots.
I'm running Win 7 Professional.
Many thanks in advance for your help.
Does it only BSOD when loading bittorent?
What are the temperature's running at? download and run http://www.cpuid.com/softwares/hwmonitor.html
my google kingfu is saying this could be a temperature related issue.
Look in the system event log for the stop code. It is in the form of stop: 0x00000000. Then search on it in the MS Knowledgebase for causes, workarounds and fixes.
Automatic rebooting can be turned off in the computer properties dialog.
Hi,
I would also suggest SpeedFan, as it continually displays in the system tray at a size that us old folks can read :D
http://www.almico.com/speedfan.php
OK overheating can cause all sorts of problems, but you specifically mention NETIO.SYS which points to networking?
I appreciate that your bittorrent app is loading the system and could provoke a heat issue issue without being of itself to blame. However I am inclined to call drivers/resources/applications conflicts on this one.
If your stop code is 0xD1 (and the rest), then it is almost certainly a driver issue.
Are you running Norton (Symantec) or ZoneAlarm security products? They have been known to cause conflicts and crashes like this in certain circumstances.
If it is network/internet related there might be some sort of issue with your wireless/LAN/NIC drivers and Windows 7 or a security application?
I would suggest that you go to your Laptop manufacturer's site and make sure that you have the latest Windows 7 drivers for your model.
@HYBR|D : It BSODs after running bittorrent for some time. I checked the temperature to be 48 deg C just before BSOD.
@ua549 : The keywords of system event log is 0x8000000000000002. Please tell me what to do next.
Thanks
@nihil : Updated all drivers from Acer's website for my Aspire 5755 laptop. Problem persists. Please suggest. I'm just having Microsoft Security Essentials.
There are too many digits in the stop code.
It has a form factor of 0x followed by eight digits - 0x01234567.
The numbers in parentheses can be ignored for now.
This article and software will help you.
@ua549 : Whocrashed analysed as follows:-
46 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
mfenlfk.sys (McAfee NDIS Light Filter Driver, McAfee, Inc.)
I found that McAfee was there in installed programs list and immediately uninstalled it.
The problem is fixed. Thank you so much for your help.
Forever in your debt.
Regards
Oh Noes!
It crashed again...
Whocrashed reports:
On Wed 11/23/2011 3:30:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112311-14227-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001611B2D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Please advice what should I do next.
Hey ua549, that's a great link!.............. now I have a pile of toys to play with at the weekend :D I see that they are an Italian outfit, but I must admit that I had never even heard of them.
If the error is 0x80000002 then it is a weird one, as that is usually something you come across in the coding/development environment? or it used to be. I think that it can mean "Out Of Memory" or some sort of datatype mis-match.
Neither of those seemed to fit this situation..............anyways props to ua549 for suggesting the tool that solved the issue :D
Glad you have the issue resolved princesheril :)
Sorry that I wasn't of much help, but I did get quite close when I called drivers and security software............."two out of three ain't bad" :D
I would guess that the McAfee was a leftover of the bloatware trial versions of applications that are usually bundled with brand name computers these days...............I think that mine had Norton (for a few milliseconds :lildevil:)
Cheers
Dear nihil,
Apologies for undermining your super expertise. As my jubilation was short lived, my call for celebration has to wait for long.
This BSOD issue still persists and my sincere request for its solution still stands before you and all other Antionline members.
Please tell me if I could provide any other information to cure this problem.
Regards
Hi there princesheril,
Don't be too disappointed just yet, as you have made progress. The McAfee problem that Whocrashed reported earlier was real, this is a new issue. What I suspect was happening was that the McAfee driver was causing a crash before this one had a chance to.
Firstly, this doesn't look like a temperature related issue, as 48C isn't that hot for a laptop.
I am not familiar with their use of terminology, but I think that Whocrashed is saying that this isn't a physical hardware problem but one related to a software driver. I guess that could be a driver for hardware though.
First thing I would do is reboot into the BIOS and disable memory caching and shadowing. At lest that will give us a level playing field so to speak. :)
Then you should go into Control Panel and Device Manager and check through all your hardware items to see if they are reporting an IRQ conflict.
Would I be correct in thinking that this only happens when you are running bittorrent?
Incidentally, how are you connecting to your internet hub/router............. is it wireless?
Also, has this always happened when you have been using bittorrent. Probably not a terribly likely cause but I guess it wouldn't harm to reinstall the bittorrent software?
Please let us know how you get on :)
I much prefer using Microsoft Security Essentials than any other anti-virus software.
It is free. It is light weight and doesn't interfere with normal operations.
IMO McAfee and Norton cause more problems than what they solve.
Well, in theory that should be good, at least from a systems performance viewpoint, given that it comes from the OS providers themselves.Quote:
I much prefer using Microsoft Security Essentials than any other anti-virus software.
I have certainly fixed quite a few issues in the past few years by getting rid of Norton. In particular the expired "trial" versions that ship with a new computer. :)
In fact, I try to get rid of all expired application trials as they can only cause issues and are doing no good at all.
I forgot to mention to princesheril that it would be a good idea to check if he has any other trial software packages on his machine and uninstall those as well.
By the same token, I would look at what is starting up and running, and disable (set to manual start) anything that you don't really need.
The idea is to clear out as much as possible so it will be easier to find the culprit.
If this actually removes the problem then re-enable the startup options (if you want to) one by one, until you identify the culprit that way.
EDIT:
I have a sneaking suspicion that the problem might be with the driver for the NIC/Wireless card, so I would check that I have the latest one. this might well be separate from other drivers on the manufacturer's website?
I'll check for any trial/bloatware programs and revert.
I share similar suspicion with nihil. Under Network Adapters in Device Manager I have following 3 branches:
1. Atheros AR5B97 Wireless Network Adapter
2. Broadcom Netlink (TM) Gigabit Ethernet, and
3. Microsoft Virtual WiFi Miniport Adapter
I'll see updates for each on google and check if problem is fixed.
Hey princesheril,
Looks like someone's spawning a remote bind shell on you or a similar exploit that's coded poorly....do a full Malwarebytes scan and a full scan with Hitman Pro. Then from an elevated command prompt run - sfc /scannow to repair any compromised system files.
The fact that bitorrent triggers it tells me it's something naughty.....happy hunting
Actually, the more I think about this ("Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.") and the weird 0x80000002 error code is definitely a buffer overflow exploit, it's not hardware.......may wanna format the MBR too to kill the rootkit.....
Hi Wazz,
That's a thought that never occurred to me but it does fit the circumstances. I sort of associated the strange 0x8~ error with a coding problem, so badly written malware would fit that. :)
@ princesheril:
Your Atheros is an onboard wireless chipset (if it's like mine). The Broadcom is a standard 10/100/1000 cat5/RJ45 cable network connection, and I guess that the other one is for a wireless miniport adapter. If it's like the UK that is where I would plug in the Telco's "WiFi anywhere" adapter.
The updates for those should be included in the OEM's updates with the possible exception of the miniport; but that doesn't mean that they are :D
At this point I think that Wazz's suggestion of a "rat hunt" is going to be the most profitable.
I guess you will need to check your laptop documentation to find out about sfc /scannow, as Windows will normally ask you for a Windows installation CD, which OEMs don't ship these days. There will doubtless be some way to do it through their recovery partition and disks?
Good luck!
Apologies for my delay in writing, but I was waiting to see if BSOD returns. Miraculously it didn't and I can call a party now! :D
I did sfc scan, tested with Hitman Pro, deleted all suspicious files, and updated all drivers from their specific vendors websites. I really can't isolate which one of them did the trick. I'm glad my problem is fixed.
Loads of thanks to nihil, ua549 and Wazz. You guys are angels to me.
Cheers
Excellent!!! Glad you're all set.......and you are welcome, anytime my friend!!!
We do not allow images to be posted.
The best you can do is post a link to an image that is hosted elsewhere.
Glad to hear everything worked out. I appreciate your frustration at not knowig exactly what solved the problem, but at the end of the day it is solving the problem quickly that is the priority. :)