Windows BBS The Place for Microsoft Windows Support! Windows, Support, Help Site

Go Back   Windows BBS > Operating Systems > Windows Server System

Windows Server System Post your Windows Server System question here. Besides Windows Server 2003, Windows Server System also includes other Microsoft Server software (such as BizTalk Server, Exchange Server, ISA Server & others).

Register your FREE account to unlock additional features at WindowsBBS.com
Register
Welcome to WindowsBBS.com
Microsoft Windows Support

Mission Statement

WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.

Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.


Discussion Forums
Operating Systems
Windows 7 Windows 7
Windows Vista Windows Vista
Windows XP Windows XP
Windows Server System Windows Server System
Windows 2000 Windows 2000
Windows 95/98/Me/NT Windows 95/98/Me/NT
Internet & Networking
Networking
Internet Explorer
Microsoft Mail
Firefox, Thunderbird
      & SeaMonkey

General Internet
Security
General Security
Malware and Virus
     Removal

Other
Other Software
Hardware
Test Posts
Community
Introductions
General Discussions
Comments
      & Suggestions

News @ WindowsBBS

Forum Sponsor
 Image

Reply
 
LinkBack Thread Tools
Old 15th May 2006   #1
Inactive
 
Profile:
Join Date: May 2006
Posts: 1
Computer Experience:
Intermediate
kricket Reputation Level


W2k3 BSOD [DUMP Data]

Hi All,

We have recently purchased a brand new HP Proliant ML370 G4 server and put W2k3 Server and citrix metaframe 3.0 presentation server on it.

Over the past couple of weeks we have started having random BSOD, with the following error codes;

Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3 00000000, parameter4 00000000

