RE: KB925902 - Stop Error BSOD
- From: Helium <Helium@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 16 Apr 2007 11:42:01 -0700
I found KB898900, then applied it to Windows XP workstation and import the
registery value (listed below) to server and XP workstation but XP is still
crash. I cannot apply KB898900 to the Windows 2003 server since we has
applied Windows 2003 SP2 already, the mup.sys in server is updated to version
5.2.3790.3959 (17/2/2007).
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup\Parameters]
"DfsIrpStackSize"=dword:0000000a
Regards.
Helium
"Debbie" wrote:
Since last week we have done some additional testing and found that the.
hotfix + registry change mentioned in KB906866 *DOES* correct the STOP
0x00000035 BSOD we were getting. We are going to continue testing, but this
approach seems much more promising than removing the KB922582 patch.
"Helium" wrote:
Hi,
We have similiar situation for 10 computers when saving MS Word or Excel
file to Windows 2003 server with DFS share location. Our problem started on
April 11. In addition, change the directory name or file name in the Windows
2003 server with DFS share location, the Windows XP crash too. After the XP
restart, one more error popup as below.
Error signature
BCCode : 35 BCP1 : 89302008 BCP2 : 00000000 BCP3 : 00000000
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1
I tested one comptuer on April 11 with Symantec Corporation AntiVirus
10.1.0.401, Scan engine 71.2.0.12, Virus Definitions File version : 4/9/2007,
install "Malicious Software Removal Tool - April 2007 (KB890830)", the
Windows XP crash started when save MS Word or Excel to Windows 2003 server
with DFS share location. If uninstall Symantec, no crash. Further testing,
install Symantec Symantec Corporation AntiVirus 10.1.0.401 without virus
definition file update (defualt Virus Definitions File version : 2/15/2006
rev 6), no crash. Update virus definition files, crash happens.
Remove KB922582 patch fix the crash but I don't think this is the solution
since WindowsUpdate will automatically install it back and crash again.
Regards.
Helium
"Debbie" wrote:
Our environment is very similar to yours, and we first began experiencing the
BSOD STOP 0x00000035 "NO_MORE_IRP_STACK_LOCATIONS" April 6th. We tried the
hotfix mentioned in KB906866 with a decimal value of 10, but the BSOD problem
continued. We suspected that KB925902 might be the culprit since we noticed
many other folks were having problems with it... But in the end, we found it
was due to the KB922582 patch that was distributed by Microsoft last fall,
but only just resulted in a problem when mixed with some of the most recent
security patches. Removing KB922582 is not an acceptable solution, but it
did resolve the BSOD errors in our particular case.
"Ry" wrote:
Well - after doing more digging, it looks as though KB916846 was the culprit.
This patch (addressing an SMB communication issue) is responsible for
causing a "NO_MORE_IRP_STACK_LOCATIONS" overflow blue-screen when client
computers write to a DFS namespace.
I hope there is a fix/patch soon for this!
Ry
"Bob Held" wrote:
STOP 0x00000035 (0x8207ecd8, 0x00000000, 0x00000000, 0x00000000)
NO_MORE_IRP_STACK_LOCATIONS
Getting this consistently on systems with Roxio version 8.x when trying to
save to word, excel documents, etc to DFS fileshares after installing the
KB925902 security update.
Finding that un-install of patch does not help. Trying System Restore.
We do find that if we un-install Roxio ver 8 or upgrade to ver 9 that
problem does not happen.
- Follow-Ups:
- RE: KB925902 - Stop Error BSOD
- From: Helium
- RE: KB925902 - Stop Error BSOD
- References:
- KB925902 - Stop Error BSOD
- From: Bob Held
- RE: KB925902 - Stop Error BSOD
- From: Helium
- RE: KB925902 - Stop Error BSOD
- From: Debbie
- KB925902 - Stop Error BSOD
- Prev by Date: Re: Cleanup after Automatic Updates ?
- Next by Date: RE: Update Windows XP Home SP2
- Previous by thread: RE: KB925902 - Stop Error BSOD
- Next by thread: RE: KB925902 - Stop Error BSOD
- Index(es):
Relevant Pages
|