Windows 7 HELP & # 161; & # 161; several death errors

M

magoscar

New Member
[lang=es]hola, estos son los dos errores que tengo en mi ordenador, no encuentro de que archivo tengo el conflicto,si alguien me puediera ver que es lo que falla lo agradeceria mucho, gracias de antemano.


[FONT=Segoe UI, Arial]On Mon 03/01/2011 22:47:42 GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\010311-21122-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x858E3)
Bugcheck code: 0x50 (0xFFFFFFFFBFFFFFE9, 0x1, 0xFFFFFFFF830A2EFE, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntkrnlpa.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 26/12/2010 12:05:12 GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\122610-24429-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x322493)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86CE72D4, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.[/FONT][/lang]
 

Attachments

  • 010311-21122-01.dmp
    141.2 KB · Views: 362
  • 122610-24429-01.dmp
    128 KB · Views: 328
Last edited by a moderator:
Hello and Welcome. : )


The only driver you could update is Marvell Thor,

Code: 
mv61xx.sys   Thu Mar 19 23:47:19 2009
For the rest it's stop 0x124 which means hardware fault.


0x124_AuthenticAMD_PROCESSOR_BUS_PRV



Hope it doesn't spoil your Christmas,


5325632953_7465142bed_t.jpg













Crash Dumps:

Code: 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\DMP\010311-21122-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8303a000 PsLoadedModuleList = 0x83182810
Debug session time: Mon Jan  3 17:47:42.277 2011 (UTC - 5:00)
System Uptime: 0 days 2:10:39.853
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
......
2: 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: bfffffe9, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 830a2efe, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000002, (reserved)

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 831a2718
Unable to read MiSystemVaType memory at 83182160
 bfffffe9 

FAULTING_IP: 
nt!ObfDereferenceObjectWithTag+27
830a2efe f00fc118        lock xadd dword ptr [eax],ebx

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  FTCOMModule.ex

CURRENT_IRQL:  0

TRAP_FRAME:  a439da9c -- (.trap 0xffffffffa439da9c)
ErrCode = 00000002
eax=bfffffe9 ebx=ffffffff ecx=c0000001 edx=746c6644 esi=bfffffe9 edi=c0000001
eip=830a2efe esp=a439db10 ebp=a439dca0 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
nt!ObfDereferenceObjectWithTag+0x27:
830a2efe f00fc118        lock xadd dword ptr [eax],ebx ds:0023:bfffffe9=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 830805f8 to 830bf8e3

STACK_TEXT:  
a439da84 830805f8 00000001 bfffffe9 00000000 nt!MmAccessFault+0x106
a439da84 830a2efe 00000001 bfffffe9 00000000 nt!KiTrap0E+0xdc
a439db18 830a2ed0 c0000001 8325cda3 019aab08 nt!ObfDereferenceObjectWithTag+0x27
a439db20 8325cda3 019aab08 019aab08 00000000 nt!ObfDereferenceObject+0xd
a439dca0 8325cc56 00000000 001f0003 00000000 nt!ObInsertObjectEx+0x144
a439dcbc 8329b693 8926d440 00000000 001f0003 nt!ObInsertObject+0x1e
a439dd18 8307d42a 00000000 001f0003 00000000 nt!NtCreateEvent+0xba
a439dd18 771a64f4 00000000 001f0003 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
019aaaf8 00000000 00000000 00000000 00000000 0x771a64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObfDereferenceObjectWithTag+27
830a2efe f00fc118        lock xadd dword ptr [eax],ebx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!ObfDereferenceObjectWithTag+27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

FAILURE_BUCKET_ID:  0x50_nt!ObfDereferenceObjectWithTag+27