Can anyone shed some light on what this could be. I have tried analyzing the Memory dump with WinDbg

Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [\\gbranch\c$\WINDOWS\Minidump\Mini050806-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: Server, suite: TerminalServer
Built by: 3790.srv03_sp1_rtm.050324-1447
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af988
Debug session time: Mon May 8 11:29:57.660 2006 (GMT+8)
System Uptime: 0 days 6:57:52.492
Loading Kernel Symbols
........................................................................... ..........................................
Loading User Symbols
Loading unloaded module list
......
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, f772ffe0, 0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: kd> !analyze -v
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: f772ffe0
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

CURRENT_IRQL: 1

LAST_CONTROL_TRANSFER: from 00000000 to 80a79431

STACK_TEXT:
ba28afcc 00000000 00000000 00000000 00000000 hal!HalBeginSystemInterrupt+0x19


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
80a78000-80a78070 113 bytes - hal!HalInitApicInterruptHandlers+28
[ e8 10 66 89 44 ca 06 b9:a0 89 a7 80 a4 89 a7 80 ]
80a78072-80a78080 15 bytes - hal!Dr_HReboot_a+3e (+0x72)
[ 3d 20 00 00 00 8b 9f f8:a7 80 46 8b a7 80 46 8b ]
80a78083-80a780a4 34 bytes - hal!Dr_HReboot_a+4f (+0x11)
[ 0f 23 c3 0f 23 c9 8b 9f:ff ff ff ff 0f b6 44 24 ]
80a780a7-80a78130 138 bytes - hal!Dr_HReboot_a+73 (+0x24)
[ 0f 23 f3 0f 23 f9 e9 c8:64 00 00 00 f0 0f ab 05 ]
80a78132-80a78155 36 bytes - hal!HalpApicRebootService+2a (+0x8b)
[ 66 8e e3 66 8e d8 66 8e:00 00 b8 7c 81 a7 80 66 ]
80a78157-80a78185 47 bytes - hal!HalpApicRebootService+4f (+0x25)
[ 0f 82 57 ff ff ff c7 44:00 b8 c0 88 a7 80 66 89 ]
80a78187-80a78191 11 bytes - hal!HalpApicRebootService+7f (+0x30)
[ 0d db ba 89 5d 00 89 7d:75 0a f6 45 6c 01 0f 84 ]
80a78193-80a781bf 45 bytes - hal!HalpApicRebootService+8b (+0x0c)
[ 00 00 8b 0d 80 00 fe ff:0f 21 c3 0f 21 c9 0f 21 ]
80a781c1 - hal!Dr_HGeneric_a+5 (+0x2e)
[ 02:00 ]
80a781c3-80a781cc 10 bytes - hal!Dr_HGeneric_a+7 (+0x02)
[ 75 0a f6 45 6c 01 0f 84:8b 9f f8 02 00 00 8b 8f ]
80a781d0 - hal!Dr_HGeneric_a+14 (+0x0d)
[ 21:23 ]
80a781d3 - hal!Dr_HGeneric_a+17 (+0x03)
[ 21:23 ]
80a781d5-80a781e0 12 bytes - hal!Dr_HGeneric_a+19 (+0x02)
[ 0f 21 d7 89 5d 18 89 4d:8b 9f 00 03 00 00 8b 8f ]
80a781e2-80a781e3 2 bytes - hal!Dr_HGeneric_a+26 (+0x0d)
[ 21 db:23 d3 ]
80a781e5-80a781fb 23 bytes - hal!Dr_HGeneric_a+29 (+0x03)
[ 21 f1 0f 21 ff 89 5d 24:23 d9 8b 9f 08 03 00 00 ]
80a781fe-80a78227 42 bytes - hal!Dr_HGeneric_a+42 (+0x19)
[ 00 8b 9f f8 02 00 00 8b:8b ff 8b 44 24 64 b9 10 ]
80a78229-80a78236 14 bytes - hal!Dr_HGeneric_a+6d (+0x2b)
[ 8b 8f 0c 03 00 00 0f 23:00 00 90 8b 85 84 00 00 ]
80a78238-80a78270 57 bytes - hal!Dr_HGeneric_a+7c (+0x0f)
[ 00 00 8b ff 8b 44 24 64:8b 4d 7c 8b 95 80 00 00 ]
80a78272-80a7827a 9 bytes - hal!V86_HGeneric_a+a (+0x3a)
[ 00 00 8b 4d 7c 8b 95 80:75 b8 bb 30 00 00 00 b8 ]
80a7827d-80a78280 4 bytes - hal!V86_HGeneric_a+15 (+0x0b)
[ 66 89 45 50:00 66 8e e3 ]
80a78282-80a782ac 43 bytes - hal!V86_HGeneric_a+1a (+0x05)
[ 89 5d 30 66 89 4d 34 66:8e d8 66 8e c0 64 8b 1d ]
80a782ae-80a782de 49 bytes - hal!HalpBroadcastCallService+1e (+0x2c)
[ 75 b8 66 83 7c 24 6c 08:00 00 00 64 8b 0d 24 01 ]
80a782e2-80a782e4 3 bytes - hal!HalpBroadcastCallService+52 (+0x34)
[ 64 c7 05:8b 0d 80 ]
80a782e6-80a782f3 14 bytes - hal!HalpBroadcastCallService+56 (+0x04)
[ 00 00 00 ff ff ff ff 89:fe ff 51 a3 80 00 fe ff ]
80a782f5 - hal!HalpBroadcastCallService+65 (+0x0f)
[ 01:00 ]
80a782f7-80a7830e 24 bytes - hal!HalpBroadcastCallService+67 (+0x02)
[ 0f 82 3f ff ff ff c7 44:00 e8 c1 52 00 00 58 a3 ]
80a78310-80a7834d 62 bytes - hal!HalpBroadcastCallService+80 (+0x19)
[ f6 41 03 ff 0f 85 a2 fe:00 02 00 75 0a f6 45 6c ]
80a7834f-80a78359 11 bytes - hal!HalpBroadcastCallService+bf (+0x3f)
[ 00 ff 25 10 60 a7 80 8b:8b 9f f8 02 00 00 8b 8f ]
80a7835b-80a78364 10 bytes - hal!HalpGenericCall+3 (+0x0c)
[ 00 00 f7 05 00 02 a8 80:0f 23 c3 0f 23 c9 8b 9f ]
80a78367-80a78399 51 bytes - hal!HalpGenericCall+f (+0x0c)
[ 75 ef f0 0f ba 2d 00 02:8b 8f 04 03 00 00 0f 23 ]
80a7839c-80a783b4 25 bytes - hal!HalpGenericCall+44 (+0x35)
[ e8 6f 42 00 00 e8 16 00:8b 52 04 8b 52 1c c1 e0 ]
80a783b7-80a783ba 4 bytes - hal!HalpGenericCall+5f (+0x1b)
[ 00 00 c2 0c:90 8b 85 84 ]
80a783bc-80a783f9 62 bytes - hal!HalpPollForBroadcast (+0x05)
[ a1 48 f0 df ff 85 05 0c:00 00 8b 9d 88 00 00 00 ]
80a783fb-80a78434 58 bytes - hal!Dr_HApicErr_a+7 (+0x3f)
[ 75 0a f6 45 6c 01 0f 84:00 02 00 75 b8 66 83 7c ]
80a78437-80a78452 28 bytes - hal!Dr_HApicErr_a+43 (+0x3c)
[ 8b 9f f8 02 00 00 8b 8f:00 00 ff ff ff ff 89 5c ]
80a78455-80a7845f 11 bytes - hal!Dr_HApicErr_a+61 (+0x1e)
[ 0f 23 d3 0f 23 d9 8b 9f:64 8b 0d 24 01 00 00 fc ]
80a78461-80a78482 34 bytes - hal!Dr_HApicErr_a+6d (+0x0c)
[ 8b 8f 0c 03 00 00 0f 23:f6 41 03 ff 0f 85 a1 fe ]
80a78484-80a784a9 38 bytes - hal!Abios_HApicErr_a+10 (+0x23)
[ 8b 52 04 8b 52 1c c1 e0:00 00 83 ec 04 54 68 c1 ]
80a784ac-80a784b3 8 bytes - hal!V86_HApicErr_a+c (+0x28)
[ 8b 4d 7c 8b 95 80 00 00:00 f7 05 10 02 a8 80 01 ]
80a784b5-80a784d5 33 bytes - hal!V86_HApicErr_a+15 (+0x09)
[ 66 89 45 50 66 89 5d 30:00 00 75 ef f0 0f ba 2d ]
80a784d7-80a78506 48 bytes - hal!HalpLocalApicErrorService+f (+0x22)
[ 4c 24 40 89 54 24 3c f7:15 18 02 a8 80 a3 1c 02 ]
80a78509-80a78532 42 bytes - hal!HalpLocalApicErrorService+41 (+0x32)
[ 00 66 8e e3 66 8e d8 66:c2 0c 00 64 a1 48 00 00 ]
80a78534-80a78538 5 bytes - hal!HalpLocalApicErrorService+6c (+0x2b)
[ ff c7 44 24 64:f7 02 00 10 00 ]
80a7853a-80a78546 13 bytes - hal!HalpLocalApicErrorService+72 (+0x06)
[ 00 00 00 8b 0d 24 f1 df:74 03 49 75 f5 8b c1 c3 ]
80a78548-80a78591 74 bytes - hal!HalpLocalApicErrorService+80 (+0x0e)
[ f6 41 03 ff 0f 85 a2 fe:00 02 00 75 0a f6 45 6c ]
80a78593-80a785d1 63 bytes - hal!HalpLocalApicErrorService+cb (+0x4b)
[ 00 00 00 a1 20 f0 df ff:0f 23 c3 0f 23 c9 8b 9f ]
80a785d3-80a7864d 123 bytes - hal!Dr_Hipi_a+7 (+0x40)
[ 75 0a f6 45 6c 01 0f 84:00 8b 52 04 8b 52 1c c1 ]
80a7864f-80a78651 3 bytes - hal!Abios_Hipi_a+3 (+0x7c)
[ 64 b9 10:30 bb 30 ]
80a78655-80a78658 4 bytes - hal!Abios_Hipi_a+9 (+0x06)
[ 64 8b 15 20:b8 23 00 00 ]
80a7865a-80a78669 16 bytes - hal!Abios_Hipi_a+e (+0x05)
[ 00 00 8b 52 04 8b 52 1c:66 8e e3 66 8e d8 66 8e ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.
7915 errors : !hal (80a78000-80a79fff)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

Followup: memory_corruption


Last edited by kricket; 15th May 2006 at 10:41. Reason: More info
kricket is offline   Reply With Quote
Didn't find the information you thought to find?
Check out these Similar Threads
Old 16th May 2006   #2
Inactive
 
Profile:
Join Date: Jul 2005
Location: HK
Posts: 367
Computer Experience:
Experienced
cpc2004 Reputation Level


corrupted paging space

Your windows is crashed with 7915 memory errors and it is the sign of corrupted paging space. Run chkdsk /r and re-allocate the paging space.
cpc2004 is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows XP SP2 + mediaportal/mediaplayer [DUMP DATA] zeizei Windows XP 5 18th April 2006 20:27
BSOD - WinXP DRIVER_FAULT? [DUMP DATA] pmossop Windows XP 7 18th April 2006 18:07
Random BSOD [dump data] spotta Windows XP 9 14th February 2005 04:12
BSOD/probably HDD corrupt [DUMP DATA] Kostya Windows XP 1 5th February 2005 03:17
Windows XP Pro - Restarting - BSOD [Dump Data] krhymer Windows XP 1 22nd January 2005 19:24


All times are GMT +1. The time now is 22:55.






Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.2.0
Copyright © 2002 - 2008 WindowsBBS.com. All rights reserved.
Terms of Use, Legal Information & Privacy Policy
[]