[jj1919]

I built my computer about a year ago, it ran fine for like 6 months then it started giving me all kinds of blue screens and seemingly random errors. Never really had time to fix it but now i need to and I've tried everything and cannot solve it. Ive ran memtest many times, No errors. Ive switched video cards, ive ran checkdisk and no errors, even tried a different hard drive, new sata cables, nothing. Ive taken out the sound card, and got a new powersupply and a new mtherboard from asus but my computer still crashes. And of course i have reinstalled windows many times. I get many different stop errrors but ive pasted the most recent minidump here. If anyone can help i would really appreciate it.

system specs:
asus p5n32-sli premium
c2duo e6600
2gb 800mhz corsair xms2 6400-c4
nvidia 7900gt
150 gb WD raptor hd
75 gb WD raptor hd
Audigy 2 sound card
600watt silverstone psu


MINIDUMP:

*** WARNING: Unable to verify timestamp for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {1000003, 1c, 0, 804fa0ff}



Probably caused by : win32k.sys ( win32k!zzzWakeInputIdle+26 )

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: 01000003, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, 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: 804fa0ff, address which referenced memory

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




READ_ADDRESS: 01000003

CURRENT_IRQL: 1c

FAULTING_IP:
nt!MmAccessFault+66f
804fa0ff 8b7904 mov edi,dword ptr [ecx+4]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: avp.exe

LAST_CONTROL_TRANSFER: from bf800f73 to 804fa0ff

STACK_TEXT:
b9330d10 bf800f73 00ffffff 00000001 00000000 nt!MmAccessFault+0x66f
b9330d2c bf80ced3 e22461a8 00000027 0076faec win32k!zzzWakeInputIdle+0x26
b9330d40 bf80109a 000005ff b9330d64 0076faec win32k!EXFORMOBJ::bXform+0x4b
b9330d50 b9330d64 8054086c 000005ff 00000027 win32k!ThreadUnlock1+0x5
WARNING: Frame IP not in any known module. Following frames may be wrong.
b9330d54 8054086c 000005ff 00000027 0076fb24 0xb9330d64
b9330d64 7c90eb94 badb0d00 0076fae4 002f33aa nt!RtlIpv4StringToAddressExA+0x149
b9330d78 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!zzzWakeInputIdle+26
bf800f73 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: win32k!zzzWakeInputIdle+26

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45f013f6

FAILURE_BUCKET_ID: 0xA_win32k!zzzWakeInputIdle+26

BUCKET_ID: 0xA_win32k!zzzWakeInputIdle+26

Followup: MachineOwner

[Advertisements]

Sorry, but this is the wrong area of the forum for your problem

[droidack]

Sorry, but this is the wrong area of the forum for your problem

[SRX660]

This can be either a memory problem or a driver problem. Did you install anything just before the problems started? Run Memtest86 and see if it is a memory problem. You could also try a repair install of windows.

http://www.geekstogo...ws-XP-t138.html

Beyond doing a repair install, you could be working on the computer for a long time trying to find the problem. I do not do this at my shop. A reinstall is faster and easier.

SRX660