Question Locked

Error Code, BSOD

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After all these yrs now I have one of these hits which seem to come and go.
Memory dump
0x0000007E (0xC0000005, 0x8056DE4C, 0xF78EEC54, 0xF78EE950)
the only thing that has changed in the last many yrs since I bought the puter is the video card, now a MSI NX8400GS, other then that the sys has worked very well, mainly doing Photoshop and CAD.
Thanks for any input.

11 replies

by captbilly1eye

See if these steps correct it:
http://support.microsoft.com/kb/330182

The most common cause for that error is a faulty device driver (ie. sound card, mouse, video card, etc.). Try updating drivers.

Additionally, in some cases, I've seen where this did the trick:
Boot to BIOS window using F2.
Look for Power Management.
Look for Load Default.
Highlight that option and press Enter.
Select Yes and Restart.

Let us know what does the trick.

by cybersecurity

Thanks, I was hoping to understand what the four parameters in the error message meant, that should I think tell the story behind the error, tho I'm not at all up on this...

by Former member

CAUSE
This issue may occur if a system thread generates an exception that the error handler does not catch. You receive this error message if one or more of the following conditions are true:
? If this issue occurs after the first restart during Windows Setup, or after the Setup program is finished, the computer may not have sufficient hard disk space to run Windows.
? If this issue occurs after the first restart during Windows Setup, or after Setup is complete, the computer BIOS may be incompatible with Windows.
? Incompatible video adapter drivers.
? A damaged device driver or system service.
? If the issue is associated with the Win32k.sys file, it may be caused by a third-party remote control program.