BUCKET_ID:  0x50_nt!ObfDereferenceObjectWithTag+27

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







Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\DMP\122610-24429-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8301a000 PsLoadedModuleList = 0x83162810
Debug session time: Sun Dec 26 07:05:12.730 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:13.306
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, 86ce72d4, 0, 0}

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, Machine Check Exception
Arg2: 86ce72d4, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8e397cc4 830e8fc5 86ce72b8 83181c28 83181c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8e397ce4 830e9def 83181c20 86ce72b8 83181c50 nt!WheapProcessWorkQueueItem+0x56
8e397d00 83087f2b 83181c20 00000000 85ba3020 nt!WheapWorkQueueWorkerRoutine+0x1f
8e397d50 8322866d 00000001 bc7c2109 00000000 nt!ExpWorkerThread+0x10d
8e397d90 830da0d9 83087e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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




Drivers:

Code: 
start    end        module name
8bf4a000 8bf92000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8c0a0000 8c0a9000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8bff7000 8c000000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8c03d000 8c060000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
8c6b6000 8c6be000   AtiPcie  AtiPcie.sys  Mon Aug 24 04:25:22 2009 (4A924E72)
8362e000 83636000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
83678000 83723000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8c691000 8c6b6000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
83636000 83678000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8c395000 8c3f2000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
8c6be000 8c6cb000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8c680000 8c691000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
8c6d6000 8c6df000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
8c6cb000 8c6d6000   dump_ataport dump_ataport.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
8c6df000 8c6f0000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
8c0dd000 8c0ee000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8c0a9000 8c0dd000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8c200000 8c209000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8c64e000 8c680000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D)
8c562000 8c593000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
8342a000 83461000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8c646000 8c64e000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
80b9f000 80ba7000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
8c382000 8c395000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8c000000 8c025000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:34:00 2009 (4A5BC468)
83612000 8361d000   mcupdate mcupdate.dll Mon Jul 13 19:13:13 2009 (4A5BBF89)
8be0e000 8be24000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8bf92000 8bf9a000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8c357000 8c382000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8c636000 8c646000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8c060000 8c0a0000   mv61xx   mv61xx.sys   Thu Mar 19 23:47:19 2009 (49C311C7)
8c0ee000 8c1a5000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
8c1a5000 8c1e3000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
8301a000 8342a000   nt       ntkrpamp.exe Mon Jul 13 19:15:19 2009 (4A5BC007)
8c228000 8c357000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8bfcf000 8bfe0000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
8bfa5000 8bfcf000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8bff0000 8bff7000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
8be00000 8be0e000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8c3f2000 8c400000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8361d000 8362e000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
8c609000 8c636000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
8bf24000 8bf4a000   SCSIPORT SCSIPORT.SYS Mon Jul 13 19:45:55 2009 (4A5BC733)
8c5db000 8c5e3000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
8be28000 8bf1b000   sppc     sppc.sys     Sun Oct 11 16:54:02 2009 (4AD245EA)
8c419000 8c562000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E)
8bf9a000 8bfa5000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8c593000 8c59b380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
8bfe0000 8bff0000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
837a2000 837ed000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8c59c000 8c5db000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
83723000 83794000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
83794000 837a2000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8bf1b000 8bf24000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
Mini Kernel Dump does not contain unloaded driver list
 
You must log in or register to reply here.

Similar threads

Z
BSOD 0x124_4_GenuineIntel_PCIEXPRESS_UNSUPPORTED_REQUEST_IMAGE_GenuineIntel.sys
Replies
3
Views
2K
dianawolws
dianawolws
S
Help Needed: Facing Window Issue on Lenovo PC
Replies
1
Views
416
ChatGPT
ChatGPT
K
Windows 10 installation. Dozens of Driver errors
Replies
3
Views
429
ka1gt
K
J
System Shutdown error 6008 on all normal shutdowns
Replies
4
Views
980
Neemobeer
Neemobeer
X
Windows 10 Error 0x80070570 on Blu-ray recordable (BD-R) - zero-byte files dated 1974
Replies
6
Views
708
xio
X
Back
Top