BSOD 0x0000007E STOP Error


G

Guest

Hello,

Anyone I need assistance on this; I turn on my PC booting in normal mode for
Windows XP SP2 Professional, it displays Blue Screen for 1 second and
automatically restarts, I tried Repair Installation and it was useless I'm
only able to boot on safe mode even after repairing, I disabled automatic
restart on system failure and it displayed this technical information strap
code:

STOP: 0x0000007E (0xC0000005, 0xF802B184, 0xF89FAD3C, 0xF89FAA38)
 
Ad

Advertisements

K

Kerry Brown

Have you recently added any new hardware? A bad driver often causes that
error.
 
G

Guest

No, I use a third-party driver when I enter windows setup to detect my hard
disk it's called ITE8212;

But, I don't think it's a hardware issue, Any Solutions ?
 
K

Kerry Brown

That error is almost always a hardware issue. Have you made any hardware or
software changes recently?
 
G

Guest

I could notice something when I boot up from Windows XP Setup Disk my HDD
used to be detected as 892100MB, now it's detected 871200MB, although the
result of the check on the 3 partitions was clean, and I can access the data
stored smoothly, Am I stuck ?

Any Suggestions ...
 
Ad

Advertisements

R

Ron Martell

Ahmed said:
Hello,

Anyone I need assistance on this; I turn on my PC booting in normal mode for
Windows XP SP2 Professional, it displays Blue Screen for 1 second and
automatically restarts, I tried Repair Installation and it was useless I'm
only able to boot on safe mode even after repairing, I disabled automatic
restart on system failure and it displayed this technical information strap
code:

STOP: 0x0000007E (0xC0000005, 0xF802B184, 0xF89FAD3C, 0xF89FAA38)

Is there any file or module name mentioned as part of the error
message?

Your error is SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
This indicates that a system thread generated an exception which the
error handler did not catch.

The error originated in whatever device driver or component that is
using memory address 0xF802B184

There is a way to possibly identify the device driver involved, but in
order to do so your computer has to be able to boot normally.

Hope this is of some assistance.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
G

Guest

Mr. Ron;

The BSOD STOP error don't diplay any devices or module names involved, but
there's a problem with starting the Network Associates McAfee Enterprise
services Although, I tried to stop the services from loading on startup and
booting normally, it was useless.

Thank You for Your Attention...
 
K

Kerry Brown

Troubleshooting stop errors is never easy. Here's a couple couple of links
that may help.

http://aumha.org/win5/kbestop.php

http://msdn2.microsoft.com/en-us/library/ms789516.aspx

In your case the 0xC0000005 parameter indicates a memory access violation.
The 0x7E Stop error means it was in an area of memory owned by a driver.
This usually means one of a few things. The hardware for the driver is bad.
The driver has a bug in it. The area of RAM where the driver is loaded is
faulty. The last two are the most common. Bad RAM is quite easy to test for
so that is the first place I'd start. Run a memory test program for several
hours, overnight is best.

http://www.memtest.org/

If the memory test passes then we are back to my original question. What is
the last hardware change you made? This could include a driver update or
adding new hardware like a printer, USB stick, card reader, digital camera,
whatever.
 
G

Guest

Mr. Ron, please tell me how can I identify the device driver involved, I'm
running a parallel windows on my system now.

Thank You
 
R

Ron Martell

Ahmed said:
Mr. Ron, please tell me how can I identify the device driver involved, I'm
running a parallel windows on my system now.

Identifying the cause of STOP errors using PSTAT & Excel

Many times when a STOP error occurs the information provided does not
specifically identify the application, device driver, or other
component file where the error occurred. However the 4 parameters
associated with the STOP (bugcheck) code will very often include one
that is the address where the error occurred. You first need to look
up the detailed information about the specific STOP code in order to
determine if the address is included and if so which of the 4
parameters has the address.

You can identify the meaning of each of the parameters for your
specific STOP code at:
http://msdn2.microsoft.com/en-us/library/ms789516.aspx

The second step in the procedure is to identify the addresses that
each active process is being loaded at. The PSTAT utility will
provide this information. On some systems the PSTAT utility may
already be present. Check this by opening a Command Prompt window
(Start - Run - CMD) and entering the following command:

PSTAT /?

If PSTAT is not on your computer you can download it free from
Microsoft. The download is called "Windows XP Service Pack 2 Support
Tools" and it is available from
http://www.microsoft.com/downloads/...76-9BB9-4126-9761-BA8011FABF38&displaylang=en
With PSTAT installed on your computer the next step is to open a
Command Prompt window again (Start - Run - CMD) and generate a report
with PSTAT. Because you need to copy part of the information from
this report (and only part) it is best to create the report as a text
file. In the Command Prompt window enter the following command:

PSTAT > C:\JUNK\PSTAT.TXT

You may change C:\JUNK\ to whatever drive and folder that you want to
save the report into.

Now open the saved file in Notepad. Start - Run - NOTEPAD
C:\JUNK\PSTAT.TXT

Scroll down the file, about 80% of the way to the end of the file and
you will find a head line:

ModuleName Load Addr Code Data Paged LinkDate