RESOLUTION
Where to start
Use the Windows Error Reporting tool
Click Send Error Report when you are prompted to send the error report to Microsoft.
? If a fix or a workaround is available, click More Information after you send the error report to Microsoft. This helps you obtain the fix or information about how to work around the issue
? If a fix or a workaround is not available, you can use the "Advanced Troubleshooting" section to try to resolve this issue. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help or contact support. For information about how to contact support, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/ (http://support.microsoft.com/contactus/)

Advanced troubleshooting
To troubleshoot this issue, use the following methods.

Method 1:

Make sure that you have sufficient hard disk space. For problems during Windows installation that are associated with a lack of available hard disk space, you must free space on your hard disk. Delete any unnecessary temporary files, Internet cache files, program backup files, and .chk files that contain saved file fragments from disk scans. You can also use another hard disk that has more free space for the installation.

Method 2:

Update the computer BIOS
Make sure that your computer BIOS revision is current. Contact the computer manufacturer to obtain the latest BIOS update for the computer. You may have to temporarily disable BIOS memory options such as caching or shadowing.

For information about how to contact the computer manufacturer, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
65416 (http://support.microsoft.com/kb/65416/) Hardware and software vendor contact information, A-K

60781 (http://support.microsoft.com/kb/60781/) Hardware and software vendor contact information, L-P

60782 (http://support.microsoft.com/kb/60782/) Hardware and software vendor contact information, Q-Z

Method 3:

Disable or update device drivers
View the Microsoft Hardware Compatibility List (HCL) to determine if the PCI devices in the computer are compatible with Windows XP. For information about the hardware compatibility list, visit the following Microsoft Web site
http://www.microsoft.com/whdc/hcl/default.mspx (http://www.microsoft.com/whdc/hcl/default.mspx)

Update the video adapter drivers to the latest versions. If a driver is listed by name in the Stop error message, disable or remove that driver. Disable or remove any drivers or services that you recently added. If the error occurs during the startup sequence and the system partition is using the NTFS file system, you may be able to use "safe mode" to rename or to delete the faulty driver. If the driver is used as part of the system startup process in safe mode, you must start the computer by using the Recovery Console to use the file. For more information about video adapter drivers in safe mode , click the following article number to view the article in the Microsoft Knowledge Base:
292460 (http://support.microsoft.com/kb/292460/) How to troubleshoot the video adapter driver in safe mode in Windows XP
If the problem is associated with the Win32k.sys file, the problem may be caused by a third-party remote control program. To remove the service, use the Recovery Console to start the computer, and then delete the specified system service file.

Method 4:

Remove unsigned drivers
If you cannot start Windows in safe mode, remove all drivers that are not digitally signed by Microsoft.

For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
316434 (http://support.microsoft.com/kb/316434/) How to perform advanced clean-boot troubleshooting in Windows XP

Method 5:

Remove all third-party drivers
In rare cases, you may be unable to determine which third-party driver causes the error. To troubleshoot this issue, move all third-party driver files from the Windows\System32\Drivers folder to a different location. To do this, follow these steps:

1. Use the Recovery Console to start the computer, or start the computer from a different installation of Windows if you have performed a parallel Windows installation.

2. Move all files from the Windows\System32\Drivers folder that do not have a creation date for Windows XP of 8/13/2001. If the computer relies on a third-party IDE or SCSI controller driver for correct operation, you must identify those driver files, and then leave them in the Windows\System32\Drivers folder.

3. Restart the computer.

4. Continue the Windows Setup program.
For more information about how to disable a service that prevents Windows from starting, click the following article number to view the article in the Microsoft Knowledge Base:
310602 (http://support.microsoft.com/kb/310602/) How to disable a service or a device that prevents Windows from starting

MORE INFORMATION
If the following conditions are true, the issue may be a hardware incompatibility with Windows XP because all the installed drivers are Windows XP drivers:
? You receive the STOP 0x7E error when you first start the computer.
? You receive the STOP 0x7E error after you run the Setup program.
? You did not install any third-party drivers during the installation of Windows.
However, if you receive the STOP 0x7E error after you upgrade from Windows 2000 Professional, or if you recently added a new hardware device, this issue may be an incompatible driver or an incompatible hardware device.

If you are still experiencing problems similar to the one described in this article, it may be a different problem than the one described in this article. This is a list of articles that discuss similar problems that you can review to try to address the problem:
315222 (http://support.microsoft.com/kb/315222/) A description of the Safe Boot Mode options in Windows XP
314058 (http://support.microsoft.com/kb/314058/) Description of the Windows XP Recovery Console
308041 (http://support.microsoft.com/kb/308041/) Resources for troubleshooting startup problems in Windows XP
For additional information about other troubleshooting steps that you can use, click the following article number to view the article in the Microsoft Knowledge Base:
314063 (http://support.microsoft.com/kb/314063/) Troubleshooting a Stop 0x0000000A error in Windows XP
If these articles do not help you resolve the problem or if you experience symptoms that differ from those that are described in this article, search the Microsoft Knowledge Base for more information. To search the Microsoft Knowledge Base, visit the following Microsoft Web site:
http://support.microsoft.com (http://support.microsoft.com/)
Then, type the text of the error message that you receive, or type a description of the problem in the Search Support (KB) field.
Just a little Knowledge on your problem...

Please post back if you have anymore problems or questions.

by rob miners

and you can read up on the Codes.

My Computer, Properties, Advanced, Startup and Recovery and untick Automatically restart. While you are there make sure that Small memory dump (64 KB) is selected and the output is %SystemRoot%\Minidump. The Blue Screen will dump the Minidump file.

Restart the PC normally as this will allow the PC to Blue Screen.

Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp

How to read the small memory dump files that Windows creates for debugging
http://support.microsoft.com/kb/315263

To download and install the Windows debugging tools, visit the following Microsoft Web site:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Instructions on using Windbg.

Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.
Close the workpage and save the Workspace information. This should lock in the Symbol path.
Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
Ctrl + a will let you copy the information and paste it into notepad.

Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
FAULTING_THREAD: 864f6a98

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: logon.scr

LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

STACK_TEXT:
f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585

STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb

FOLLOWUP_IP:
sgiul50!DrvBitBlt+585
bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: sgiul50!DrvBitBlt+585

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: sgiul50

IMAGE_NAME: sgiul50.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7

FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

by cybersecurity

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini051208-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 \WINDOWS\system32\ntoskrnl.exe, Win32 error 0n2
*** 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 3.3264) MP (2 procs) Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon May 12 16:57:50.500 2008 (GMT-4)
System Uptime: 0 days 1:51:36.236
*********************************************************************
* 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 \WINDOWS\system32\ntoskrnl.exe, Win32 error 0n2
*** 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
..................
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fefeff02, 2, 1, 804f2ffc}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+1bffc )

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

by rob miners

download the Symbols for XP and lock in the Symbol path. It seems that there should have been more information in this dump.

by cybersecurity

Note: this is a different MiniDump, wanted to see the change between the two..

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

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

Symbol search path is: C:\WINDOWS\Symbols\
Executable search path is:
Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3.3264) MP (2 procs) Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon May 5 21:18:30.843 2008 (GMT-4)
System Uptime: 1 days 7:00:37.464
Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
....................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....................
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fefeff02, 2, 1, 804f350a}

*** WARNING: Unable to verify timestamp for mssmbios.sys
Unable to load image Unknown_Module_b6083000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_b6083000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_b6083000
Probably caused by : Unknown_Module_b6083000 ( Unknown_Module_b6083000+1b0e3 )

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: fefeff02, 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: 804f350a, address which referenced memory

Debugging Details:
------------------

WRITE_ADDRESS: fefeff02

CURRENT_IRQL: 2

FAULTING_IP:
nt!CcInitializeCacheMap+44a
804f350a ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804f350a to 804e0a9c

STACK_TEXT:
a49de198 804f350a badb0d00 89df98d8 00000000 nt!KiTrap0B+0xb6
a49de20c 804ee3fc 898780e0 a49de2dc 00000000 nt!CcInitializeCacheMap+0x44a
a49de234 804ecf53 898780e0 00000000 00000000 nt!IoFreeMdl+0x9
a49de2bc b609e0e3 897d1890 00000000 00000000 nt!MmBuildMdlForNonPagedPool+0x71
WARNING: Stack unwind information not available. Following frames may be wrong.
a49de2e4 b609e259 8a1a8248 e149d6d0 00000001 Unknown_Module_b6083000+0x1b0e3
a49de33c b609e3f6 8a1a8248 8a11d200 00000001 Unknown_Module_b6083000+0x1b259
a49de358 b60941dd 8a1a8248 89d91118 00000001 Unknown_Module_b6083000+0x1b3f6
a49de3a8 b608cb7c 8a1a8248 897e2e98 89d91118 Unknown_Module_b6083000+0x111dd
a49de5f0 b608ad76 8a1a8248 895e2008 a49d0000 Unknown_Module_b6083000+0x9b7c
a49de634 804e13c9 89d91020 895e2008 897e2e98 Unknown_Module_b6083000+0x7d76
a49de634 00000004 89d91020 895e2008 897e2e98 nt!KiTrap0D+0x483
a49de700 804e13c9 8a189448 895e2008 895e2008 0x4
a49de700 00000000 8a189448 895e2008 895e2008 nt!KiTrap0D+0x483

STACK_COMMAND: kb

FOLLOWUP_IP:
Unknown_Module_b6083000+1b0e3
b609e0e3 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: Unknown_Module_b6083000+1b0e3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module_b6083000

IMAGE_NAME: Unknown_Module_b6083000

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0xA_W_Unknown_Module_b6083000+1b0e3

BUCKET_ID: 0xA_W_Unknown_Module_b6083000+1b0e3

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

0: kd> lmvm Unknown_Module_b6083000
start end module name
b6083000 b60a7000 Unknown_Module_b6083000 T (no symbols)
Loaded symbol image file: Unknown_Module_b6083000
Image path: Unknown_Module_b6083000
Image name: Unknown_Module_b6083000
Timestamp: unavailable (00000000)
CheckSum: 00000000
ImageSize: 00024000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

by rob miners

Description: mssmbios.sys is located in the folder C:\Windows\System32\drivers.

Some malware camouflage themselves as mssmbios.sys, particularly if they are located in c:\windows or c:\windows\system32 folder. Thus check the mssmbios.sys process on your pc whether it is pest or it may be corrupted.

Click Start, Run and type sfc /scannow and press Enter.

You may require your XP CD.

Update the Drivers for MSI NX8400GS

by cybersecurity

mssmbios.sys is a MS OS version 5.1.2600.2180 per the properties.
The MSI driver has been updated since I bought.
Can't run, sfc /scannow, I don't have a copy of XP SP3 on hand, only SP2.
One thing to note, I have a hardware firewall; D-link, and a software wall;Comodo, also running AVG and have never had a bug yet, tho I don't visit or open downloads from anyone till the system scans it as needed. I have tested the system walls using Gibson Research Corporation test site and from their data I'm doing very well.

by rob miners

that mssmbios.sys hasn't became corrupted. That was the point of running SFC.

This discussion is closed to new replies.