Stop Errors and Random Freezing

Microsoft Windows 7 professional 32-bit
August 4, 2010 at 05:03:18
Specs: Windows 7
Hi I have been trying to fix some random stop 0x7F, 0xD1 and 0xA errors as well as freezing but can't seem to figure out the cause.. I have taken it to a pc shop twice and they cant seem to get it to error, Initially the network card stopped working correctly so I disabled it in the bios, and then I disabled onboard sound too but still it's still freezing.

I was getting Blue Screens at the beginning but now it's simply freezing and telling me there has been a dmp created when I reboot, there was a thunderstorm which effected some electronics in near by houses (few hundred yards away) not sure if that's the cause as they can't reproduce it at the pc shop, they have run tests and loaded the machine up with the apps I usually use at home (when at home it crashes when there it doesn't)

they have also checked the ram in a different machine AND the graphics card in a different machine, If i can pin it down to the motherboard i'll just buy a new one, but im not sure if thats going to be wasted time and money as it may be more than one component and if it is i may as well build a new machine.

This crashes on both of my operating systems (one per hard drive) which are windows vista ultimate and windows 7 pro

This machine is several years old and has been great up until last month. Nothing has been installed recently except a NIC card

Last three dump files:
http://www.kaista.co.uk/other/wth_i...

Hope you guys can help, thanks for reading my post.

Specs:
CPU: Intel Pentium D CPU
Motherboard: ASUS P5DL2
Ram (3gb) Corsair 512x2 + Crucial 1Gbx2)


See More: Stop Errors and Random Freezing

Report •


#1
August 4, 2010 at 09:30:19
If BOTH OSes crash, that points to hardware to me. I analyzed your dmp files, but am getting Symbol errors.

Those dmp files were created in:

- What OS?
- What Service pack level in that OS?
- 64 or 32 bit OS?

Just another stupid saying...


Report •

#2
August 4, 2010 at 11:11:02
Hi sorry for missing such important details, Windows 7 Pro 32bit and Windows Vista Ultimate 32bit, completely up to date as far as windows updates (so latest Service Pack)

Report •

#3
August 4, 2010 at 15:46:32
Your *.dmp files seem to be Win7 files; the 080410-21062-01.dmp check says, Probably caused by : hardware.

#1

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


Loading Dump File

080410-21062-01.dmp

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x83006000 PsLoadedModuleList = 0x83145570
Debug session time: Wed Aug 4 06:16:50.093 2010 (GMT-5)
System Uptime: 0 days 0:00:12.859
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 871a3024, 0, 0}

Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
Probably caused by : hardware

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, MCA_ASSERT
Arg2: 871a3024, Address of WHEA_ERROR_RECORD structure
Arg3: 00000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
Arg4: 00000000, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the error

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


WHEA_ERROR_RECORD: !errrec ffffffff871a3024

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
80e3dcc4 830c91c5 871a3008 83163f88 83163f80 nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x316f63)
80e3dce4 830c9fe1 83163f80 871a3008 83163fb0 nt!RtlBaseAceType+0x9
80e3dd58 c2ad7e04 00000000 00000000 00000000 nt!RtlpSetSecurityObject+0x4a7
WARNING: Frame IP not in any known module. Following frames may be wrong.
80e3dd7c ffffffff 830bb0d5 c14be2fc 00000000 0xc2ad7e04
80e3dd80 830bb0d5 c14be2fc 00000000 00000000 0xffffffff
80e3dd98 00000000 00000000 00000000 00000000 nt!CmpFindSubKeyByName+0x8e


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_GenuineIntel_CPER_Sev_1

BUCKET_ID: 0x124_GenuineIntel_CPER_Sev_1

Followup: MachineOwner


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

#2:

080410-21203-01.dmp, says, Probably caused by : ntoskrnl.exe

Loading Dump File

080410-21203-01.dmp

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82c02000 PsLoadedModuleList = 0x82d41570
Debug session time: Tue Aug 3 10:16:10.061 2010 (GMT-5)
System Uptime: 0 days 0:01:07.842
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {abd24b54, ff, 1, 82c3a908}

Probably caused by : ntoskrnl.exe ( nt!IoReadDiskSignature+d0 )

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: abd24b54, memory referenced
Arg2: 000000ff, 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: 82c3a908, address which referenced memory

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


WRITE_ADDRESS: abd24b54

CURRENT_IRQL: 0

FAULTING_IP:
nt!IoReadDiskSignature+d0
82c3a908 89550c mov dword ptr [ebp+0Ch],edx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: p.exe

LOCK_ADDRESS: 82c841e0 -- (!locks 82c841e0)

Resource @ nt!PiEngineLock (0x82c841e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x82c841e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 82c3a908 to 82c3ab7b

STACK_TEXT:
abd24ad4 82c3a908 badb0d00 0000a6e8 00000000 nt!PipProcessStartPhase3+0x108
abd24b48 abd24b5c 87e68c28 87dd2de0 000040a0 nt!IoReadDiskSignature+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
abd24b58 8800f978 abd24ba0 82c9ca2f 87e68c28 0xabd24b5c
abd24b5c abd24ba0 82c9ca2f 87e68c28 000bf400 0x8800f978
abd24b60 82c9ca2f 87e68c28 000bf400 00000000 0xabd24ba0
abd24ba0 ffffffff abd24c2c 00000002 82c3a8cc nt!NtQueryInformationProcess+0x492
abd24bb8 85247320 ffffffff 00000030 00000000 0xffffffff
abd24bbc ffffffff 00000030 00000000 00054b84 0x85247320
abd24bc0 00000000 00000000 00054b84 82d3f760 0xffffffff


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!IoReadDiskSignature+d0
82c3a908 89550c mov dword ptr [ebp+0Ch],edx

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!IoReadDiskSignature+d0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cac3

FAILURE_BUCKET_ID: 0xA_nt!IoReadDiskSignature+d0

BUCKET_ID: 0xA_nt!IoReadDiskSignature+d0

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

Just another stupid saying...


Report •

Related Solutions


Ask Question