Still getting dumped on!

I've formatted my C drive and reinstalled windows but I'm still getting the BSOD. I've installed WinDbg and this is what it says about my dumps if anyone has any ideas:

Dump 1:

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.

An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates

that an unaligned data reference was encountered. The trap frame will

supply additional information.

Arguments:

Arg1: c0000005, The exception code that was not handled

Arg2: 8058b56e, The address that the exception occurred at

Arg3: f1013ac0, 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!MiUnsecureVirtualMemory+38

8058b56e 8b4b04 mov ecx,[ebx+0x4]

TRAP_FRAME: f1013ac0 -- (.trap fffffffff1013ac0)

ErrCode = 00000000

eax=00000000 ebx=00002000 ecx=85e5ce98 edx=e10da870 esi=00002000 edi=00000000

eip=8058b56e esp=f1013b34 ebp=f1013b40 iopl=0 nv up ei pl zr na po nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

nt!MiUnsecureVirtualMemory+0x38:

8058b56e 8b4b04 mov ecx,[ebx+0x4] ds:0023:00002004=????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 8058c7f1 to 8058b56e

STACK_TEXT:

f1013b40 8058c7f1 85e5cda8 00000000 bf8531ae nt!MiUnsecureVirtualMemory+0x38

f1013b4c bf8531ae 00002000 bf993588 e1b544e8 nt!MmUnsecureVirtualMemory+0xb

f1013b9c bf8725eb 00000000 bf993588 07050611 win32k!SURFACE::bDeleteSurface+0x157

f1013bac bf862069 07050611 e22a6700 bf84fc64 win32k!bDeleteSurface+0x18

f1013bb8 bf84fc64 07050611 e1b544e8 bc513e34 win32k!GreDeleteObject+0x8e

f1013bd0 bf86db39 e1b544e8 00000002 bf870446 win32k!_DestroyCursor+0xbe

f1013bdc bf870446 e22a6700 bf8787c1 bc51138c win32k!DestroyUnlockedCursor+0xb

f1013be4 bf8787c1 bc51138c 85fb6038 e23dfd18 win32k!HMDestroyUnlockedObject+0x18

f1013bfc bf87cc14 00000000 86121d10 00000000 win32k!DestroyProcessesObjects+0x68

f1013c24 bf877fc8 00000001 bf87eb6f 86121d10 win32k!xxxDestroyThreadInfo+0x22a

f1013c2c bf87eb6f 86121d10 00000001 00000000 win32k!UserThreadCallout+0x48

f1013c44 805ac50e 86121d10 00000001 85f783f8 win32k!W32pThreadCallout+0x3a

f1013cf0 805ac952 40010004 86121d10 804f8269 nt!PspExitThread+0x3e7

f1013cfc 804f8269 85f783f8 f1013d48 f1013d3c nt!PsExitSpecialApc+0x20

f1013d4c 8052d5da 00000001 00000000 f1013d64 nt!KiDeliverApc+0x1ad

f1013d4c 7ffe0304 00000001 00000000 f1013d64 nt!KiServiceExit+0x58

00eeffb0 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4

FOLLOWUP_IP:

win32k!SURFACE::bDeleteSurface+157

bf8531ae 397dfc cmp [ebp-0x4],edi

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!SURFACE::bDeleteSurface+157

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3f73195d

STACK_COMMAND: .trap fffffffff1013ac0 ; kb

BUCKET_ID: 0x8E_win32k!SURFACE::bDeleteSurface+157

Followup: MachineOwner




Dump 2:


PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except,

it must be protected by a Probe. Typically the address is just plain bad or it

is pointing at freed memory.

Arguments:

Arg1: eb6cf000, memory referenced.

Arg2: 00000001, value 0 = read operation, 1 = write operation.

Arg3: bf9067ca, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 00000000, (reserved)

Debugging Details:

------------------

Could not read faulting driver name

WRITE_ADDRESS: eb6cf000

FAULTING_IP:

win32k!MAPPER::MAPPER+6d

bf9067ca f3a5 rep movsd

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from bf851a5c to bf9067ca

STACK_TEXT:

eb6cdcf4 bf851a5c 00000000 eb6cded8 eb6cded0 win32k!MAPPER::MAPPER+0x6d

eb6cde3c 85f9cdc0 b22049b2 01c47fb8 790c6d00 win32k!ppfeGetAMatch+0x33

WARNING: Frame IP not in any known module. Following frames may be wrong.

85fd0f40 00000000 00000000 00000000 00000000 0x85f9cdc0

d01cbccc 00000000 00000000 00000000 00000000 nt!KiCallUserMode+0x4



FOLLOWUP_IP:

win32k!MAPPER::MAPPER+6d

bf9067ca f3a5 rep movsd

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!MAPPER::MAPPER+6d

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3f73195d

STACK_COMMAND: kb

BUCKET_ID: 0x50_W_win32k!MAPPER::MAPPER+6d

Followup: MachineOwner

Sorry if that was largely useless info, not sure exactly what bit has the relevant stuff.

Cheers
T

 

How often are you seeing all of these errors?


Multiple random stop errors in my experience has indicated a hardware problem, in the end.

 

Since formatting C and re-installing XP last night I've had 2. Prior to that I was getting between 0 and about 5 a day. The more opening and closing programs and files within programs eg Photoshop the more likely a crash would occur. Didn't sem to be any real pattern to it, I could leave WinAmp running streaming radio for hours or play Halo online for hours then at a random point it'd blue screen. This has all been since having a new graphics card and a new hard drive installed. As it's still doing it after a fresh install of XP I would agree that hardware is the likely culprit, I just need to figure out which device. It's definitely more stable than before but the fact it's done any at all tells me the system is still faulty somwhere.


I am shielded to the max so I am pretty sure this isn't a virus/trojan/worm issue. It is possible however that something could have been on my D or E partitions and it reinfested C. I have since formatted those as well to clear some files that wouldn't delete.


T

 

It sounds like a driver issue to me.
What graphics card? Can you try running it as a generic VGA device and see what happens?

 

My card is a Leadtek GeForce FX5700 with 256mb DDR. It also says Winfast A360 on the box but I didn't install the WInfast drivers when I reinstalled XP as I have the Nvidia drivers and they do their job ok. To be honest I think the Winfast stuff was partly responsible for some of my earlier crashes.

Er, how do I get it to run in VGA?

All my drivers should be ok, they are all up to date for the chipset and graphics as well. My gut feeling it's either Bios or hardware related but I have no idea what usually causes

T

 

(continued cos of stupid 3 minute limit)

...'Kernel Mode Exception Not Handled M', 'Page Fault in Non Paged Area' and 'Pnf List corrupt'. I was hoping someone here would be familiar with what those are caused by.

T

 

This sounds like a memory issue to me.

 

Ok thanks. Mmm, but memory where, the RAM or the memory on the graphics card? Replacing a stick of memory is a lot less expensive and awkward than a dodgy motherboard or graphics card, so I hope that is the cause.


T

 

yes, system memory. You may want to consider running a memory tester on the modules (it's software) to see if the RAM passes or fails.

MemTest
http://www.majorgeeks.com/download350.html

 

Got to about 700% and no errors for Memtest so maybe it isn't the RAM that's at fault. Are there any equally no brainer programs for checking the performance of the motherboard and graphics card I could try?

T