BSODs/CTDs while gaming. :(

[dinesh.th14]

Hi,

I bought a new comp a few months ago with following specs.
Intel Core 2 duo E6600(2.4 Ghz)
2 GB kingston RAM(2*1 GB)
MSI P6N SLI
Nvidia 8800 GTS 640MB
250GB WD HDD

Initially, a few games(NFS:Most wanted and Doom3 at max gaphics) used to crash to the desktop or occasionally give out a BSOD(STOP msg : 7F or 50). I switched the RAM sticks and used them individually and found out that one of them was faulty coz with i didn't have any persistent problems(but i did have the occasional CTD/BSOD but very rarerly) with the other one. I got the faulty stick exchanged and i still experienced the crashes/BSODs with both of the sticks installed. I then just stuck to using the single stick that was working fine and had no problems till a few days ago when I ran DiRT(runs fine at full detail )
and i get a BSOD(PAGE FAULT at NON PAGE AREA). Now most of my other games also crash with a BSOD after a few minutes. I'm guessing the single proper RAM stick also has gone faulty. What i wanted to know was if they were becoming defective coz of a heating problem or if theres a problem with my motherboard. I still haven't run memtest yet, which i will soon.

I have attached a dump of the 7F STOP msg. Can anyone throw some light on the issue?

 

[peterdiva]

Try updating the sound drivers. That dump crashed at a sound driver with a (usually) hardware related bugcheck. Post some more dump files if it continues to crash.

BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : RtkHDAud.sys ( RtkHDAud+7b04f )
Image name: RtkHDAud.sys Timestamp: Wed Nov 15 14:34:28 2006 (455AB4F4)

 

[Tedster]

learn how to read minidumps. https://www.techspot.com/vb/topic31341.html

 

[howard_hopkinso]

There`s nothing in the thread you link to Tedster that would help anyone to learn to read minidumps effectively.

This link HERE is better. However, reading minidumps is a bit of a specialist subject and simply being able to see the output of a minidump won`t necessarily help, if the person has no experience of reading miniduimps.

Regards Howard

 

[dinesh.th14]

I've had around 4 crashes over the last week and i did read the mini dumps using windbg(Thanks for the links). Each of the crash was caused by a different application/module. They were

1.ntoskrnl.exe - got some basic info from google. Not really sure on what this is apart from that it is related to the bootup.
2.nv4_disp.dll - I have the latest drivers for my card.
3.RtkHDAud.sys - Updated the sound card drivers but still crashed later.

Windbg reported the minidump of another BSOD yesterday stating the possible cause to be 'memory_corruption'. Here's the bugcheck.

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, 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: 8051a0ab, address which referenced memory

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




WRITE_ADDRESS: 00000010

CURRENT_IRQL: 2

FAULTING_IP:
nt!MmCheckCachedPageState+3b1
8051a0ab ff4310 inc dword ptr [ebx+10h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 804e2420 to 8051a0ab

STACK_TEXT:
f7a1a520 804e2420 e0d20000 00000001 f7a1a64c nt!MmCheckCachedPageState+0x3b1
f7a1a568 804e3eb4 8663c008 f7a1a5a8 00001000 nt!CcMapAndRead+0x86
f7a1a5fc 805695ab 867131e8 f7a1a63c 00001000 nt!CcPinFileData+0x204
f7a1a670 f7285a43 867131e8 f7a1a6b0 00001000 nt!CcPreparePinWrite+0x93
f7a1a6f0 f7285ba1 e14d5210 e10083e0 00001fe0 Ntfs!LfsGetLbcb+0x5b
f7a1a704 f7285822 e14d5210 00000e40 e10083e0 Ntfs!LfsPrepareLfcbForLogRecord+0x4a
f7a1a734 f7285556 e14d5210 e10083e0 00000002 Ntfs!LfsWriteLogRecordIntoLogPage+0x5c
f7a1a810 f728507f e10083e0 00000002 f7a1a8d0 Ntfs!LfsWrite+0x2f7
f7a1a994 f72866a7 f7a1ac1c 86713e68 00000000 Ntfs!NtfsWriteLog+0x6a2
f7a1abe8 f7286ff4 f7a1ac1c 866a6100 00000000 Ntfs!NtfsCheckpointVolume+0xa82
f7a1ad7c 80537851 00000000 00000000 867c3420 Ntfs!NtfsCheckpointAllVolumes+0xd2
f7a1adac 805ce7d4 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7a1addc 805451ce 80537762 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmCheckCachedPageState+3b1
8051a0ab ff4310 inc dword ptr [ebx+10h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MmCheckCachedPageState+3b1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 434c50c7

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MmCheckCachedPageState+3b1

BUCKET_ID: 0xA_W_nt!MmCheckCachedPageState+3b1

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

Planning to memtest my memory over the weekend. But i was wondering if any of these symptoms point to any specific problem? I'd appreciate any help.

Thanks.