Z
zzattack
After 10 passes memtest did not report any errors. Checkdisc ran fine too, and my winxp install is clean.
- Status
zzattack said:
chkdsk is not a complete, intelligent drive test nor is memtest perfect - So don't rule these things out.
I'd recommend taking a spin over to this thread https://www.techspot.com/vb/topic7602.html and run the appropriate drive diagnostc, as this is a very good possibility.
If it isn't your drive, then we'll need more information. Maybe your processor or graphics card is overheating, maybe it is a driver issue, maybe it is an incompatability issue, maybe it is a bad cable, maybe it is a failing power supply... you get the idea. The more information the better.
Hi,
The culprit is hardware. Probably it is faulty motherboard as one of the minidump crashes with cli (ie clear interrupt)
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bff50ff0, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804de9a4, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: bff50ff0
FAULTING_IP:
nt!KiServiceExit2+0
804de9a4 fa cli
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
CLI_FAULT_INSTR:
nt!KiServiceExit2+0
804de9a4 fa cli
LAST_CONTROL_TRANSFER: from 005642fd to 804de9a4
STACK_TEXT:
f2f55d64 005642fd badb0d00 8003f41c 005642fd nt!KiServiceExit2
WARNING: Frame IP not in any known module. Following frames may be wrong.
fb56c010 00000000 00000000 00000000 00000000 0x5642fd
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!KiServiceExit2+0
804de9a4 fa cli
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiServiceExit2+0
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: CLI_FAULT
BUCKET_ID: CLI_FAULT
The culprit is hardware. Probably it is faulty motherboard as one of the minidump crashes with cli (ie clear interrupt)
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bff50ff0, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804de9a4, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: bff50ff0
FAULTING_IP:
nt!KiServiceExit2+0
804de9a4 fa cli
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
CLI_FAULT_INSTR:
nt!KiServiceExit2+0
804de9a4 fa cli
LAST_CONTROL_TRANSFER: from 005642fd to 804de9a4
STACK_TEXT:
f2f55d64 005642fd badb0d00 8003f41c 005642fd nt!KiServiceExit2
WARNING: Frame IP not in any known module. Following frames may be wrong.
fb56c010 00000000 00000000 00000000 00000000 0x5642fd
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!KiServiceExit2+0
804de9a4 fa cli
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiServiceExit2+0
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: CLI_FAULT
BUCKET_ID: CLI_FAULT
Z
zzattack
Thanks for the replies
Rick and cpc2004,
Thanks for the help you gave so far.
As I found from running WD's tools nothing's wrong with my hdd. However, sometimes when I'm not doing anything with the pc, sometimes it makes a sound as if the power supply is gone (I think it's the HDD making the sound), it's some sort of a knicking sound. I think it might be either the HDD, PSU, or RAM. It's also quite occasionaly happening that I get ta BSoD when starting up iTunes.
Rick and cpc2004,
Thanks for the help you gave so far.
As I found from running WD's tools nothing's wrong with my hdd. However, sometimes when I'm not doing anything with the pc, sometimes it makes a sound as if the power supply is gone (I think it's the HDD making the sound), it's some sort of a knicking sound. I think it might be either the HDD, PSU, or RAM. It's also quite occasionaly happening that I get ta BSoD when starting up iTunes.
- Status
