Fatal Errors

Hi.
Before I start I just want to thank all of you who read this and contribute. It's very nice of you to help people with their computer problems as they are oftentimes very extensive and aggravating.

My problem is I bought a new case the other day (bad idea) and attempted to reinstall the motherboard myself (worse idea) without reading any directions whatsoever (horrible idea). The system actually works fine, except on occasion I get the following blue screen which I didn't before.

I downloaded the debugging tools and I got this from it.


Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp2.030422-1633
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054a230
Debug session time: Fri Aug 13 01:45:52.109 2004 (GMT-7)
System Uptime: 0 days 0:07:23.826
Loading Kernel Symbols
...................................................................................................................
Loading unloaded module list
.........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 80538105, b61e35b0, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+105 )

Followup: Pool_corruption
---------

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 80538105, The address that the exception occurred at
Arg3: b61e35b0, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

FAULTING_IP:
nt!ExDeferredFreePool+105
80538105 893b mov [ebx],edi

TRAP_FRAME: b61e35b0 -- (.trap ffffffffb61e35b0)
ErrCode = 00000002
eax=e2aa07a0 ebx=00000000 ecx=000001ff edx=e2aa0d10 esi=89537078 edi=00aa0000
eip=80538105 esp=b61e3624 ebp=b61e3664 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ExDeferredFreePool+0x105:
80538105 893b mov [ebx],edi ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 805386dc to 80538105

STACK_TEXT:
b61e3664 805386dc 00000001 00000000 e2a65008 nt!ExDeferredFreePool+0x105
b61e369c bf87dfff e2a65008 00000000 bf87609c nt!ExFreePoolWithTag+0x40a
b61e36a8 bf87609c e2a65008 bf877824 e2a65008 win32k!HeavyFreePool+0xb6
b61e36b0 bf877824 e2a65008 00000005 690107ba win32k!FreeObject+0x22
b61e3704 bf8725eb 00000000 690107ba e8050806 win32k!SURFACE::bDeleteSurface+0x149
b61e3714 bf862069 e8050806 e8050806 bf85f7ea win32k!bDeleteSurface+0x18
b61e3720 bf85f7ea e8050806 00000558 00000001 win32k!GreDeleteObject+0x8e
b61e3874 bf85eb21 1e010802 00000043 00000000 win32k!GreStretchDIBitsInternal+0xc80
b61e38ec 805306a4 1e010802 00000043 00000000 win32k!NtGdiStretchDIBitsInternal+0xd2
b61e38ec 7ffe0304 1e010802 00000043 00000000 nt!KiSystemService+0xc9
0006c848 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+105
80538105 893b mov [ebx],edi

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: Pool_corruption

SYMBOL_NAME: nt!ExDeferredFreePool+105

MODULE_NAME: Pool_Corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x8E_nt!ExDeferredFreePool+105

BUCKET_ID: 0x8E_nt!ExDeferredFreePool+105

Followup: Pool_corruption
---------


Any ideas?

 

What kind of software do you have on your system? Only the O.S. XP?
There is nothing to do with the motherboard. We must to learn and for that we need to do all that kind of things

 

Yah I dunno. I was just thinking that because it didn't do this before I messed with the case and now that it happens after that it was probably something to do with an incorrectly installed part.

I just have a single OS which is XP. I don't overclock or do anything like that.

 

Oh just one more thing that might help a bit with the diagnosis.

3/5 times this happens when I try to shut down the computer... I click shut down, it starts turning off and then I get the blue screen.

Hope this helps

 

From reviesing the debug info it looks as if your Network hangsup before you are finished transmitting, as a result BOOM. I take it when you installed a new mobo you didnt install a clean WinXP?..It's not usually a problem but you could have some driver problems if they are similar boards

 

I didnt install a new motherboard =(

Everything in there is the exact same as it was in the older case.