Getting a BCCode error.

[Skraeling]

So i decided to overclock my video card one night and forgot to un-oc before i went to bed. Wake up the next morning to the comp sitting at a bsod, not a big deal just need to undo the oc settings. Get that done and then i start getting these wierd lockups and sys performance seemed really kinda bleh. Finally computer decided to just hate life and would get to the xp loading bar screen and bsod then reboot. Couldnt get it past that today so reformatted thinking that would help (had everything backed up). It did for a short while and then it failed on me again. Decided to run the windows debugger and it said memory_corruption.

BCCode was this.

CCode : 1000000a BCP1 : 00000005 BCP2 : 00000002 BCP3 : 00000001 bcp4 : 8050CB4A
OSver : 5_1_2600 SP : 3_0 Product : 768_1

Link to the dump. Dump.

Both sticks passed Memtest.

 

[dclive]

can you post results of !analyze -v pls?

If that's the only change, it's likely you'll need to get your hw vendor to replace the card, but let's see the analysis 1st.

 

[Skraeling]

do that soon as i get off work.

 

[Skraeling]

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 01904001
Arg3: 000006d2
Arg4: c0883000

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


BUGCHECK_STR: 0x1a_41284

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: wirelesscm.exe

LAST_CONTROL_TRANSFER: from 80523309 to 804f9f33

STACK_TEXT:
b5d87af4 80523309 0000001a 00041284 01904001 nt!KeBugCheckEx+0x1b
b5d87b2c 80523b8f 000006d2 01904000 c0600060 nt!MiLocateWsle+0xc1
b5d87b60 80523fa8 c000c820 01904000 00000000 nt!MiDeletePte+0x1fd
b5d87c28 805135b6 00000220 019bffff 00000000 nt!MiDeleteVirtualAddresses+0x164
b5d87c68 805d2706 013638c0 887669b8 88766c00 nt!MmCleanProcessAddressSpace+0x262
b5d87d08 805d28c8 c0000005 887669b8 00000000 nt!PspExitThread+0x680
b5d87d28 805d2aa3 887669b8 c0000005 b5d87d64 nt!PspTerminateThreadByPointer+0x52
b5d87d54 8054161c 00000000 c0000005 0012fee4 nt!NtTerminateProcess+0x105
b5d87d54 7c90e4f4 00000000 c0000005 0012fee4 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fee4 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiLocateWsle+c1
80523309 2b45f0 sub eax,dword ptr [ebp-10h]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiLocateWsle+c1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c1

BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c1

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

 

[Skraeling]

Upon googling, it seems this is a file accociated with my D-link wireless nic. At least thats my conclusion... opinions?

 

[dclive]

Yep. So update the file and see if the issues go away.