Hola!buenas tardes a todos.
Antes que nada deciros que soy nuevo en esto de los foros y, la verdad, es que cuando tienes algun problema informatico viene muy bien acudir a ellos aunque solo sea para ver si a a lguien le pasa lo que a ti y poder encontrar una solucion.
Mi problema es el siguiente, a ver si alguien me puede ayudar.
Desde que tengo puesto el ADSL ONO Banda ancha 4 megas, despues de estar unas horas puesto el ordenador simplemente con la mula descargando, el ordenador se me apaga solo y se reinicia y me indica que windows se ha recuperado de un error grave.Leyendo en otros foros e podido ver que es necesario ver los datos del archivo de error que se crea en Windows/Minidump, lo que me aparece en dicho archivo es lo siguiente:
MENSAJE DE ERROR CUANDO SE REINICIA SOLO:
BCCode : 100000d1 BCP1 : 00000006 BCP2 : 00000002 BCP3 : 00000000
BCP4 : F7696504 OSVer : 5_1_2600 SP : 2_0 Product : 768_1
C:\DOCUME~1\RAL~1\CONFIG~1\Temp\WER8658.dir00\Mini040207-01.dmp
C:\DOCUME~1\RAL~1\CONFIG~1\Temp\WER8658.dir00\sysdata.xml
----------------------------------------------------------------------
INFORMACION DEL VISOR DE SUCESOS:
Código de error
100000d1, parámetro 1 00000006, parámetro 2 00000002, parámetro 3 00000000,
parámetro 4 f7696504.
Para obtener más información, vea el Centro de ayuda y soporte técnico en
(link roto)
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 64 100000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 36 2c 20 000006,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 66 37 36 39 00, f769
0050: 36 35 30 34 6504
0000: 74737953 45206d65 726f7272 72452020
0010: 20726f72 65646f63 30303120 64303030
0020: 50202031 6d617261 72657465 30302073
0030: 30303030 202c3630 30303030 32303030
0040: 3030202c 30303030 202c3030 39363766
0050: 34303536
Details
Product: Windows Operating System
ID: 1003
Source: System Error
Version: 5.2
Symbolic Name: ER_KRNLCRASH_LOG
Message: Error code %1, parameter1 %2, parameter2 %3, parameter3 %4, parameter4 %5.
Explanation
A blue screen (Stop error) was reported. The message contains details about the error.
A matching event with Event ID 1001 might also appear in the event log.
This matching event displays information about the specific error that occurred.
User Action
No user action is required.
----------------------------------------------------------------------
INFORMACION DE MINIDUMP:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini040207-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Mon Apr 2 11:41:17.390 2007 (GMT+2)
System Uptime: 0 days 1:38:29.100
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
Unable to load image NDIS.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
Unable to load image Sacm2A.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for Sacm2A.sys
*** ERROR: Module load completed but symbols could not be loaded for Sacm2A.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {6, 2, 0, f7696504}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : Sacm2A.sys ( Sacm2A+cd8 )
Followup: MachineOwner
---------
**************************************************
EL ARCHIVO Sacm2A.sys es el Driver de mi modem
Mi modem es:
Scientific-Atlanta WebSTAR 2000 series Cable modem
Me ocurre unas 2 o 3 veces al dia, es desesperante que cada vez que me da por mirar la mula, a ver que tal se estan bajando las cosas, me encuentro conque el ordenador se ha reiniciado solo y se ha recuperado del error grave.
Ya he actualizado los drivers del modem que me descarge de la pagina oficial de webstar, he pasado el skandisk, he desfragmentado el disco duro y sigue pasando.
Para mas informacion, mi ordenador venia con un modem interno de 56K que he desinstalado y he abierto el ordenador y lo he quitado, por si daba conflicto y ahora cada vez que arranca el ordenador me dice: "nuevo hardware se ha encontrado" y que lo tengo que instalar y resulta ser el del modem interno de 56k que ya he quitado de dentro del ordenador!!!!!!!!!,que puedo hacer???alguien me puede ayudar?????agradeceria enormemente cualquier comentario o sugerencia al respecto.
MUCHAS GRACIAS!!!!!!
