Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD Error 0x40000080


  • Please log in to reply
5 replies to this topic

#1 Dreamspinner3

Dreamspinner3

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:24 PM

Posted 24 January 2012 - 07:12 AM

I have been getting the blue screen of death on my Windows Professional XP SP 3 machine. It gives me stop code 0x40000080. Each time it has happened, I've been doing something different: opening email, surfing the web. I have not installed any new hardware recently. I have four minidump files:

Mindump 1

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini010912-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Jan 9 07:52:07.828 2012 (UTC - 6:00)
System Uptime: 8 days 18:55:32.861

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Loading Kernel Symbols

Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 40000080, {8ac15ad0, 8a655828, 80550fdc, 1}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner


Minidump 2

icrosoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini012412-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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jan 24 05:22:08.625 2012 (UTC - 6:00)
System Uptime: 13 days 14:45:22.032
*********************************************************************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Loading Kernel Symbols

Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 40000080, {8ad53130, 8a5d52b0, b84db8dc, 1}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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


Minidump 3

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini122711-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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Dec 27 00:59:36.828 2011 (UTC - 6:00)
System Uptime: 0 days 10:05:55.809
*********************************************************************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Loading Kernel Symbols

Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 40000080, {8aceead0, 8a56db48, 80550fdc, 1}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( Unknown_Module_826f22a4>+3566857d )

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


Minidump 4

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini123111-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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Dec 31 09:00:43.609 2011 (UTC - 6:00)
System Uptime: 2 days 17:22:45.211
*********************************************************************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Loading Kernel Symbols

Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 40000080, {8ad63130, 8a3ebb48, b84db8dc, 1}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

My machine specs are:

Operating System: Windows XP Professional Service Pack 3
Antivirus Software: Avasta Free Antivirus
Firewall: Cunbelt Personal Firewall Free Edition
Computer: Custom
CPU: Intel Core 2 Quad Q9400 @ 2.66GHz
Motherboard: TP43D2-A7 Biostar Group
Ram: DDR2 4 Gigabytes
Storage: Seagate ST3320613AS 320 GB 72000 RPM SATA-300 & Seagate ST9500325AS 500 GB 5400 RPM SATA-150
Video Card: NVIDIA GeForce 9600 GT 512 MB
Soundcard: Creative Technology Ltd Sound Blaster X-Fi Xtreme Audio
Power Supply: Antec TruePower Trio 550W TruePower 2.0 ATX 12V v2.0 Power Supply 120mm Fan
Case: Cooler Master Silver Centurion 5 ATX Case

Can anyone help me figure out what is causing these errors?

Thanks!

Kim
Operating System: Windows XP Professional Service Pack 3
Antivirus Software: Avasta Free Antivirus
Firewall: Cunbelt Personal Firewall Free Edition
Computer: Custom
CPU: Intel Core 2 Quad Q9400 @ 2.66GHz
Motherboard: TP43D2-A7 Biostar Group
Ram: DDR2 4 Gigabytes
Storage: Seagate ST3320613AS 320 GB 72000 RPM SATA-300 & Seagate ST9500325AS 500 GB 5400 RPM SATA-150
Video Card: NVIDIA GeForce 9600 GT 512 MB
Soundcard: Creative Technology Ltd Sound Blaster X-Fi Xtreme Audio
Power Supply: Antec TruePower Trio 550W TruePower 2.0 ATX 12V v2.0 Power Supply 120mm Fan
Case: Cooler Master Silver Centurion 5 ATX Case

Edited by Dreamspinner3, 24 January 2012 - 07:35 AM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,554 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:24 PM

Posted 24 January 2012 - 07:49 AM

From what i see...that code seems to be related to network/connectivity problems.

I would try uninstalling the current ethernet/wireless drivers...then rebooting/reinstalling same.

Louis

#3 Dreamspinner3

Dreamspinner3
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:24 PM

Posted 24 January 2012 - 12:46 PM

Since I posted this message, I opened up the PC & discovered that the CPU heatsink fan is not spinning. It tries to spin but only jerks a bit. I am assuming it is gummed up with dust. Could this have caused these errors?

Once I get that part replaced, I will also try updating the network drivers.

Kim

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,554 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:24 PM

Posted 24 January 2012 - 12:53 PM

Overheating...is the enemy of anything that is electronic in nature and crammed into a small, closed space :).

Let's see how it runs after you clean and replace the CPU fan/heatsink.

Louis

#5 Dreamspinner3

Dreamspinner3
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:10:24 PM

Posted 24 January 2012 - 05:36 PM

Any recommendations on a new CPU cooler? My old one was a Arctic Cooling Freezer 7 Pro Socket LGA775 & the heatsink fan became bound up after only two years of use--but I usually leave my PC running 24/7. I am looking for one that is easy to install & already has the thermal paste applied to the heatsink. I plan on shopping tomorrow.

Kim

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,554 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:24 PM

Posted 24 January 2012 - 06:26 PM

I've never had any preference...I use the stock heatsink/fan provided in AMD processor kits, never had a problem.

I don't game and I've never seen a situation on any system calling for a heatsink/fan combo other than the ones I receive in retail CPU kits.

IMO...a lot things that some users get prissy about...are only for gameers, overclockers, and the like. For ordinary users, the standard items will hold their own quite well.

Just make sure you get one that suits your motherboard/CPU.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users