Minidump STOP 10000000a help requested.

Status
Not open for further replies.

Splitter

Posts: 11   +0
I've been having a nightmare with my machine for many more months than I would like to recall. The machine is an athlon64 3200+, Abit AV8, 1gig crucial ballistix. audigy 2 and an nvidia 6800 GT. I've tested the memory, thats all fine but still occassionally my machine will lock up with a BSOD. If anyone could shed some light one what is causing this i would be most appreciative. The only driver on my system that isnt quite up to date (because for some reason it wont detect my soundcard properly) is the audigy 2 driver.

I've attached the dumps to see if you can get anything out of them
Thank in advance.
 
Just had another BSOD, this time its a STOP 00000050 PAGE_FAULT_IN_NON_PAGED_AREA (or something)

minidump attached.
 
If your using SP2 switch back to SP1, worked for BSOD problems for me.
 
Hi,

It is memory corruption issue. Maybe it is overheat, faulty PSU or motherboard.


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: 43ea0862, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 806d0c03, address which referenced memory

Debugging Details:
------------------
OVERLAPPED_MODULE: kmixer
WRITE_ADDRESS: 43ea0862
CURRENT_IRQL: ff

FAULTING_IP:
hal!HalpApcInterrupt+93
806d0c03 0fa593feffffb8 shld [ebx+0xb8fffffe],edx,cl

CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 806d0866 to 806d0c03

STACK_TEXT:
8aea07d4 806d0866 badb0d00 00000000 8aea0948 hal!HalpApcInterrupt+0x93
8aea0844 804fa74f 83b20618 83b205d8 00000000 hal!KeReleaseInStackQueuedSpinLock+0x16
8aea0864 804f0498 83b20618 00000000 00000000 nt!KeInsertQueueApc+0x4b
8aea0898 f66e439a 80212004 83b205f0 862c4af0 nt!IopfCompleteRequest+0x1d8
8aea0948 804eddf9 8637c038 83b20598 00000030 VIDEOPRT!pVideoPortDispatch+0xd3e
8aea0958 bf85790e e52faa00 00000000 e52faa10 nt!IopfCallDriver+0x31
8aea0988 bf857988 8637c038 80212004 8aea0a04 win32k!GreDeviceIoControl+0x93
8aea09ac bfa41823 8637c038 80212004 8aea0a04 win32k!EngDeviceIoControl+0x1f
WARNING: Stack unwind information not available. Following frames may be wrong.
00000001 00000000 00000000 00000000 00000000 nv4_disp+0x6e823


CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
!chkimg -lo 50 -d !hal
806d0c04 - hal!HalpApcInterrupt+94

[ 85:a5 ]
1 error : !hal (806d0c04)

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT
STACK_COMMAND: kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
 
Thanks for the quick reply.
Just a few questions to get things straight in my head.

1: Is this definently a hardware problem (or could it be caused by a driver issue?)

2: Could this fault have been caused by video card ram or only the system ram / cpu cache

3: Could this also be caused by corruption in the windows page file as opposed to in the hardware?

The reason i ask is that the PSU, motherboard, CPU and memory have all been replaced in this machine since the problems began occurring (although those minidumps i posted only relate to this build). Also the system ram tested ok on a memtest last time i checked it, i will however be checking it again today.

Once again thanks for the quick reply.
 
Well my ram is crucial ballistix so i am currently running it at 2-2-2-6 @2.8 volts as it is posted. The last time i had this problem i relaxed the timings to the motherboard defaults and it revealed a TON of errors. Im hoping it isnt faulty ram again...i only just got this stuff RMAd
 
Retested the memory using memtest, multiple passes. No errors. The machine has blue screened another time, this time a 0000007e STOP.
 
Hi,

Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot. Reseat video card as well.
3. Downclock the ram. Check to default setting if you video card is overclocked.
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
For example : DIMM1 and DIMM2 do not have the same timing.
DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
7. Make sure that your PSU have adequate power to drive all the hardware including USB devices

If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
 
Thanks for the continued replies, its saving my machine from going out of the window at this very moment.

1: I avoided the heat issue before because the temperatures (cpu/ambient/video) are about normal. My CPU is around 39C idle. The case is about 28C idle (possibly lower) and the video card idles at about 55, rising to 60 under load. Since its a 6800GT i think thats fairly normal.
2: I'll do that tommorrow

3: This is an interesting one, i dont overclock anything so thats not an issue. But when i had a ram problem before crucial recommended downclocking the ram speeds to 3-3-3-8@2.6v. So i tried this only to find that windows wont even boot to the loading screen without getting a STOP 00000000C5.

4: Same again (although its a CM stacker case so it doesnt get that dusty)
5: Im sure the ram is compatible.
6:The memory is a matched pair and both are running at the same speeds.
7: The PSU is fine, i have made sure of this with a replacement.

I used that diagnostic method the last time, however, all that happened was that the system was stable with EITHER stick in by itself but unstable with both in (dual and single channel).

I'll post up when ive done the other things, please keep it coming though, you seem to know what youre talking about :)
 
Status
Not open for further replies.
Back