Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

BCCode: 7f
BCP1: 0000000D
BCP2: 00000000
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1

The PC usually crashes while it sits idle or when I'm web browsing. The other use of the PC is for World of Warcraft, and it rarely crashes while I'm playing.

Any help would be greatly appreciated. Thank you.

Forgot to upload my minidump.

Attached Files

Mini010808-09.zip (17.2 KB, 13 views)

7F errors are often cause, but not always, corrupted memory. I suggest running MemTest to see if you have faulty RAM.

I wish that were the case, but the memory has been tested repeatedly. That was my first check. I've also replaced the power supply and my sound card to start with and updated all my drivers that I can think of.

Your PC is crashed with intel interrupt code d and it is general protection fault. 90% of the problem is related to hardware problem and 10% is related to device driver error. One minidump is insufficient to find out the culprit. Zip 5 to 6 minidump and attach the zip file here.

BTW hardware error does not mean faulty ram and it means ram. CPU, m/b, PSU or video card. Usually half of hardware error is related ram. You must aware that some faulty ram can pass memtest.

Thanks for the replies guys, I really appreciate the help. Here are some more mini-dumps.

Attached Files

	Mini010808-02.zip (17.9 KB, 8 views)
	Mini010808-04.zip (15.7 KB, 6 views)
	Mini010808-05.zip (17.4 KB, 6 views)
	Mini010808-06.zip (17.9 KB, 6 views)
	Mini010808-07.zip (16.6 KB, 6 views)

One more for good measure.

Attached Files

Mini010808-08.zip (17.3 KB, 6 views)

It is weried that all of the minidumps are crashed with the same symptom. Maybe this is firmware problem of the bios. You had better upgrade the BIOS of the motherboard.

Just out of curiosity, what are the minidumps saying? (I'm not sure how to read them)

FYI

Mini010808-02.dmp BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemFatalException+f )

Mini010808-04.dmp BugCheck 7F, {d, 0, 0, 0}
Probably caused by : portcls.sys ( portcls!KspShellTransferKsIrp+4c )

Mini010808-05.dmp BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemFatalException+f )

Mini010808-06.dmp BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemFatalException+f )

Mini010808-07.dmp BugCheck 7F, {d, 0, 0, 0}
Probably caused by : atapi.sys ( atapi!AtapiProcessInterrupt+1d6 )

Mini010808-08.dmp BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemFatalException+f )

Mini010808-09.dmp BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemFatalException+f )

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: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 9
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: Idle
CURRENT_IRQL: 6
LAST_CONTROL_TRANSFER: from 81c3604c to 81c49b47

STACK_TEXT:
81ce9b30 81c3604c badb0d00 00000000 81ce9c4c nt!KiSystemFatalException+0xf
81ce9bac 81c6be77 84c8f580 81ce9c68 00000008 nt!memcpy+0x5c
81ce9bf8 81c72ff8 81ce9c24 00000000 00000002 nt!EtwpLogKernelEvent+0x1fe
81ce9c44 81c74d40 00000f43 20004000 00000008 nt!EtwTraceTimedEvent+0xa5
81ce9c70 81c3726e 8913d005 00007101 8872dca0 nt!PerfInfoLogInterrupt+0x43
81ce9c70 8918f41e 8913d005 00007101 8872dca0 nt!KiInterruptDispatch+0x11e
81ce9d14 891901af 81cee610 869e4f94 81c9f353 intelppm!C1Halt+0x4
81ce9d20 81c9f353 8566d480 81cefac0 81cec700 intelppm!C1Idle+0x25
81ce9d50 81c37a02 00000000 0000000e 00000000 nt!PopIdleDefaultHandler+0x239
81ce9d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xa

I was just wondering, are there any simple programs that I can use to test my m/b and/or video card memory and tell if they're working properly?