Windows XP Crashes

[AdamE]

Hey! Thanks for taking the time to help me with my computer issue. I have spent a bit of time searching these forums and am yet to find a thread with an issue identical to mine.


Summary of Issue

Over the past couple of days Windows XP has crashed (and displayed that horrible "blue screen") quite often. I have analysed the Minidumps and displayed the output below.

Error Outputs


-------------------------------------------------------------
ERROR 1
-------------------------------------------------------------

*******************************************************************************
* *
* 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: 00000010, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 805165d8, address which referenced memory

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


WRITE_ADDRESS: 00000010

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRestoreTransitionPte+64
805165d8 ff4910 dec dword ptr [ecx+10h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 805218a7 to 805165d8

STACK_TEXT:
f78bea90 805218a7 816ffea0 00000007 00000000 nt!MiRestoreTransitionPte+0x64
f78beaa8 80521eba e2f3b880 857efd30 857a25b0 nt!MiRemovePageFromList+0xd1
f78beac0 80514abd 00000400 000004c0 822c8398 nt!MiRemoveAnyPage+0xc8
f78beaf0 8051565b 00010000 857efd90 857efdc0 nt!MiResolveMappedFileFault+0x407
f78beb34 80515821 00000000 ce590000 c0672c80 nt!MiResolveProtoPteFault+0x195
f78bebb8 8051f4eb e2f3b880 ce590000 c0672c80 nt!MiDispatchFault+0xf1
f78bec24 8051a363 00000000 ce590000 00000000 nt!MmAccessFault+0x877
f78bec84 804e1a59 ce590000 00000000 80558698 nt!MmCheckCachedPageState+0x601
f78bed34 804e7072 865c8098 80563720 865c8c10 nt!CcPerformReadAhead+0x20b
f78bed7c 8053791b 865c8098 00000000 865c8c10 nt!CcWorkerThread+0x150
f78bedac 805ce84c 865c8098 00000000 00000000 nt!ExpWorkerThread+0xef
f78beddc 8054528e 8053782c 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRestoreTransitionPte+64
805165d8 ff4910 dec dword ptr [ecx+10h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiRestoreTransitionPte+64

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 43fa825b

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MiRestoreTransitionPte+64

BUCKET_ID: 0xA_W_nt!MiRestoreTransitionPte+64

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

-------------------------------------------------------------
ERROR 2
-------------------------------------------------------------

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_0

TRAP_FRAME: f78a6b54 -- (.trap fffffffff78a6b54)
ErrCode = 00000000
eax=000188e2 ebx=0000071d ecx=0000071d edx=00000000 esi=000188e2 edi=00000000
eip=f6e13a91 esp=f78a6bc8 ebp=000000f0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ALCXWDM+0x8ea91:
f6e13a91 f7f7 div eax,edi
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: fsx.exe

LAST_CONTROL_TRANSFER: from 805a11d1 to 804f9db6

STACK_TEXT:
f78a6af0 805a11d1 0000007f f6e13a91 000188e2 nt!KeBugCheck+0x14
f78a6b48 805413d4 f78a6b54 000000f0 f6e13a91 nt!Ki386CheckDivideByZeroTrap+0x41
f78a6b48 f6e13a91 f78a6b54 000000f0 f6e13a91 nt!KiTrap00+0x84
WARNING: Stack unwind information not available. Following frames may be wrong.
f78a6bc4 f78a6d01 f78a6c0c 864c4668 f78a6c04 ALCXWDM+0x8ea91
f78a6bc8 f78a6c0c 864c4668 f78a6c04 f6e04c3b 0xf78a6d01
f78a6d01 01000004 00000000 9c00002d 808643a0 0xf78a6c0c
f78a6d05 00000000 9c00002d 808643a0 0000000a 0x1000004


STACK_COMMAND: kb

FOLLOWUP_IP:
ALCXWDM+8ea91
f6e13a91 f7f7 div eax,edi

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ALCXWDM

IMAGE_NAME: ALCXWDM.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 44e555a1

SYMBOL_NAME: ALCXWDM+8ea91

FAILURE_BUCKET_ID: 0x7f_0_ALCXWDM+8ea91

BUCKET_ID: 0x7f_0_ALCXWDM+8ea91

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

My Thoughts

The first error occured when extracting Microsoft Flight Simulator X. I am stilll unsure as to what caused it. The error has yet to repeat itself.

The second error occurs when I press the 'bomb drop' button in Simulator X. If I uninstall/disable my Realtek AC'97 Audio driver then the error doesn't occur. I have downloaded and installed the very latest (audio) drivers and it crashes everytime.

Thanks again!

 

[howard_hopkinso]

Hello and welcome to Techspot.

I believe you problem is caused by Microsoft Flight Simulator. This is a common problem.

Check for any patches that might be available for the game, from the manufacturers website.

Regards Howard :wave: :wave:

 

[Sjbrand99]

Have you recently installed any hardware on your computer? Have you checked the drivers?

 

[AdamE]

Thanks for your replies. I am now getting these errors outside of Flight Simulator so I'm thinking it isn't the issue. They all seem to have something to do with "memory corruption".

I get the errors in Flight Simulator with both (RAM) sticks in, only one stick in, and only the other stick in. Can both sticks be faulty like that?

I also got two errors on Memtest the other day but I've run a test this morning with over 19 passes and the error isn't coming up again. I got a RAM error with Windows Memory Diagnostic too.

I then decided to run Memtest on each stick individually but it's not "erroring". I am going to run the Windows Memory Diagnostic tool on each stick by itself and see which one is causing the error. I need to know which one is failing so I can send it back to my PC supplier. How can it be that Flight Sim. errors on either or both? Argh.

Any help/ideas/suggestions?

 

[kirock]

How can it be that Flight Sim. errors on either or both? Argh.

It can if Flight Sim is the cause.
Just in case... try increasing your Vdimm voltage in the BIOS Advanced settings. Use the smallest increment it offers.

 

[AdamE]

Ok I tried increasing the voltage but it still runs into the 7F error. My CPU voltage is about 1.35V (in the BOIS), is that about normal for an Athlon X2 (dual-core) 4600+?


The error I received on Vista (this time not Flight Sim.) was:

------
BugCheck A, {ffffea80014fc200, 2, 0, fffff800018780c9}

Probably caused by : memory_corruption ( nt!MmDoesFileHaveUserWritableReferences+39 )
------

 

[kirock]

The error I received on Vista (this time not Flight Sim.) was:

------
BugCheck A, {ffffea80014fc200, 2, 0, fffff800018780c9}

Probably caused by : memory_corruption ( nt!MmDoesFileHaveUserWritableReferences+39 )
------

Oh you're using Vista, umm Beta version I guess? I was suggesting raising the voltage on the RAM which can help stabilize older RAM and reduce errors. If you're running beta Vista then who knows what the prob can be. That HAS to be speckled with bugs, some minor some major, but you said you got mem errors with memtest and windows memory dianostics....so I think you need to clear that prob up before venturing into Vista domain.

 

[AdamE]

Thanks for your reply kirock. Vista RC1 is incredibility stable on this computer, all of my drivers are compatible and I'm not running any other non-Windows programs. But for testing the RAM I go back to Windows XP. I just listed the Vista error to show that it's probably not a driver error (seeing as all my Vista drivers are different).

I ran the Windows Memory Diagnostic tool overnight, these are the results I obtained:

Error distribution by memory module:

Bank 'Bank 0/1': Slot 'A0': 7
Bank 'Bank 2/3': Slot 'A1': 26
Bank 'Bank 4/5': Slot 'A2': Empty
Bank 'Bank 6/7': Slot 'A3': Empty

Error distribution by error test

Stride6 (cache disabled): 33

Does this mean both sticks are faulty? I cannot get the tool to find errors when testing one stick at a time. Could my motherboard be at fault? Or maybe the slots themselves? Should I try the sticks in the third and fourth slots?

 

[kirock]

Does this mean both sticks are faulty?

Most likely. You can try to clean the copper fingers with an eraser, this sometimes helps. I think you need to get this resolved before you can diagnose the Sim problem. You can try increasing the Chipset voltage in the BIOS advanced settings. The Northbridge chipset is what controls the DIMM slots (RAM). You might want to also check the voltages on the PSU and make sure you have enough amps on the 5 and 12Volt outputs.

Your 1st post mentioned the Relatek AC97 audio drivers causing the prob, but when uninstalled the Flight Sim worked fine. Have you searched for updated mobo drivers too?

 

[AdamE]

I am currently downloading the latest motherboard driver (I'm not sure what my current version is or whether it's out of date).

Just noticed something. I am using 'FreshDiagnose' to checkout what hardware my computer has installed. I checked the sensor readings and found this:

VOLTAGES

CPU Core==> 1.38v
+2.5v ==> 1.82v
+3.3v ==> 3.28v
+5v ==> 4.92v
+12v ==> 12.35v
-12v ==> -12.6v
-5v ==> -5.25v
+5v Standby ==> 5.03v
VBat Battery ==> 3.07v

Does anyone know what the +2.5v connection does? Also, the diagnose tool tells me my memory module voltage is 2.9 volts but my MOBO detail page says it supports 1.8v memory modules.

Thanks!