"KA Spencer" <> wrote...
> "Kerry Brown" wrote:
>> What are the details of the BSOD?
>
> The crash is followed by a completely blank blue screen (unlike XP/2003
> etc
> which give the error details) BUT after the restart, the following are the
> error details:
>
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.256.6
> Locale ID: 2057
>
> Additional information about the problem:
> BCCode: 7f
> BCP1: 00000000
> BCP2: 00000000
> BCP3: 00000000
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 256_1
Hi Ken,
STOP 0x7F means "UNEXPECTED_KERNEL_MODE_TRAP". Something running in kernel
mode (eg a device driver) has hit an unrecoverable exception, and needs to
shut down. A crash is bad, but it is better than leaving the system running,
and letting the problem possibly corrupt data during a "graceful" shutdown.
It's better to pull the plug immediately.
The first parameter to the 0x7F STOP is 00000000 - this means the particular
type of unrecoverable exception was a "divide by zero" error. This is a
fatal error on all computers.
A divide by zero can be caused by memory corruption, or other hardware
problems; or software failures.
So far it seems to only affect specifi user accounts (administrtors). That's
a bit unusual - we'd need to conclude that an Administrator logon is
exercising the machine so it hits this error, while other user accounts do
not. So it could be things like: administrator is loading additional device
drivers; launching some application automatically at logon; or admin account
has a corrupt user profile. Exact cause would require some further problem
determination. Here are some things, I'd try:
- first, boot into safe mode (press F8 during bootup) then log in as
Administrator. Does system still crash?
- if not, create a *new* local account, as member of Administrators group
- now reboot normally, and log in as the new administrative user. Does this
new admin account also experience the problem?
- use a tool like "msconfig" (builtin) or autoruns
(
http://www.microsoft.com/technet/sys.../Autoruns.mspx) to
check what is being run automatically, when th administrator account logs
in. Disable everything which look suspicious.
-use Vista's memory test utility to run a memory test. Either boot from
Vista DVD and choose Repair opitions, or run "Mmeory Diagnostics Tool" (go
to Start, Search, start typing memor... , it will appear in the menu). If
memory test finds bad memory, replace your RAM.
- final step is pretty drastic so, wait until you've heard back from
Microsoft, and/or exhausted other avenues. The problem could be a corrupt
user profile. This is the file NTUSER.DAT in the user's home directory
(normally it is a hidden file). Log in as the new admin user, then delete
the "real" Administrator's NTUSER.DAT (actually, just move it to a safe
location, don't delete it altogether!!). Now log out and log in as teh
Administrator. The system will create a new blank Profile for the
Administrator. If the cause is something in the profile, it should no longer
occur with the fresh, clean profile. Noe that you will loose all customised
user settings (everything that was in HKEY_Current_User).
If Microsoft PSS are examining the dump they may be able to isolate the
specific cause - but, you'd need to have a Service Request open with PSS. If
you sent in the dump using the Windows Error Reporting tool, that still gets
analysed (automatically, by machine), but you won't get an individualised
reply. If they isolate a common bug they will produc a hotfix via Windows
Update.
Hope it helps,
--
Andrew McLaren
amclar (at) optusnet dot com dot au
Similar Threads
Linear Mode