It is the information from this line to the end of the file that we
want to copy from this file and save as a separate file. Select the
block of text and copy it to the clipboard. Open a new notepad window
and paste the clipboard contents into it. Save this file under a
different name. I use PSTAT2.TXT and put it into the same C:\JUNK
folder.

Now launch Microsoft Excel and use File - Open to bring the PSTAT2.TXT
file into Excel. Excel will automatically parse the file into
columns. Once this is done use DATA - SORT to sort the entire
spreadsheet based on the value in Column B (Load Addr).

It is now a simple task to read down the addresses until you find the
highest value that is less than the address where the error occurred.
That module (name in column A) is the prime suspect for the cause of
your error.

Good luck



Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
Ad

Advertisements

G

Guest

ModuleName Load Addr
------------ ----------
ntdll.dll 7C900000
ntoskrnl.exe 804D7000
hal.dll 806EC000
win32k.sys BF800000
dxg.sys BF9C1000
framebuf.dll BFF50000
Fastfat.SYS F7843000
srv.sys F78B6000
ndisuio.sys F7BF9000
mrxsmb.sys F7EC9000
rdbss.sys F7F60000
afd.sys F7F8C000
tcpip6.sys F7FAE000
netbt.sys F7FE5000
ipnat.sys F800D000
tcpip.sys F802E000
ipsec.sys F8086000
VIDEOPRT.SYS F80B9000
dump_diskdump.sys F816D000
mouhid.sys F818D000
update.sys F8195000
hidusb.sys F81C9000
rdpdr.sys F81F1000
psched.sys F8222000
ndiswan.sys F8233000
ks.sys F824A000
USBPORT.SYS F826D000
b57xp32.sys F8290000
HDAudBus.sys F82AF000
mssmbios.sys F82F0000
ndistapi.sys F8320000
Mup.sys F8344000
sfdrv01.sys F835F000
sfvfs02.sys F8371000
NDIS.sys F8385000
Ntfs.sys F83B2000
KSecDD.sys F843F000
fltMgr.sys F8456000
SCSIPORT.SYS F8475000
atapi.sys F848D000
dmio.sys F84A5000
ftdisk.sys F84CB000
SPTD9997.SYS F84EA000
sptd.sys F8502000
pci.sys F85D5000
ACPI.sys F85E6000
isapnp.sys F8635000
MountMgr.sys F8645000
sfsync02.sys F8655000
VolSnap.sys F8665000
iteatapi.sys F8675000
disk.sys F8685000
CLASSPNP.SYS F8695000
i8042prt.sys F86C5000
imapi.sys F86D5000
cdrom.sys F86E5000
redbook.sys F86F5000
rasl2tp.sys F8705000
raspppoe.sys F8715000
raspptp.sys F8725000
msgpc.sys F8735000
termdd.sys F8745000
NDProxy.SYS F8755000
usbhub.sys F8775000
mvstdi5x.sys F8795000
netbios.sys F87A5000
HIDCLASS.SYS F87C5000
Cdfs.SYS F87E5000
PCIIDEX.SYS F88B5000
PartMgr.sys F88BD000
iteraid.sys F88C5000
PxHelp20.sys F88CD000
sfhlp02.sys F88D5000
BTHidMgr.sys F88DD000
usbehci.sys F890D000
mouclass.sys F8915000
fdc.sys F891D000
watchdog.sys F892D000
kbdclass.sys F893D000
dump_iteraid.sys F8955
point32.sys F895D000
flpydisk.sys F897D000
vga.sys F899D000
Msfs.SYS F89BD000
TDI.SYS F89C5000
Npfs.SYS F89D5000
ptilink.sys F89ED000
raspti.sys F89FD000
usbuhci.sys F8A15000
HIDPARSE.SYS F8A2D000
Ip6Fw.sys F8A35000
BOOTVID.dll F8A45000
tunmp.sys F8AF9000
rasacd.sys F8B09000
pfc.sys F8B15000
Dxapi.sys F8B19000
vbtenum.sys F8B2D000
KDCOM.DLL F8B35000
WMILIB.SYS F8B37000
dmload.sys F8B39000
swenum.sys F8B4F000
USBD.SYS F8B57000
Fs_Rec.SYS F8B5B000
Beep.SYS F8B5F000
RDPCDD.sys F8B63000
pciide.sys F8BFD000
Null.SYS F8C8D000
dxgthk.sys F8D0D000

Error
-------
STOP: 0x0000007E (0xC0000005, 0xF7FEB184, 0xF89BAD3C, 0xF89BAA38)


Mr. Ron; Sorry for disturbance, please help me identifying which module is
causing the error.

Thank You Again,
 
Ad

Advertisements

R

Ron Martell

netbt.sys F7FE5000
Error
-------
STOP: 0x0000007E (0xC0000005, 0xF7FEB184, 0xF89BAD3C, 0xF89BAA38)


Mr. Ron; Sorry for disturbance, please help me identifying which module is
causing the error.

Thank You Again,

In your error message it is parameter 2 that identifies the address at
which the exception occurred.

Module netbt.sys is loaded at F7FE5000 and the next higher address is
ipnat.sys at F800D000

inpnat.sys is part of the Windows XP builtin firewall. If you have
an alternative firewall product available you could try turning off
the Windows XP Firewll (Control Panel - Security) and see if that
resolves the error problem.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top