Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Sign up or Login to participate.
|
|||||||
Begin your free trial now
Pay-as-you-go options starting at $10/user/month
Pay-as-you-go options starting at $10/user/month
The computer has rebooted from a bugcheck
|
|
Thread Tools | Search this Thread |
|
#1
|
|||
|
|||
|
The computer has rebooted from a bugcheck
Can any one be of help please?
"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a", could you please help in analyzing the root cause for this issue? Just for your reference I am posting the dump output: *************************************************************************** **** * * * Bugcheck Analysis * * * *************************************************************************** **** Use !analyze -v to get detailed debugging information. BugCheck A, {97, 2, 1, 80539f04} Probably caused by : memory_corruption ( nt!MiSessionOutSwapProcess+166 ) Followup: MachineOwner --------- 0: 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: 00000097, 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: 80539f04, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: unable to read from 80487e18 unable to read from 80487748 unable to read from 804875fc unable to read from 80479268 unable to read from 80487610 unable to read from 80487744 unable to read from 8047926c unable to read from 80487804 unable to read from 80487db8 00000097 CURRENT_IRQL: 2 FAULTING_IP: nt!MiSessionOutSwapProcess+166 80539f04 ff8698000000 inc dword ptr [esi+98h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: f7487cbc -- (.trap 0xfffffffff7487cbc) ErrCode = 00000002 eax=00000000 ebx=800654f0 ecx=80488044 edx=00000000 esi=ffffffff edi=80488044 eip=80539f04 esp=f7487d30 ebp=f7487d44 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!MiSessionOutSwapProcess+0x166: 80539f04 ff8698000000 inc dword ptr [esi+98h] ds:0023:00000097=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 80539f04 to 8046ccbc STACK_TEXT: f7487cbc 80539f04 00000206 80430237 00000001 nt!KiTrap0E+0x210 f7487d44 804426fb 8c214900 8c2149e0 8c2149a0 nt!MiSessionOutSwapProcess+0x166 f7487d78 80468591 8c2149a0 00000000 00000000 nt!MmOutSwapProcess+0x2f f7487d90 8046833c 00000000 00000000 00000000 nt!KiOutSwapProcesses+0x6b f7487da8 804593cc 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x5a f7487ddc 8046e476 804682e2 00000000 00000000 nt!PspSystemThreadStartup+0x54 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiSessionOutSwapProcess+166 80539f04 ff8698000000 inc dword ptr [esi+98h] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiSessionOutSwapProcess+166 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 40d1d1be IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0xA_nt!MiSessionOutSwapProcess+166 BUCKET_ID: 0xA_nt!MiSessionOutSwapProcess+166 Followup: MachineOwner --------- |
|
#2
|
|||
|
|||
|
Bad memory module is the likely cause. Try testing with only one memory module. If it works, retest with the other module.
|
|
#3
|
|||
|
|||
|
thanks for the update... will this help?? as this suggests to be a driver issue?
Minidump (sample) C:\Program Files\Support Tools>dumpchk.exe C:\WINNT\Minidump\Mini022009-02.dmp **************************************************************** ** ** Windows 2000 Crash Dump Analysis ** **************************************************************** * Filename . . . . . . .C:\WINNT\Minidump\Mini022009-02.dmp Signature. . . . . . .PAGE ValidDump. . . . . . .DUMP MajorVersion . . . . .free system MinorVersion . . . . .2195 DirectoryTableBase . .0x008a9000 PfnDataBase. . . . . .0x81000000 PsLoadedModuleList . .0x80487dc0 PsActiveProcessHead. .0x80489528 MachineImageType . . .i386 NumberProcessors . . .4 BugCheckCode . . . . .0x0000000a BugCheckParameter1 . .0x00000097 BugCheckParameter2 . .0x00000002 BugCheckParameter3 . .0x00000001 BugCheckParameter4 . .0x80539f04 ExceptionCode. . . . .0x80000003 ExceptionFlags . . . .0x00000001 ExceptionAddress . . .0x8046ccbc C:\Program Files\Support Tools>dumpchk.exe -v C:\WINNT\Minidump\Mini022009-02.dm p **************************************************************** ** ** Windows 2000 Crash Dump Analysis ** **************************************************************** * Filename . . . . . . .C:\WINNT\Minidump\Mini022009-02.dmp Signature. . . . . . .PAGE ValidDump. . . . . . .DUMP MajorVersion . . . . .free system MinorVersion . . . . .2195 DirectoryTableBase . .0x008a9000 PfnDataBase. . . . . .0x81000000 PsLoadedModuleList . .0x80487dc0 PsActiveProcessHead. .0x80489528 MachineImageType . . .i386 NumberProcessors . . .4 BugCheckCode . . . . .0x0000000a BugCheckParameter1 . .0x00000097 BugCheckParameter2 . .0x00000002 BugCheckParameter3 . .0x00000001 BugCheckParameter4 . .0x80539f04 ExceptionCode. . . . .0x80000003 ExceptionFlags . . . .0x00000001 ExceptionAddress . . .0x8046ccbc Module ntoskrnl.exe loaded at 0x80400000 Module hal.dll loaded at 0x80062000 Module BOOTVID.dll loaded at 0xf7410000 Module ACPI.sys loaded at 0xbffd8000 Module WMILIB.SYS loaded at 0xf75c8000 Module pci.sys loaded at 0xf7000000 Module isapnp.sys loaded at 0xf7010000 Module pciide.sys loaded at 0xf75c9000 Module PCIIDEX.SYS loaded at 0xf7280000 Module intelide.sys loaded at 0xf7500000 Module MountMgr.sys loaded at 0xf7288000 Module ftdisk.sys loaded at 0xbffbb000 Module Diskperf.sys loaded at 0xf7502000 Module dmload.sys loaded at 0xf7504000 Module dmio.sys loaded at 0xbff99000 Module PartMgr.sys loaded at 0xf7414000 Module twintail.sys loaded at 0xf7290000 Module xevtchn.sys loaded at 0xbff53000 Module XENUTIL.SYS loaded at 0xf7020000 Module atapi.sys loaded at 0xbff3d000 Module adpu160m.sys loaded at 0xf7030000 Module SCSIPORT.SYS loaded at 0xbff2a000 Module nfrd960.sys loaded at 0xf7040000 Module xenvbd.sys loaded at 0xbff06000 Module scsifilt.sys loaded at 0xf7298000 Module disk.sys loaded at 0xf72a0000 Module CLASSPNP.SYS loaded at 0xf7050000 Module nfrdperf.sys loaded at 0xf7060000 Module ibmhpf.sys loaded at 0xf72a8000 Module Dfs.sys loaded at 0xbfef3000 Module ino_flpy.sys loaded at 0xf72b0000 Module KSecDD.sys loaded at 0xbfee1000 Module Ntfs.sys loaded at 0xbfe5e000 Module NDIS.sys loaded at 0xbfe34000 Module Mup.sys loaded at 0xbfe1e000 Module i8042prt.sys loaded at 0xf7070000 Module mouclass.sys loaded at 0xf72e0000 Module kbdclass.sys loaded at 0xf72f8000 Module serial.sys loaded at 0xf7080000 Module serenum.sys loaded at 0xf74c0000 Module parport.sys loaded at 0xf7330000 Module cdrom.sys loaded at 0xf7348000 Module USBD.SYS loaded at 0xf7388000 Module uhcd.sys loaded at 0xf7360000 Module VIDEOPRT.SYS loaded at 0xf70a0000 Module cirrus.sys loaded at 0xf7090000 Module audstub.sys loaded at 0xf7627000 Module rasl2tp.sys loaded at 0xf70b0000 Module ndistapi.sys loaded at 0xbfde6000 Module ndiswan.sys loaded at 0xbed12000 Module TDI.SYS loaded at 0xbfdce000 Module raspptp.sys loaded at 0xf70c0000 Module ptilink.sys loaded at 0xf7368000 Module raspti.sys loaded at 0xf7390000 Module parallel.sys loaded at 0xf70d0000 Module rdpdr.sys loaded at 0xbecee000 Module ks.sys loaded at 0xbec98000 Module swenum.sys loaded at 0xf75ec000 Module update.sys loaded at 0xbec6d000 Module xennet.sys loaded at 0xbec5c000 Module usbhub.sys loaded at 0xf70e0000 Module NDProxy.SYS loaded at 0xf70f0000 Module EFS.SYS loaded at 0xf7358000 Module HIDPARSE.SYS loaded at 0xf72d0000 Module HIDCLASS.SYS loaded at 0xf7380000 Module hidusb.sys loaded at 0xf74bc000 Module mouhid.sys loaded at 0xbfdf6000 Module Fs_Rec.SYS loaded at 0xf751c000 Module Null.SYS loaded at 0xf763a000 Module Beep.SYS loaded at 0xf75ce000 Module mnmdd.SYS loaded at 0xf75d8000 Module Msfs.SYS loaded at 0xf7310000 Module Npfs.SYS loaded at 0xf7100000 Module rasacd.sys loaded at 0xf752a000 Module tcpip.sys loaded at 0xbead2000 Module msgpc.sys loaded at 0xf7110000 Module wanarp.sys loaded at 0xf7320000 Module netbt.sys loaded at 0xbeaaa000 Module netbios.sys loaded at 0xf7120000 Module Rp32Spin.sys loaded at 0xf7530000 Module rdbss.sys loaded at 0xbea75000 Module mrxsmb.sys loaded at 0xbe9fc000 Module dump_scsiport.sys loaded at 0xbec2c000 Module dump_XENUTIL.SYS loaded at 0xf7150000 Module dump_xevtchn.sys loaded at 0xbe96a000 Module dump_xenvbd.sys loaded at 0xbe9b0000 Module win32k.sys loaded at 0xa0000000 Module cirrus.dll loaded at 0xa018f000 Module ino_fltr.sys loaded at 0xbe403000 Module ofant.sys loaded at 0xbe3dd000 Module afd.sys loaded at 0xbe36f000 Module ParVdm.SYS loaded at 0xf757a000 Module TWGSYSIN.SYS loaded at 0xbebd4000 Module Fips.SYS loaded at 0xf71d0000 Module lm78nt.sys loaded at 0xbdf55000 Module srv.sys loaded at 0xbdea1000 Module pmemnt.sys loaded at 0xf7514000 Module Rp32Wire.sys loaded at 0xf7576000 Module termdd.sys loaded at 0xbdac9000 Module Cdfs.SYS loaded at 0xbdb61000 Module ipsec.sys loaded at 0xbd239000 Module TDTCP.SYS loaded at 0xf72e8000 Module RDPWD.SYS loaded at 0xbd16b000 |
|
#4
|
|||
|
|||
|
Basically, what it boils down to is that you have a nice computer with Windows 2000 Professional that has a hardware problem, most likely a memory failure. But it could be related to your CPU fan or power supply. Something that causes the system to quit because something is not working. Windows 2000 is not the easiest to figger out.
|
![]() |
| Similar Topics | ||||
| Topic | Replies | Forum | ||
He computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1
|
1 | Device Drivers | ||
The computer has rebooted from a bugcheck the bugcheck was: 0x100000d1
|
8 | Device Drivers | ||
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1
|
16 | Device Drivers | ||
The computer has rebooted from a bugcheck. The bugcheck was D1.
|
2 | Windows OS | ||
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1
|
4 | Windows OS | ||
| Thread Tools | Search this Thread |
|
|
All times are GMT -4. The time now is 09:57 AM.



He computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1