Are you getting this dump on all your DELL 755's or on only one computer?
Main Topics
Browse All TopicsTrying to apply a group policy to a large group of machines. All models work just fine except our DELL 755's. The BSOB is recieved before log in.
I've included the memory dump. How can I put my finger on the file/driver/service that causing me headaches? When setting up the dump file, only choices I had were mini dump or Kernal memory, I expected to see a third option but didn't.
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\\amedwamct7551\c$\WINDOW
Kernel Summary Dump File: Only kernel address space is available
**************************
WARNING: Dump file has been truncated. Data may be missing.
**************************
Symbol search path is: C:\WINDOWS\Symbols;srv*C:\
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.090206-1
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu Sep 3 15:39:33.371 2009 (GMT-4)
System Uptime: 0 days 0:02:08.921
Loading Kernel Symbols
..........................
..........................
...................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd600c). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
**************************
* *
* Bugcheck Analysis *
* *
**************************
Use !analyze -v to get detailed debugging information.
BugCheck 51, {4, 1, e41d9638, e02d18}
PEB is paged out (Peb.Ldr = 7ffd600c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd600c). Type ".hh dbgerr001" for details
Probably caused by : memory_corruption
Followup: memory_corruption
---------
1: kd> !analyze -v
**************************
* *
* Bugcheck Analysis *
* *
**************************
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 00000004, (reserved)
Arg2: 00000001, (reserved)
Arg3: e41d9638, depends on where Windows bugchecked, may be pointer to hive
Arg4: 00e02d18, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 7ffd600c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd600c). Type ".hh dbgerr001" for details
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x51
PROCESS_NAME: services.exe
LAST_CONTROL_TRANSFER: from 8062f066 to 804f9e0b
STACK_TEXT:
a94cf91c 8062f066 00000051 00000004 00000001 nt!KeBugCheckEx+0x1b
a94cf940 80633f1d 0000002e 00e02d18 d97f9cbc nt!CmpAssignSecurityToKcb+
a94cf968 8062cedc e2058008 02eb8cb8 d97f9cbc nt!CmpCreateKeyControlBloc
a94cf9b8 8062d8bc e2058008 02eb8cb8 d97f9cbc nt!CmpDoOpen+0xf4
a94cfbb0 805bd9a9 02eb8cb8 02eb8cb8 8a5635c0 nt!CmpParseKey+0x558
a94cfc28 805ba454 0000078c a94cfc68 00000040 nt!ObpLookupObjectName+0x1
a94cfc7c 80623673 00000000 8b491040 a94cfd01 nt!ObOpenObjectByName+0xea
a94cfd50 8054088c 00100d68 01060009 0080f318 nt!NtOpenKey+0x1af
a94cfd50 7c90e514 00100d68 01060009 0080f318 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0080f358 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
80503990-80503997 8 bytes - nt!KiServiceTable+30
[ ce 33 5d 80 7e 33 5d 80:f8 1e ba 8a 30 fe bd 8a ]
805039a4-805039a7 4 bytes - nt!KiServiceTable+44 (+0x14)
[ 8e 75 5a 80:98 64 c6 8a ]
805039dc-805039df 4 bytes - nt!KiServiceTable+7c (+0x38)
[ a4 30 5a 80:c0 b2 b8 8a ]
80503a0c-80503a0f 4 bytes - nt!KiServiceTable+ac (+0x30)
[ 72 55 61 80:18 5b c5 8a ]
80503a34-80503a37 4 bytes - nt!KiServiceTable+d4 (+0x28)
[ c8 f8 5c 80:5a 0e ba ac ]
80503a64-80503a67 4 bytes - nt!KiServiceTable+104 (+0x30)
[ 8e 27 62 80:90 36 ed ac ]
80503aac-80503aaf 4 bytes - nt!KiServiceTable+14c (+0x48)
[ f6 19 5b 80:e0 39 ee 8a ]
80503ac4-80503ac7 4 bytes - nt!KiServiceTable+164 (+0x18)
[ 16 73 5f 80:08 87 c1 8a ]
80503acc-80503acf 4 bytes - nt!KiServiceTable+16c (+0x08)
[ 52 60 5d 80:b0 28 bb 8a ]
80503b10-80503b13 4 bytes - nt!KiServiceTable+1b0 (+0x44)
[ 7e 0a 5b 80:f0 82 be 8a ]
80503b28-80503b2b 4 bytes - nt!KiServiceTable+1c8 (+0x18)
[ 5c cf 60 80:18 c9 c5 8a ]
80503b4c-80503b4f 4 bytes - nt!KiServiceTable+1ec (+0x24)
[ d0 bf 5e 80:10 5d bc 8a ]
80503b64-80503b67 4 bytes - nt!KiServiceTable+204 (+0x18)
[ ee bf 5e 80:10 ad ee 8a ]
80503c24-80503c27 4 bytes - nt!KiServiceTable+2c4 (+0xc0)
[ e8 01 62 80:80 77 0b 8b ]
80503c98-80503c9b 4 bytes - nt!KiServiceTable+338 (+0x74)
[ 0a 32 5d 80:58 3e bb 8a ]
80503cb4-80503cb7 4 bytes - nt!KiServiceTable+354 (+0x1c)
[ 02 00 5d 80:c8 f0 42 8b ]
80503cf0-80503cf7 8 bytes - nt!KiServiceTable+390 (+0x3c)
[ 54 c7 5c 80 d8 a9 5c 80:58 53 bf 8a 30 4f ee 8a ]
80503d3c-80503d3f 4 bytes - nt!KiServiceTable+3dc (+0x4c)
[ ee 07 62 80:e0 38 ed ac ]
80503d54-80503d5b 8 bytes - nt!KiServiceTable+3f4 (+0x18)
[ d2 32 5d 80 44 31 5d 80:38 45 1d 8b d8 f8 bc 8a ]
80503d64-80503d6b 8 bytes - nt!KiServiceTable+404 (+0x10)
[ 32 12 5d 80 2c 14 5d 80:68 c8 bb 8a 50 9e 1b 8b ]
80503d8c-80503d8f 4 bytes - nt!KiServiceTable+42c (+0x28)
[ 8c 18 5b 80:c8 87 b8 8a ]
80503db4-80503db7 4 bytes - nt!KiServiceTable+454 (+0x28)
[ 0c 2e 5b 80:60 49 c6 8a ]
805a30a4-805a30a8 5 bytes - nt!NtConnectPort
[ 8b ff 55 8b ec:e9 c5 33 70 39 ]
805bb014-805bb018 5 bytes - nt!NtMakeTemporaryObject (+0x17f70)
[ 8b ff 55 8b ec:e9 41 b4 6e 39 ]
805be9b6-805be9ba 5 bytes - nt!NtSetSecurityObject (+0x39a2)
[ 8b ff 55 8b ec:e9 8b 7a 6e 39 ]
805c9d0a-805c9d0e 5 bytes - nt!NtOpenProcess (+0xb354)
[ 68 c4 00 00 00:e9 59 c5 6d 39 ]
805c9f96-805c9f9a 5 bytes - nt!NtOpenThread (+0x28c)
[ 68 c0 00 00 00:e9 e1 c2 6d 39 ]
805cc754-805cc758 5 bytes - nt!NtSetInformationProcess
[ 68 fc 00 00 00:e9 75 9b 6d 39 ]
805cfa2a-805cfa2b 2 bytes - nt!NtCreateProcessEx (+0x32d6)
[ 6a 0c:e9 89 ]
805cfa2d-805cfa30 4 bytes - nt!NtCreateProcessEx+3 (+0x03)
[ e8 a8 4d 80:6d 39 90 90 ]
805cfae0-805cfae4 5 bytes - nt!NtCreateProcess (+0xb3)
[ 8b ff 55 8b ec:e9 bf 67 6d 39 ]
80620536-8062053a 5 bytes - nt!NtRestoreKey (+0x50a56)
[ 8b ff 55 8b ec:e9 cd 5e 68 39 ]
80620ab6-80620abc 7 bytes - nt!NtUnloadKey (+0x580)
[ 6a 68 68 c8 08 4e 80:e9 23 59 68 39 90 90 ]
806212fc-80621302 7 bytes - nt!NtQueryMultipleValueKey
[ 6a 4c 68 60 09 4e 80:e9 85 50 68 39 90 90 ]
80621b54-80621b5a 7 bytes - nt!NtRenameKey (+0x858)
[ 6a 34 68 b0 09 4e 80:e9 db 47 68 39 90 90 ]
8062212e-80622132 5 bytes - nt!NtCreateKey (+0x5da)
[ 68 c4 00 00 00:e9 d7 41 68 39 ]
806225be-806225c4 7 bytes - nt!NtDeleteKey (+0x490)
[ 6a 38 68 18 0a 4e 80:e9 5b 3d 68 39 90 90 ]
8062296e-80622974 7 bytes - nt!NtEnumerateKey (+0x3b0)
[ 6a 54 68 70 0a 4e 80:e9 3f 3a 68 39 90 90 ]
80622bd8-80622bde 7 bytes - nt!NtEnumerateValueKey (+0x26a)
[ 6a 54 68 b0 0a 4e 80:e9 bf 37 68 39 90 90 ]
806234c4-806234c8 5 bytes - nt!NtOpenKey (+0x8ec)
[ 68 94 00 00 00:e9 2d 2e 68 39 ]
806237e8-806237ee 7 bytes - nt!NtQueryKey (+0x324)
[ 6a 60 68 60 0b 4e 80:e9 43 2c 68 39 90 90 ]
80623aa8-80623aae 7 bytes - nt!NtLoadKey2 (+0x2c0)
[ 6a 68 68 a0 0b 4e 80:e9 1b 29 68 39 90 90 ]
80623d0e-80623d12 5 bytes - nt!NtReplaceKey (+0x266)
[ 8b ff 55 8b ec:e9 09 27 68 39 ]
80623e28-80623e2c 5 bytes - nt!NtNotifyChangeKey (+0x11a)
[ 8b ff 55 8b ec:e9 c7 25 68 39 ]
226 errors : !nt (80503990-80623e2c)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
---------
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
We are getting the same error 51 from all the dell 755's. The image used to create the image for the 755's was a Dell 745 that they used and loaded onto a 755. This image works great and has for a couple of years. Its not until we apply the group policy with security setttings, registry updates and file permission changes. We have an abundance of other Dell and HP models and no others give us the BSOD. We've created a new image and tested it and it works great. The problem is we have over a 1,000 755's deployed and reimaging that many would be a problem as you can imagine. So, I am trying to find the driver/service/file/regist
Thanks for the assist
Please run some additional Windbg commands...
!analyze -v; kv; r; lmnt; lmntsm; !locks; !vm; .bugcheck
Have you considered running the driver verifier? START | Run | cmd | verifier
Here is additional d/verifier info - http://www.techsupportforu
Regard
jcgriff2
Hello, WaywardS0n
some functions (nt!NtOpenProcess, nt!NtOpenKey and etc) in the ntoskrnl are hooked by some module. To determine which module hooked them you should perform the command (for example):
u 806234c4
Results should be similar to "jmp mymodule+0xXXX (B9CA62F1)" where "mymodule" is a name of the module which hooked the function, in this case, NtOpenKey.
Hi -
Thank you for running those commands. I don't believe this has anything to do with Group Policy directly, rather it just lit the fuse. It appears to me that the very recent update of Norton (NIS, N360 --?) pushed the envelope and the BSODs resulted. When was Norton updated - before or after the image was created?
The dates on the Norton drivers are very recent -
naveng.sys Sat Aug 22 01:31:12 2009 (4A8F82A0)
navex15.sys Sat Aug 22 01:37:19 2009 (4A8F840F)
Not much doubt here that Norton was a huge catalyst primarily because you are running XP SP2 and the new drivers may very well have been written with XP SP3 in mind, now out for 1.5 years. I think it is time that SP3 be looked at for installation. The only Windows Updates that are evident to me are the NT Kernel & win32k - Feb 2009 & Apr 2009, respectively. Other than that, all are either 2001 or 2004.
Also - the ~ 1 year old dormant and most likely corrupt installation of McAfee is certainly not helping matters here in the least. Mcafee & Norton will go after each other and you will not be the winner. Use the McAfee Removal Tool</A> to remove these remnants -
mfehidk.sys Thu Oct 30 18:38:34 2008 (490A376A)
mfetdik.sys Thu Oct 30 18:39:56 2008 (490A37BC)
Also, this Intel PRO/1000 NIC driver is/ will be a big problem - it may cause 0xc0000005 exceptions (memory access violations) -
e1e5132.sys Fri Apr 13 16:12:48 2007 (461FE440)
There are other older 3rd party drivers from the likes of Creative Solutions (Roxio) from 2005 that can cause trouble as well.
I know you are looking for a quick solution here. My best guess on this is that the Intel Pro NIC or maybe McAfee clashed with Norton. No doubt that Norton is in the lead here as the primary contributor to the crash.
Regards. . .
jcgriff2
First of all, thank you for taking the time to look at this issue.
I'm going to work with the suggestions given.
1st. try service pack 3.
2nd investigate the NIC driver /remove driver not required (roxio) etc.
3rd try to remove norton and mcafee
Also, here is the BSOD scenerio.
1. Re-image the PC with an image used on all the 755's
2. The computer object is put into an intermediate OU without the GP attached.
3. PC is brought online and attached to the domain.
4. PC is tested by running apps, log offs & on, reboots and power offs.
5. The PC is powered down.
6. The computer object is moved to an OU with the GP attached.
7.The PC is powered on.
8. Before anyone can log on, we get the BSOD
How we discovered the problem to begin with...
Approximately 90mins after attaching the GP to a test group of computers ALL of the 755's delivered the BSOD with or without a users logged in and actively working.
Thanks for the input and I'll let you know the results of the testing.
WaywardS0n:
You mentioned above: "....... The image used to create the image for the 755's was a Dell 745 that they used and loaded onto a 755. This image works great and has for a couple of years.........We've created a new image and tested it and it works great...."
Has this scenario changed? If it hasn't.....then the problem was solved? Was it not?
One thing I don't understand. . . if this was an image that has been working great for years... how did a 2009 installation of Norton get in here?
As mentioned in my post, I would use the McAfee removal tool & get rid of the old installation.
Then use the Norton removal tool as well. It is possible that the McAfee damaged Norton in some manner.
McAfee RTool - http://download.mcafee.com
No
I
Are you sure this image BSODs on more than the one system?
If it is a driver that is the underlying cause the Driver Verifier should be able to flag it. Please take a look at these instructions -
http://www.techsupportforu
Don't run the D/V until Norton, McAfee, Roxio are removed.
When you do run the driver verifier, be ready to encounter another BSOD. Please get the dump and attach it so that I can take a look at it. You'll have to rename it so it ends in TXT.
Also, run Driver Query -
driverquery /v > "%temp%\1" & start notepad "%temp%\1" --- save it as a text file & attach.
Another big help would be a msinfo32 NFO file - from the cmd/DOS prompt, msinfo32 - save it with the default NFO file ext, then rename TXT & attach.
Post here and I will check the thread throughout the day. You can also use the email on my profile page &/or send a message to me via the one that wrote the driver verifier post at the TSF forum. I'll make sure that all is posted back here for all to see.
Regards. . .
jcgriff2
Business Accounts
Answer for Membership
by: BitsBytesandMorePosted on 2009-09-04 at 08:43:56ID: 25260710
This means that you might have a bad memory