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

[pitbullfan01]

System - Dell PowerVault 745N
Microsoft Windows Server 2003, Standard Edition SP1
P4 3 GHz
RAM - 2GB
Network - Intel(R) PRO/1000

I have 2 identical computers NAS1 and NAS2. Both Systems have been completely update to rule out as cause. Servers have been having issue since at least August. Both servers are Stand Alone.

The servers frequently reboot when I Remote Desktop to them. Not all the time, but very frequent. After reboot, I receive the Send error report screen. When I click on view techincal information, a minidump has been created. I also notice the same errors in the logs of both machines:

Error # 1. Event ID 1003
Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3 00000000, parameter4 00000000.

Error # 2. The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini110706-01.dmp.

I have run numerous DSET reports for Dell. All hardware passed each test. Ran check disk with /F and /R. Came back clean fooor both.

Dell now thinks the pagefile may be corrupted on both computers... They want me to move the pagefile to another drive, then move back to C: drive. I am kinda sceptical about doing this. In the past, on a few Windows servers, I removed the pagefile from C: and create on another drive. When I reboot, the server OS is hosed. Server is pingable but most services will not start and drivers are not present. Also, cannot RDP to server and when I go to the server to logon, I am able to logon but server is hosed. Bottom line, I need to repair OS on the server. So, I would like to move pagefile as last resort because I am also not sure if Dell is still troubleshooting or thinks this is the fix...

I have attached Minidumps. Hopefully, you can point me to what is causing the reboots... Help please! MiniDumps reference NAS1 and NAS2. These are 2 different servers.

 

[xxdanielxx]

for nas1 all of the dump files point to DRIVER_FAULT_SERVER_MINIDUMP ntkrnlmp.exe have u install any new hardware?

for nas2 all of the dump files point to memory_corruption try runing memtest86 to check your ram let it run for at least 5 passes

 

[cpc2004]

Hi,

For NAS1, they are crashed by stack overflow, extend the stack will resolve the problem. Click Here to find out the procedure to extend windows kernel stack.

For NAS2, there has hundreds of memory corruption and this is the sign of bad paging space. Run chkdsk /r at recovery console and re-allocate the paging space.

 

[xxdanielxx]

cpc how did you get stack overflow i would like to know to further my knowl... of reading minidumps

 

[xxdanielxx]

never mind i can belive i am blind

 

[cpc2004]

Hi,

Windbg !thread command shows the size of the stack. The limit is b6564000 (refer the value of esp) and the last stack is starting at b656efe0 and the size is 16. Obviously the stack is full. The stack is full maybe related to stack is not big enough or the stack pointer is corrupted due to software problem. There has only one stack entry at the stack trace. Probably the stack pointer is corrupted and all the dumps are the same. I don't believe that it is hardwar problem as hardware occurs randomly. Anyway it is no hint to extend the size of the stack. Maybe it can fix the problem.

0: kd> r
eax=b6560023 ebx=b65640e8 ecx=85f1d020 edx=85ef4008 esi=b6564064 edi=8083930e
eip=80837c8b esp=b6563fe0 ebp=b6563fe0 iopl=0 nv up di pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010046
nt!KiTrap0E+0x5c:
80837c8b 89550c mov dword ptr [ebp+0Ch],edx ss:0010:b6563fec=????????

0: kd> !thread
GetPointerFromAddress: unable to read from 808a5298
THREAD 85f1d020 Cid 13d8.09a4 Teb: 7ffdd000 Win32Thread: e3d55c28 RUNNING on processor 0
IRP List:
Unable to read nt!_IRP @ 86074bc0
Not impersonating
GetUlongFromAddress: unable to read from 808b4414
Owning Process 85f33b20 Image: csrss.exe
ffdf0000: Unable to get shared data
Wait Start TickCount 19572655
Context Switch Count 138 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.0000
KernelTime 00:00:00.0000
Start Address 0x4a6810ea
Stack Init b6567000 Current b6564df0 Base b6567000 Limit b6564000 Call 0
Priority 14 BasePriority 13 PriorityDecrement 0
ChildEBP RetAddr Args to Child
b6563fe0 00000000 00000000 00000000 00000000 nt!KiTrap0E+0x5c (FPO: [0,0] TrapFrame-EDITED @ 00000000)