P Pablo Well-known member Joined May 9, 2014 Posts 73 Location Argentina May 31, 2014 #1 Hi guys, here I am coming again to learn from your expertise This PC is experiencing BSOD's with a month or two between one and the other... with no further delay here are the minidumps: View attachment Minidump.rar What could it be? lots of thanks from the southern part of the world
Hi guys, here I am coming again to learn from your expertise This PC is experiencing BSOD's with a month or two between one and the other... with no further delay here are the minidumps: View attachment Minidump.rar What could it be? lots of thanks from the southern part of the world
Jared Sysnative Staff, BSOD Kernel Dump Expert Joined Feb 3, 2014 Posts 1,591 May 31, 2014 #2 Given that your dump files are old, you're using Windows XP, the bugcheck code is unknown and we're using minidumps I cannot give too much information. But it your Realtek network driver is causing issues. Code: BugCheck 40000080, {86d37ad0, 86688cd8, 80549ae0, 1} Unable to load image Rtenicxp.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Rtenicxp.sys *** ERROR: Module load completed but symbols could not be loaded for Rtenicxp.sys Probably caused by : Rtenicxp.sys ( Rtenicxp+5fe1 ) It should be update here. Code: kd> lmvm Rtenicxpstart end module name f6270000 f6288280 Rtenicxp T (no symbols) Loaded symbol image file: Rtenicxp.sys Image path: Rtenicxp.sys Image name: Rtenicxp.sys Timestamp: Tue Aug 07 10:40:37 2007 (46B83E15) CheckSum: 00020208 ImageSize: 00018280 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Given that your dump files are old, you're using Windows XP, the bugcheck code is unknown and we're using minidumps I cannot give too much information. But it your Realtek network driver is causing issues. Code: BugCheck 40000080, {86d37ad0, 86688cd8, 80549ae0, 1} Unable to load image Rtenicxp.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Rtenicxp.sys *** ERROR: Module load completed but symbols could not be loaded for Rtenicxp.sys Probably caused by : Rtenicxp.sys ( Rtenicxp+5fe1 ) It should be update here. Code: kd> lmvm Rtenicxpstart end module name f6270000 f6288280 Rtenicxp T (no symbols) Loaded symbol image file: Rtenicxp.sys Image path: Rtenicxp.sys Image name: Rtenicxp.sys Timestamp: Tue Aug 07 10:40:37 2007 (46B83E15) CheckSum: 00020208 ImageSize: 00018280 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 May 31, 2014 #3 Hi, To further expand off of MooMoo's reply, 0x40000080 is the NDIS driver bug check for Windows 2000 and XP based systems. It's 0x7C on future generation OS'. ndis.sys (Network Driver Interface Specification driver) routine call. The Network Driver Interface Specification (NDIS) is an application programming interface (API) for network interface cards (NICs). The NDIS forms the Logical Link Control (LLC) sublayer, which is the upper sublayer of the OSI data link layer (layer 2). Therefore, the NDIS acts as the interface between the Media Access Control (MAC) sublayer, which is the lower sublayer of the data link layer, and the network layer (layer 3). The NDIS is a library of functions often referred to as a "wrapper" that hides the underlying complexity of the NIC hardware and serves as a standard interface for level 3 network protocol drivers and hardware level MAC drivers. Another common LLC is the Open Data-Link Interface (ODI). With that said, as MooMoo already stated, update your network drivers ASAP. Regards, Patrick
Hi, To further expand off of MooMoo's reply, 0x40000080 is the NDIS driver bug check for Windows 2000 and XP based systems. It's 0x7C on future generation OS'. ndis.sys (Network Driver Interface Specification driver) routine call. The Network Driver Interface Specification (NDIS) is an application programming interface (API) for network interface cards (NICs). The NDIS forms the Logical Link Control (LLC) sublayer, which is the upper sublayer of the OSI data link layer (layer 2). Therefore, the NDIS acts as the interface between the Media Access Control (MAC) sublayer, which is the lower sublayer of the data link layer, and the network layer (layer 3). The NDIS is a library of functions often referred to as a "wrapper" that hides the underlying complexity of the NIC hardware and serves as a standard interface for level 3 network protocol drivers and hardware level MAC drivers. Another common LLC is the Open Data-Link Interface (ODI). With that said, as MooMoo already stated, update your network drivers ASAP. Regards, Patrick