Window XP BSOD

Hi, for the past few days I been keep getting BSOD. The problem started with my computer keep freezes randomly so I tried to reformat my computer to solve the problem. But now it freezes and BSOD comes up. After the BSOD and windows boots up my ATI controller program was having error, so I reinstall the driver for it and now it still showing BSOD. I also did memtest to see if my memory is failing, and I passed the standard test twice. Here are the debugging analysis that I did for my latest minidump files. I have had a total of 4 BSODs for the last 3 days. Plz Help Thank You

Minidump 1
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071509-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 XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.090206-1316
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jul 15 01:06:23.750 2009 (GMT-7)
System Uptime: 0 days 15:05:34.690
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {4128a, 6adbf201, 8279b824, c0883000}

Probably caused by : memory_corruption ( nt!MiSwapWslEntries+191 )

Followup: MachineOwner
---------

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0004128a, The subtype of the bugcheck.
Arg2: 6adbf201
Arg3: 8279b824
Arg4: c0883000

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


BUGCHECK_STR: 0x1a_4128a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: avgnsx.exe

LAST_CONTROL_TRANSFER: from 8052365f to 804f9f43

STACK_TEXT:
9ee13c54 8052365f 0000001a 0004128a 6adbf201 nt!KeBugCheckEx+0x1b
9ee13c88 80506182 000000c4 00000009 c0883000 nt!MiSwapWslEntries+0x191
9ee13cb8 805062d8 89a91db8 000000c4 e1d27301 nt!MiAddWsleHash+0x1d6
9ee13cf4 80520b65 89a91db8 00461c08 00000000 nt!MiGrowWsleHash+0x11c
9ee13d4c 80544588 00000008 00461c08 00000001 nt!MmAccessFault+0x1193
9ee13d4c 00461c08 00000008 00461c08 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
00effdec 00000000 00000000 00000000 00000000 0x461c08


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiSwapWslEntries+191
8052365f f6451401 test byte ptr [ebp+14h],1

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiSwapWslEntries+191

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 498c114b

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x1a_4128a_nt!MiSwapWslEntries+191

BUCKET_ID: 0x1a_4128a_nt!MiSwapWslEntries+191

Followup: MachineOwner
---------

Minidump 2

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


Loading Dump File [C:\WINDOWS\Minidump\Mini071209-02.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 XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.090206-1316
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jul 12 19:27:35.187 2009 (GMT-7)
System Uptime: 0 days 1:00:17.759
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {0, 2, 1, 805226f8}

Probably caused by : memory_corruption ( nt!MiRemovePageByColor+66 )

Followup: MachineOwner
---------

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 805226f8, address which referenced memory

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


WRITE_ADDRESS: 00000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemovePageByColor+66
805226f8 ff08 dec dword ptr [eax]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: GSvr.exe

TRAP_FRAME: 9d9d5a90 -- (.trap 0xffffffff9d9d5a90)
ErrCode = 00000000
eax=01140000 ebx=01130000 ecx=00001000 edx=fffff000 esi=0113f000 edi=01140000
eip=80615add esp=9d9d5b04 ebp=9d9d5b0c iopl=0 nv up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
nt!ProbeForWrite+0x39:
80615add 8a06 mov al,byte ptr [esi] ds:0023:0113f000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 80522a90 to 805226f8

STACK_TEXT:
9d9d5a08 80522a90 00000000 c00089f8 0000000f nt!MiRemovePageByColor+0x66
9d9d5a24 80520885 0113f000 0113f000 9d9d5b0c nt!MiRemoveZeroPage+0x8a
9d9d5a78 80544588 00000000 0113f000 00000000 nt!MmAccessFault+0xeb3
9d9d5a78 80615add 00000000 0113f000 00000000 nt!KiTrap0E+0xd0
9d9d5b0c 80611137 01130000 00010000 00000004 nt!ProbeForWrite+0x39
9d9d5d4c 8054162c 00000005 01130000 00010000 nt!NtQuerySystemInformation+0x51
9d9d5d4c 7c90e514 00000005 01130000 00010000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00befaac 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemovePageByColor+66
805226f8 ff08 dec dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiRemovePageByColor+66

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 498c114b

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiRemovePageByColor+66

BUCKET_ID: 0xA_nt!MiRemovePageByColor+66

Followup: MachineOwner
---------

 

I also see avgnsx.exe which is file a from AVG AntiVirus. Try uninstalling AVG and see what happens.... I'm by no means any sort of dump-reading guru, but this seems fairly straight-forward...

 

I also see numerous references to 'memory corruption'. Perhaps running a memory diagnostic and/or a hard drive diagnostic would be a good idea, it can't hurt. You can download the free hard drive diagnostic from your drive maker's web site, and for a free memory diagnostic, I prefer this one. The download will create either a bootable floppy disk, or an ISO image file which you'd burn to CD as an image, then boot to it. Once the program is up and running, press "T" for the extended tests, then run at leat 3-4 passes. It will take time, so be patient. Test 7 might look like the PC has locked up, it hasn't.

 

Quite a few people report problems with the Gigabyte Dymanic Energy Saver program.
I would uninstall it.