11-14-2011 05:39 PM
I did save it as a text file, and was able to open it from the link. Here is the detail from the latest crash:
Dump File : Mini111111-01.dmp
Crash Time : 11/11/2011 1:03:22 AM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0x00000001
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0xb8ad0c34
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22f43
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22f43
Stack Address 1 : ntoskrnl.exe+3be48
Stack Address 2 : ntoskrnl.exe+68dd6
Stack Address 3 : ntoskrnl.exe+692a6
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini111111-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 94,208
11-14-2011 07:21 PM
Hello dev9999, if you check the upper right hand conner of the page you will see a yellow envelope. I send you a pm with instructions. Please dont share the log in information with anyone, since that is for you to upload the files.
11-14-2011 07:26 PM - edited 11-14-2011 07:29 PM
Over the years you have had numerous crashes in different drivers.
Several for your nVidia card, a few for your network adapter, USB driver, file system driver, and an old symantec driver back in 2007.
Seeing all these different driver errors and all the page faults errors makes me suspect the RAM.
While you are waiting for Michael, maybe you could run a thorough RAM test.
I'm also curious about all the running tasks, is this XP system being used as a sql server or for software development?
EDIT- I'm sorry, I didn't see Michael's post. Please ignore this because I don't want to get in the way here.
11-14-2011 08:59 PM - edited 11-14-2011 09:17 PM
Sorry, my bad. I saved your BSOD.txt file to my hard drive and I can view it without any problems. Too bad I don't have a clue what most of it means.
I did notice a few older BSODs associated with mbam.sys. I don't want to interfere with your troubleshooting with michaell, but be sure to let him know if you have Malwarebytes' Anti-Malware or any other security software (e.g., McAffee, AVG. etc.) running in real-time protection mode at the same time as NIS. Running manual on-demand scans with anti-malware programs like MBAM shouldn't cause a problem, but having two or more anti-malware programs running simultaneously in the background can cause all sorts of odd behavior. I've even heard of users who had problems with NIS because they didn't get a clean uninstall of their old security software before installing their Norton product.
Windows Vista Home Premium 32-bit SP2 * NIS 2011 v. 184.108.40.206 * IE 9.0 * Firefox 8.0.0
HP Pavilion dv6835ca, Intel Core2Duo CPU T5550 @ 1.83 GHz, 3.0 GB RAM, NVIDIA GeForce 8400M GS
11-15-2011 05:50 PM
@dev9999, I sent you anther pm. I think I might some more dumps to figure out what is going on. One thing I did notice is there is arround 1400 handles open related to mutex to filezilla. Could you let us know how you are using it on your computer?
11-15-2011 06:50 PM
I know little about the ins and outs of networking but is there anything relevant in this thread on impact on network performance:
11-16-2011 07:22 PM
Hello dev9999, this looks like a problem in the filezila explorer extention that gets installed when you install FileZilla. The 3.1 version which is a couple of years old looks like is had a handle leak and since it gets loaded into memory into ccSvcHst during a file operation, it leaks the handle in ccSvcHst. I tested it with the latest version of filezilla and everything works fine. So you can etheir upgrade to latest version, or uninstall it if you dont use it.
11-17-2011 06:58 PM
Uninstalling FileZilla fixed the issue! The handles have remained below 6,000 for the past 24 hours. It is amazing to me that a program that I don't use and which doesn't run in the background could cause a memory leak. I have been trying to figure out the cause of the issues with my computer for years now. I will know in a few days if the handle leak was the root cause of all of the other issues, and if so, I will post again with a list of the symptoms so others may benefit.
Thanks to michaell for all the help, you are awesome!