I have exhausted all research on this problem.

I have two problems going on with my Dell Inspiron 9300 laptop.

1. BSOD's (attached)

2. Mouse freezes, in which I have to turn off the laptop.

any help would be appreciated..

thanks
Mike

The system does not contantly crash. Maybe twice a day. The mouse freezes only on occasion.

My system infomration is as follows:

Dell Inspiron 9300
CPU Type Mobile Intel Pentium M 750J, 1866 MHz (14 x 133)
Motherboard: Intel Alviso i915PM
Ram Speed, size and #sticks: DDR2-533 (266 MHz) 512mb 2 sticks
GPU: ATI Mobility Radeon X300 (M22)

OS: Windows XP Media Center Edition Service Pack 2 (build 2600)

Attached Files

	Mini060107-01.dmp (92.0 KB, 3 views)
	Mini060107-02.dmp (92.0 KB, 3 views)
	Mini061107-01.dmp (92.0 KB, 3 views)
	Mini061207-01.dmp (92.0 KB, 3 views)

i have not looked at the mini dmp yet but i ben working at a computer shop for about 2y and seen this happen a few times. if runing repare on the OS dose not help do burn in test it could be the ram

All your minidumps crash with a bugcheck of 7F. Faulty ram is a strong possibility.

0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause (many dozen KB articles exist for this error referencing specific hardware failures) and, of these, memory hardware failures are the most common.

Go and read this thread HERE and see if it helps you to identify the culprit.

Regards Howard

Your windows is crashed with intel interrupt code x'0c' (ie 12) and it is stack segment overrun fault. Expand the size of stack may fix your problem.

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
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: 0000000c, EXCEPTION_STACK_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

12 (0Ch): Stack Segment Overrrun Fault
A Stack Fault occurs with error code 0 if an instruction refers to memory beyond the limit of the stack segment. If the
operating system supports expand-down segments, increasing the size of the stack should alleviate the problem. Loading the
Stack Segment with invalid descriptors will result in a general protection fault.