Re: Stop Message 0x7E
From: Joshua Smith [MSFT] (joshsm_at_online.microsoft.com)
Date: 01/25/05
- Next message: gguadav: "Outlook Express"
- Previous message: Kent P. Iler: "Windows Explorer recently started Crawling when I open it!"
- In reply to: JDizzle995: "Re: Stop Message 0x7E"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 25 Jan 2005 08:53:51 -0800
Hi JDizzle995,
You can try the following to get a better minidump when your system
bugchecks. This will help to determine what driver is causing the problem. I
need you to enable driver verifier.
Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit Finish
5) Reboot
There is a possibility that your computer will crash on reboot. If this
occurs hit F8 when rebooting just before the windows logo screen and select
the safe mode boot option. Follow the same steps above but on step 4 choose
'Select driver names from a list'; hit next; check the box next to any
driver where the provider is not Microsoft; hit Finish; reboot.
This will slow the performance of you computer a little while enabled but
will hopefully catch the driver causing corruption. Next time you crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
corresponding minidump (by default it is at c:\windows\Minidump ) my way.
If you have any questions or I didn't explain something well enough don't
hesitate to e-mail me back. Good Luck,
Joshua Smith
OpenGL Test Lab
Microsoft
-----
Get Secure! www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights
"JDizzle995" <JDizzle995@discussions.microsoft.com> wrote in message
news:C3886673-DD77-419F-808F-18C900C07623@microsoft.com...
> Ok, found the minidump folder, but there arent any new files since august
> 2004. Also when I open one, it's just garbage. Is there a specific font
> it
> should be in??
>
> I have error reporting on, however there are no Windows Error message pop
> up's to view the technical details of 0x7E. I also have to boot it safe
> mode
> to get to windows, if started in normal mode, I get the blue screen of
> death
> just before windows would normally load everytime, and cant competely boot
> up.
>
> I do however get a pop up error window for the System Restore problem...
> How do I go about fixing this problem? It lists 30 modules... Dont
> really
> know what that means.
>
> I checked the Event viewer, and saw several errors... 4 services unable to
> function due to "a hardware device not functioning." These services are
> AFD
> Networking Support Environment Service, TCP/IP Protocol Driver, NETBT
> Service
> and IPSEC Driver Service. These services not being able to start, also
> caused other services to have errors, which is what is reported in the
> Event
> Viewer. So the errors were reported like this.... "Xxxx service was not
> able
> to start due to NETBT Service not functioning properly. Reason for this
> error is: A hardware device not functioning."
>
> Any ideas??
>
> "David Candy" wrote:
>
>> It goes to your temp directory in a wierd named sub folder containg two
>> files (this is the part sent to MS). Minidumps also go into
>> c:\windows\minidumps. You do have error reporting turned on don't you? Dr
>> Watson is the debugger if it's not on. Don't boot into safe mode after a
>> crash (after all what do you actually do in safe mode? Reboot back to
>> normal?).
>>
>> Your stop message is an Access Violation (I looked up parameter1 of your
>> error and pasted the meaning at the top of my first post). System Restore
>> (that other error - what was it in full exactly?) also generating Access
>> Violations seems worthy of investagation. System Restore is a type of app
>> that could cause a Stop Error (most apps can't cause them - it's hardware
>> or drivers).
>>
>> --
>> ----------------------------------------------------------
>> http://www.uscricket.com
>> "JDizzle995" <JDizzle995@discussions.microsoft.com> wrote in message
>> news:5810B6BA-CDCF-4EB4-B98E-0BC502273C46@microsoft.com...
>> > Ok, so I can change it back to mini dump in the Advanced tab of the
>> > System
>> > Properties, but where does the dump go? As in, which file does it go
>> > into?
>> > I do not receive a windows error message once booted up in safe mode in
>> > regards to the "blue screen" error. The only time I receive a windows
>> > error
>> > message is when I try to open the System Restore Program, or click on
>> > the
>> > System Restore tab of the System Properties window. I can view the
>> > details
>> > of that error in the window provided, or in Dr Watson's log file... But
>> > I do
>> > not believe the 2 faults are directly linked, as I can remember there
>> > being
>> > intermittent problems with the System Restore tab in the past.
>> >
>> > "David Candy" wrote:
>> >
>> >> Don't do a full dump. Noone will want that file from you. It's just
>> >> too big.
>> >>
>> >> Understand I don't get blue screens. But you should get a dialog on
>> >> restart which has a details link. That will show you the file names. I
>> >> think it gets deleted after you choose send/don't send.
>> >>
>> >> If the problem is known the dialog will say there is more info after
>> >> sending and do you want to read it. This will have the fix.
>> >>
>> >> You can type in Help while online
>> >>
>> >> 0x7e or 0x0000007e (you might need both) - you should get around 10
>> >> hits.
>> >>
>> >> and it will tell you known problems that you can look at. EG
>> >>
>> >> SYMPTOMS
>> >> When you disconnect a CardBus Compact Flash (CF) adapter, your
>> >> computer may stop unexpectedly and you may receive the following stop
>> >> error in Pci.sys on a blue screen:
>> >>
>> >> So if you aren't disconnecting a CF adaptor then this isn't your
>> >> cause.
>> >>
>> >> You can also request support from MS via
>> >> http://oca.microsoft.com
>> >>
>> >> Read around on the site.
>> >>
>> >> You can also get a memory tester from here
>> >> http://oca.microsoft.com/en/windiag.asp
>> >>
>> >> Type in a command prompt
>> >>
>> >> cacls C:\WINDOWS\system32\Restore\rstrui.exe
>> >>
>> >> and check you have permissions.
>> >> --
>> >> ----------------------------------------------------------
>> >> http://www.uscricket.com
>> >> "JDizzle995" <JDizzle995@discussions.microsoft.com> wrote in message
>> >> news:552D9C74-CFBE-46EB-91E7-2C0163F19546@microsoft.com...
>> >> >I have not been able to locate where the memory gets dumped to. I
>> >> >have
>> >> > changed the option under the Advanced tab for system info to perform
>> >> > a full
>> >> > memory dump, and specified it to be placed in C:\memory.dmp But it's
>> >> > no where
>> >> > to be found. Once I get this issue resolved, how will I trace the
>> >> > address
>> >> > back the driver or device that the error is associated with?
>> >> >
>> >> > To answer a couple things listed in your reply... I have approx 110
>> >> > gig's
>> >> > of space in my hard drive. I have the most up-to-date BIOS my mobo
>> >> > manufacturer has. And I have installed as many of the drivers for
>> >> > the mobo
>> >> > as I can find to see if that was the problem. Another issue is the
>> >> > Windows
>> >> > Installer program wont let me use the auto install feature on the
>> >> > cd.
>> >> >
>> >> > Also, I think this my be part of the problem, when I try to use the
>> >> > System
>> >> > Restore on the start menu under System Tools, I get an error...
>> >> > When I check
>> >> > the Dr Watson log, It shows a 0xc0000005 Access Violation Error...
>> >> >
>> >> > I hate messing with software, please help me before I smash my
>> >> > computer into
>> >> > little pieces!!!!
>> >> >
>> >> > "David Candy" wrote:
>> >> >
>> >> >> #define STATUS_ACCESS_VIOLATION ((NTSTATUS)0xC0000005L)
>> >> >>
>> >> >> Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
>> >> >> The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check has a value of
>> >> >> 0x0000007E. This indicates that a system thread generated an
>> >> >> exception which the error handler did not catch.
>> >> >>
>> >> >> Parameters
>> >> >> The following parameters are displayed on the blue screen.
>> >> >>
>> >> >> Parameter Description
>> >> >> 1 The exception code that was not handled
>> >> >> 2 The address at which the exception occurred
>> >> >> 3 The address of the exception record
>> >> >> 4 The address of the context record
>> >> >>
>> >> >>
>> >> >> Cause
>> >> >> This is a very common bug check. To interpret it, you must identify
>> >> >> which exception was generated.
>> >> >>
>> >> >> Common exception codes include:
>> >> >>
>> >> >> a.. 0x80000002: STATUS_DATATYPE_MISALIGNMENT
>> >> >> An unaligned data reference was encountered.
>> >> >>
>> >> >> b.. 0x80000003: STATUS_BREAKPOINT
>> >> >> A breakpoint or ASSERT was encountered when no kernel debugger
>> >> >> was attached to the system. . 0xC0000005:
>> >> >> STATUS_ACCESS_VIOLATION
>> >> >>
>> >> >> A memory access violation occurred.
>> >> >>
>> >> >> For a complete list of exception codes, see the ntstatus.h file
>> >> >> located in the inc directory of the Windows DDK.
>> >> >>
>> >> >> Resolving the Problem
>> >> >> If you are not equipped to debug this problem, you should use some
>> >> >> basic troubleshooting techniques. Make sure you have enough disk
>> >> >> space. If a driver is identified in the bug check message, disable
>> >> >> the driver or check with the manufacturer for driver updates. Try
>> >> >> changing video adapters. Check with your hardware vendor for any
>> >> >> BIOS updates. Disable BIOS memory options such as caching or
>> >> >> shadowing.
>> >> >>
>> >> >> If you plan to debug this problem, you may find it difficult to
>> >> >> obtain a stack trace. Parameter 2 (the exception address) should
>> >> >> pinpoint the driver or function that caused this problem.
>> >> >>
>> >> >> If exception code 0x80000003 occurs, this indicates that a
>> >> >> hard-coded breakpoint or assertion was hit, but the system was
>> >> >> started with the /NODEBUG switch. This problem should rarely occur.
>> >> >> If it occurs repeatedly, make sure a kernel debugger is connected
>> >> >> and the system is started with the /DEBUG switch.
>> >> >>
>> >> >> If exception code 0x80000002 occurs, the trap frame will supply
>> >> >> additional information.
>> >> >>
>> >> >> If the specific cause of the exception is unknown, the following
>> >> >> should be considered:
>> >> >>
>> >> >> Hardware incompatibility. First, make sure that any new hardware
>> >> >> installed is listed on the Microsoft Windows Hardware Compatibility
>> >> >> List (HCL).
>> >> >>
>> >> >> Faulty device driver or system service. In addition, a faulty
>> >> >> device driver or system service might be responsible for this
>> >> >> error. Hardware issues, such as BIOS incompatibilities, memory
>> >> >> conflicts, and IRQ conflicts can also generate this error.
>> >> >>
>> >> >> If a driver is listed by name within the bug check message, disable
>> >> >> or remove that driver. Disable or remove any drivers or services
>> >> >> that were recently added. If the error occurs during the startup
>> >> >> sequence and the system partition is formatted with NTFS file
>> >> >> system, you might be able to use Safe Mode to rename or delete the
>> >> >> faulty driver. If the driver is used as part of the system startup
>> >> >> process in Safe Mode, you need to start the computer by using the
>> >> >> Recovery Console to access the file.
>> >> >>
>> >> >> If the problem is associated with Win32k.sys, the source of the
>> >> >> error might be a third-party remote control program. If such
>> >> >> software is installed, the service can be removed by starting the
>> >> >> system using the Recovery Console and deleting the offending system
>> >> >> service file.
>> >> >>
>> >> >> Check the System Log in Event Viewer for additional error messages
>> >> >> that might help pinpoint the device or driver that is causing bug
>> >> >> check 0x1E. Disabling memory caching of the BIOS might also resolve
>> >> >> the error. You should also run hardware diagnostics, especially the
>> >> >> memory scanner, supplied by the system manufacturer. For details on
>> >> >> these procedures, see the owner's manual for your computer.
>> >> >>
>> >> >> The error that generates this message can occur after the first
>> >> >> restart during Windows Setup, or after Setup is finished. A
>> >> >> possible cause of the error is lack of disk space for installation
>> >> >> and system BIOS incompatibilities. For problems during Windows
>> >> >> installation that are associated with lack of disk space, reduce
>> >> >> the number of files on the target hard disk. Check for and delete
>> >> >> any unneeded temporary files, Internet cache files, application
>> >> >> backup files, and .chk files containing saved file fragments from
>> >> >> disk scans. You can also use another hard disk with more free space
>> >> >> for the installation. BIOS problems can be resolved by upgrading
>> >> >> the system BIOS version.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> ----------------------------------------------------------
>> >> >> http://www.uscricket.com
>> >> >> "JDizzle995" <JDizzle995@discussions.microsoft.com> wrote in
>> >> >> message news:CDAAD3F4-BE25-4F18-BBE5-EFE9F62FB2BD@microsoft.com...
>> >> >> > I just upgraded my motherboard, and processor to an AMD 64
>> >> >> > 3200+ with an
>> >> >> > ECS EliteGroup 755 A2 mobo. I reused my hard drive Maxtor 160gb,
>> >> >> > Ram Pc3200
>> >> >> > 512mb, Nvidia GeForce 5200 Ultra 128mb video card. I have Xp
>> >> >> > home edition
>> >> >> > with SP2. When I started it up after installing the new hard
>> >> >> > ware, it booted
>> >> >> > normally until reaching the windows xp startup screen with the
>> >> >> > scrolling blue
>> >> >> > thing. Then got the blue screen of death and 0x7E stop message.
>> >> >> > The exact
>> >> >> > message looked like this
>> >> >> >
>> >> >> > Stop Message 0x0000007E: (0xC0000005, 0xF8F31750, 0xF9200430,
>> >> >> > 0xF920012C)
>> >> >> > It didnt list a driver or sys file associated with it. I was
>> >> >> > able to
>> >> >> > start in safe mode, and after checking the Dr Watson log file,
>> >> >> > showed an
>> >> >> > Access Violation from rstrui.exe. I dont know if the 2 errors
>> >> >> > are linked, im
>> >> >> > not a software guru by any means. I dont have an XP cd to
>> >> >> > reinstall with, so
>> >> >> > Formatting the hard drive is pretty much out of the question.
>> >> >> > Please reply
>> >> >> > if you can help... i miss my computer already!
>> >> >> >
>> >> >> > AMD 64 3200+
>> >> >> > ECS Elitegroup 755 A2 mobo
>> >> >> > 512 mb PC3200
>> >> >> > Nvidia GeForce 5200 Ultra 128mb
>> >> >> > Maxtor 160Gb HD
>> >> >> > XP Home Edition SP2
>> >> >> >
>> >> >>
>> >>
>>
- Next message: gguadav: "Outlook Express"
- Previous message: Kent P. Iler: "Windows Explorer recently started Crawling when I open it!"
- In reply to: JDizzle995: "Re: Stop Message 0x7E"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
