[garydigital]

Ive had multiple BSOD and complete computer shut offs the last few weeks errors in the mini dump include

IRQL_NOT_LESS_OR_EQUAL (a) - IMAGE_NAME: memory_corruption
PAGE_FAULT_IN_NONPAGED_AREA (50) - IMAGE_NAME: nv4_disp.dll
IRQL_NOT_LESS_OR_EQUAL (a) - IMAGE_NAME: win32k.sys
PFN_LIST_CORRUPT (4e) - IMAGE_NAME: ntoskrnl.exe
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) - IMAGE_NAME: win32k.sys

I get them at various times but mostly when Im working with imageing/compositing software like Adobe After Effects CS 3 (Usually rendering), or Illustrator, but i have also gotten them while watching a video and using openoffice. When I booted into safe mode to check stuff out i opened a command prompt and the computer completely shut off. I tried this 2 times with the same result. I have also had the computer completely shut off when doing ram checks but usually after an hr or 2. There is no warning when it does this just right to black.

Luckly I am able to complete my work by saving constantly and rendering on a laptop its much slower but gets the job done when i need it to. Even if i have to purchase a new computer it would be good to know if i can salvage this one as a backup or even keep it as my primary.


After reading the forums I have done the following:

1. Reinstalled windows (fresh install 3 weeks ago)
2. Updated to the latest Video Card Driver Nvidia
3. Run Memcheck86 on all ram (The ram checked out fine and ran the checks several times. BUT 2 times the computer shut off completely with our an error after about 1-2 hrs of running checks.
4. Put ram in different slots.
5. Removed ram for a lower total
6. Updated BIOS


I am currently running the following on my system
Motherboard: GA-M55SLI-S4 (Gigabyte) UPdated to F11j Bios
CPU: AMD Athlon 64 X2-4600 +
RAM: 4x 1GB G.Skill PC2-6400 DDR II (These are new chips i used to replace the original 2x 1GB chips which i thought was the problem)
Video Card: Nvidia GeForce 8800 GT
OS: Microsoft Windows XP Professional Version 5.1.2600 Service Pack 3 Build 2600
Drive: SATA 300 BG Internal (1 external 500 GB HD with its own power) (This is new also less then 6 months old, replaced an 30 BG SATA)

I am also running dual monitors (But i have turned one monitor off and tried to work) One of the monitors is a Wacom Cintiq.

Other Software that is on when i have these erros:
Zonealarm
AVG
Logitech Setpoint (Wireless Keyboard/Mouse Software)
Nvidia Control Panel
Wacom Tablet.exe BG Process for the Monitor

If I am Missing some information please let me know and ill post it asap

ALSO: I really appreciate the time some of you have taken to help noobs like me work through our computer problems. Thanks.


Ive attached a zip of random dump files


BELOW ARE 2 Of the DUMP FILES If you dont want to read the zip
-----------------
-----------------
-----------------
Loading Dump File [C:\WINDOWS\Minidump\Mini080309-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Aug 3 12:41:06.984 2009 (GMT-4)
System Uptime: 0 days 0:22:22.705
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
..........
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf80246e, b01639cc, 0}

Probably caused by : win32k.sys ( win32k!xxxUserYield+3f )

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

1: 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: bf80246e, The address that the exception occurred at
Arg3: b01639cc, 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:
win32k!xxxUserYield+3f
bf80246e 8b4010 mov eax,dword ptr [eax+10h]

TRAP_FRAME: b01639cc -- (.trap 0xffffffffb01639cc)
ErrCode = 00000000
eax=290af8a0 ebx=00000000 ecx=00000000 edx=00000000 esi=e1984900 edi=804fab14
eip=bf80246e esp=b0163a40 ebp=b0163a40 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k!xxxUserYield+0x3f:
bf80246e 8b4010 mov eax,dword ptr [eax+10h] ds:0023:290af8b0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: csrss.exe

LAST_CONTROL_TRANSFER: from bf80a4b2 to bf80246e

STACK_TEXT:
b0163a40 bf80a4b2 e1984900 bf9ab400 e1984b00 win32k!xxxUserYield+0x3f
b0163a5c bf89b736 00000002 8ad979b8 bf89e684 win32k!NtGdiBitBlt+0xad
b0163d30 bf8846e9 bf9ab400 00000001 b0163d54 win32k!xxxDesktopThread+0x179
b0163d40 bf8010ec bf9ab400 b0163d64 0072fff4 win32k!CommitReadOnlyMemory+0x8a
b0163d54 8054162c 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x5
b0163d6c 0072ffec 00000000 00000000 00000000 nt!RtlIpv4StringToAddressExW+0xad
WARNING: Frame IP not in any known module. Following frames may be wrong.
b0163d80 00000000 00000000 00000000 00000000 0x72ffec


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!xxxUserYield+3f
bf80246e 8b4010 mov eax,dword ptr [eax+10h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!xxxUserYield+3f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e87572

FAILURE_BUCKET_ID: 0x8E_win32k!xxxUserYield+3f

BUCKET_ID: 0x8E_win32k!xxxUserYield+3f

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

1: kd> lmvm win32k
start end module name
bf800000 bf9c2f80 win32k M (pdb symbols) c:\windows\symbols\sys\win32k.pdb
Loaded symbol image file: win32k.sys
Image path: win32k.sys
Image name: win32k.sys
Timestamp: Fri Apr 17 08:26:26 2009 (49E87572)
CheckSum: 001C50F1
ImageSize: 001C2F80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4


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


Loading Dump File [C:\WINDOWS\Minidump\Mini080309-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Aug 3 10:39:14.906 2009 (GMT-4)
System Uptime: 0 days 0:21:10.625
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image parport.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for parport.sys
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 0, a988fcc8, a988f9c4}

Probably caused by : parport.sys ( parport!PptPdoThread+6b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 00000000, The address that the exception occurred at
Arg3: a988fcc8, Exception Record Address
Arg4: a988f9c4, Context Record Address

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


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

FAULTING_IP:
+7b
00000000 ?? ???

EXCEPTION_RECORD: a988fcc8 -- (.exr 0xffffffffa988fcc8)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000000
Attempt to execute non-executable address 00000000

CONTEXT: a988f9c4 -- (.cxr 0xffffffffa988f9c4)
eax=00590000 ebx=00000000 ecx=00000000 edx=00000000 esi=8ab88088 edi=804faeb6
eip=00000000 esp=a988fd90 ebp=a988fdac iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

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

EXCEPTION_PARAMETER1: 00000008

EXCEPTION_PARAMETER2: 00000000

WRITE_ADDRESS: 00000000

FOLLOWUP_IP:
parport!PptPdoThread+6b
b75424d3 ?? ???

FAILED_INSTRUCTION_ADDRESS:
+297952f00aadfdc
00000000 ?? ???

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from b75424d3 to 00000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
a988fd8c b75424d3 8ae58e70 00000000 897cc818 0x0
a988fdac 805cff70 8ab88200 00000000 00000000 parport!PptPdoThread+0x6b
a988fddc 805460ee b7542468 8ab88288 00000000 nt!IopQueryReconfiguration+0x23
a988fdf8 00000000 00000000 00000000 00001f80 nt!ExpRemovePoolTracker+0x7b


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: parport!PptPdoThread+6b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: parport

IMAGE_NAME: parport.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48025389

STACK_COMMAND: .cxr 0xffffffffa988f9c4 ; kb

FAILURE_BUCKET_ID: 0x7E_NULL_IP_parport!PptPdoThread+6b

BUCKET_ID: 0x7E_NULL_IP_parport!PptPdoThread+6b

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

[Elvandil]

I'm still voting RAM (and then maybe hard drive).

MemScope (Floppy and CD images.)
Roadkil's RAM Test
Microsoft Memory Test (floppy or CD ISO image)
Memtest86

If you have enough memory sticks, you can test them by removing one at a time and see if the problem disappears.

If you are running Vista, tap F8 on boot and choose the memory diagnostic, or if you can boot up, go to Start > Search and type:

mdsched.exe

Choose to run a memory diagnostic on next boot. Or, you can boot from the DVD and run it from there.

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

Free Hard Drive Testing Applications:
Manufacturer's Tests
Victoria for DOS
Victoria for Windows (Both versions of Victoria are among the best and most thorough tests available.)
HD Tune
CheckDisk 1.03 (Marks bad sectors as unusable.)
HDAT2 (Diagnostics and bad sector recovery)
MHDD Low-level Diagnostics
Bootable Hitachi Drive Fitness Test Floppy or CD Image (works on most drives)

Hard Drive Manufacturers' Diagnostic Utilities Links:
TachTech
BleepingComputer

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

Heat can mimic the symptoms of memory problems. What temps do you see usually? If there is a hardware monitor in your BIOS setup, check the temp immediately fater a crash or shutdown.

[garydigital]

Thanks for the other mem test software. I did use the Windows Mem test i forgot I was using the Ultimate Boot CD. I got a 404 error when trying to download Memscope but found v1.1 on another site. Ill use the other 2 in the morning and report back.

Also as an addendum A friend told me to look in the System Information for win XP and look at any conflicts where i found the following


Memory Address 0xF0000000-0xF3FFFFFF PCI standard PCI-to-PCI bridge
Memory Address 0xF0000000-0xF3FFFFFF NVIDIA GeForce 8800 GT

I/O Port 0x0000A000-0x0000AFFF PCI standard PCI-to-PCI bridge
I/O Port 0x0000A000-0x0000AFFF NVIDIA GeForce 8800 GT

I/O Port 0x00000000-0x00000CF7 PCI bus
I/O Port 0x00000000-0x00000CF7 Direct memory access controller

I/O Port 0x000003C0-0x000003DF PCI standard PCI-to-PCI bridge
I/O Port 0x000003C0-0x000003DF NVIDIA GeForce 8800 GT

IRQ 22 Realtek AC'97 Audio
IRQ 22 Standard Dual Channel PCI IDE Controller

IRQ 23 Standard Dual Channel PCI IDE Controller
IRQ 23 NVIDIA Network Bus Enumerator

Memory Address 0xE0000000-0xEFFFFFFF PCI standard PCI-to-PCI bridge
Memory Address 0xE0000000-0xEFFFFFFF NVIDIA GeForce 8800 GT

IRQ 18 Texas Instruments OHCI Compliant IEEE 1394 Host Controller
IRQ 18 NVIDIA GeForce 8800 GT

Memory Address 0xA0000-0xBFFFF PCI bus
Memory Address 0xA0000-0xBFFFF PCI standard PCI-to-PCI bridge
Memory Address 0xA0000-0xBFFFF NVIDIA GeForce 8800 GT

I/O Port 0x000003B0-0x000003BB PCI standard PCI-to-PCI bridge
I/O Port 0x000003B0-0x000003BB NVIDIA GeForce 8800 GT

[Elvandil]

Conflicts like that are a relic of Windows 98. XP shares IRQ's and handles them much better. I have never seen a conflict in XP after working on 100's of machines. I'd consider that route to be unlikely.

[garydigital]

I finally finished the ram checks one at a time using memcheck86, the windows ram checker, and Memtest. All the ram chips passes with 2 or 3 good passes and no errors. I now am going to test each slot. But its monday and i have some work to do so it might take a but.

[Elvandil]

Hopefully it is a problem with something common and not the board. Please let us know how you make out. If memory tests OK, then the other tests will at least be accurate.

Did you run a mem test all night?

[garydigital]

I didnt run them all night. I ran most of them a few hrs between 1 and 2 for each chip. Usually while i ran sunday errands. If it passed at least 3 times i would switch chips. Ill be running the individual slots tonight when i get done with work. Ill let you know how it goes.

But I will say this, i ran the memtest86 a week ago with all 4 chips in and the computer completely shut off revealing no errors.

[Elvandil]

I suppose that's good enough. It's just that sometimes errors only start to show up when the machine is hot or been used for a while, but it sounds like you did it for long enough that it would have shown problems if it were going to.

But even with that, if it's possible, I'd try using one or two sticks at a time to make sure each stick (and slot) is working as it should.

[garydigital]

Sorry for the delay. I finally ran all the individual slots with one ram chip. All of them passed with 2-3 good runs. I even did it after the computer was on and working for a few hrs.

I even tried rendering some frames with a single chip and while it did render more frames about 200 it still crashed out.

So im still at a loss.

Thanks for everyone who was helping.

[garydigital]

Also i read that downclocking the ram might help? I didnt want to attempt this until i got some feedback. Actually i really dont want to do this at all because its out of the bounds of my computer knowledge.