NT Server 4.0, Enterprise BSOD help
Stop: 0x0000000A (0x0000001C,0x00000002,0x00000001,0x80132238) IRQL_NOT_LESS_OR_EQUAL Address 80132238 has base at 80100000 ntoskrnl. exe Does anybody have any idea whats going on with this? The box is running interix 2.
Stop: 0x0000000A (0x0000001C,0x00000002,0x00000001,0x80132238)
IRQL_NOT_LESS_OR_EQUAL
Address 80132238 has base at 80100000 ntoskrnl.exe
Does anybody have any idea whats going on with this? The box is running interix 2.2 and the error seems to be stress related but there is no real pattern that I can detect. It happens about once a day. Swapped out NIC and RAM already - sent a full memory dump to the vendor for analysis but I'm not optimistic.
IRQL_NOT_LESS_OR_EQUAL
Address 80132238 has base at 80100000 ntoskrnl.exe
Does anybody have any idea whats going on with this? The box is running interix 2.2 and the error seems to be stress related but there is no real pattern that I can detect. It happens about once a day. Swapped out NIC and RAM already - sent a full memory dump to the vendor for analysis but I'm not optimistic.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Thanks for everyone's help.
Drivers were the first troubleshooting we went at.
I was able to debug the memory dump and got:
BugCheck A, {1c, 2, 1, 80132238}
Probably caused by : ntkrnlmp ( nt!MiDecrementCloneBlockReference+de )
Followup: MachineOwner
--------
and:
efe2fbdc 80132238 nt!KiTrap0E+0x284 (FPO: [0,0] TrapFrame @ efe2fbdc)
efe2fc68 80131285 nt!MiDecrementCloneBlockReference+0xde (FPO: [Non-Fpo])
efe2fcb4 80130f85 nt!MiDeletePte+0x29d (FPO: [Non-Fpo])
efe2fd74 801268db nt!MiDeleteVirtualAddresses+0x249 (FPO: [Non-Fpo])
efe2fe28 8019b6a0 nt!MmCleanProcessAddressSpace+0x21b (FPO: [Non-Fpo])
efe2fea4 8019b198 nt!PspExitThread+0x486
efe2feb0 8011b97d nt!P***itSpecialApc+0x1a (FPO: [5,0,1])
efe2feec 80141ba2 nt!KiDeliverApc+0x181 (FPO: [Non-Fpo])
efe2feec 4d00d2aa nt!KiExceptionExit+0x3a (FPO: [0,0] TrapFrame @ efe2ff04)
00d4dbb4 00000000 0x4d00d2aa
Now if only I knew what MiDecrementCloneBlockReference module was?
But I'm happy that the memory address from the blue screen and the stack call match.
I'm a little outta my element here, no real IT department and I run the intel. system (as a databases admin) on this box with little to no support (small company)
Drivers were the first troubleshooting we went at.
I was able to debug the memory dump and got:
BugCheck A, {1c, 2, 1, 80132238}
Probably caused by : ntkrnlmp ( nt!MiDecrementCloneBlockReference+de )
Followup: MachineOwner
--------
and:
efe2fbdc 80132238 nt!KiTrap0E+0x284 (FPO: [0,0] TrapFrame @ efe2fbdc)
efe2fc68 80131285 nt!MiDecrementCloneBlockReference+0xde (FPO: [Non-Fpo])
efe2fcb4 80130f85 nt!MiDeletePte+0x29d (FPO: [Non-Fpo])
efe2fd74 801268db nt!MiDeleteVirtualAddresses+0x249 (FPO: [Non-Fpo])
efe2fe28 8019b6a0 nt!MmCleanProcessAddressSpace+0x21b (FPO: [Non-Fpo])
efe2fea4 8019b198 nt!PspExitThread+0x486
efe2feb0 8011b97d nt!P***itSpecialApc+0x1a (FPO: [5,0,1])
efe2feec 80141ba2 nt!KiDeliverApc+0x181 (FPO: [Non-Fpo])
efe2feec 4d00d2aa nt!KiExceptionExit+0x3a (FPO: [0,0] TrapFrame @ efe2ff04)
00d4dbb4 00000000 0x4d00d2aa
Now if only I knew what MiDecrementCloneBlockReference module was?
But I'm happy that the memory address from the blue screen and the stack call match.
I'm a little outta my element here, no real IT department and I run the intel. system (as a databases admin) on this box with little to no support (small company)
Found these on the Windows help in relation to stress:
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q234540
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q298936
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q229703
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q235614
This interprets the bug check messages:
http://personal.cfw.com/~tkprit/stop/anatomy.html
These articles are in relation to multiple CPU's
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q142660
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q298936
You might also contact Compaq.
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q234540
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q298936
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q229703
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q235614
This interprets the bug check messages:
http://personal.cfw.com/~tkprit/stop/anatomy.html
These articles are in relation to multiple CPU's
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q142660
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q298936
You might also contact Compaq.