[4thex]

Following up on cybertech's advice
"These are generally realated to hardware problems. Could be anything from your powersupply to faulty ram.

I suggest you post in the hardware forum for help with finding the cause."

I have posted the WinDbg details on my BSOD:


Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini111708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Nov 17 18:19:26.156 2008 (GMT+11)
System Uptime: 0 days 1:03:36.875
Loading Kernel Symbols
........................................................................... ..............................................................
Loading User Symbols
Loading unloaded module list
.......................
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {49, 2, 1, 80540990}

Probably caused by : ntkrpamp.exe ( nt!KefAcquireSpinLockAtDpcLevel+0 )

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

1: kd> !analyze -v
*************************************************************************** ****
* *
* 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: 00000049, 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: 80540990, address which referenced memory

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


WRITE_ADDRESS: 00000049

CURRENT_IRQL: 2

FAULTING_IP:
nt!KefAcquireSpinLockAtDpcLevel+0
80540990 f00fba2900 lock bts dword ptr [ecx],0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 804e194b to 80540990

STACK_TEXT:
bace3c8c 804e194b 80559698 8a111e50 00000000 nt!KefAcquireSpinLockAtDpcLevel
bace3d34 804e70fc 8b332288 80564820 8b332698 nt!CcPerformReadAhead+0x7d
bace3d7c 8053877d 8b332288 00000000 8b332698 nt!CcWorkerThread+0x150
bace3dac 805cff70 8b332288 00000000 00000000 nt!ExpWorkerThread+0xef
bace3ddc 805460ee 8053868e 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KefAcquireSpinLockAtDpcLevel+0
80540990 f00fba2900 lock bts dword ptr [ecx],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KefAcquireSpinLockAtDpcLevel+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

FAILURE_BUCKET_ID: 0xA_W_nt!KefAcquireSpinLockAtDpcLevel+0

BUCKET_ID: 0xA_W_nt!KefAcquireSpinLockAtDpcLevel+0

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

[possin]

Well got no idea what all that stuff means, but you need to find a way of isolating the problem, so start by removing/disconnecting unessential components, such as the Optical drive, secondary HDDs and any extra memory modules (you only need one).
Then if you have more than one memory module try them out one by one and see if it helps.

If you still have a problem, swap out the PSU for one you know works. If you still have problems then its time to really get your hands dirty and do the following:

1.remove the components from the case and lay them on a flat non metallic surface.
2. make sure you are still only using the essential components: Motherboard, processor, 1 stick of memory, HDD and PSU.
3. Switch on the machine by shorting out the power switch pins on the motherboard.
4. Swap out the remaining components 1 at a time until the problem stops. You will already have eliminated the PSU and memory at this point, so try the HDD and processor next, if its still a problem then its almost cirtainly your motherboard.

If you need any help swapping out parts and assembling/disassembling the PC see the animations on my site here: www.pcityourself.com/building