BSOD when wanna shut down

 Minidump.zip ( 22.78k ) Number of downloads: 26

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


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

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070719-1309
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c720
Debug session time: Sat Apr 5 20:23:51.218 2008 (GMT+8)
System Uptime: 0 days 0:00:56.906
Loading Kernel Symbols
...................................................................................................................
Loading User Symbols
Loading unloaded module list
...
Unable to load image ati2mtag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2mtag.sys
*** ERROR: Module load completed but symbols could not be loaded for ati2mtag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, f57f77b0, efd2d5ec, 0}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
*** WARNING: Unable to verify timestamp for ALCXWDM.SYS
*** ERROR: Module load completed but symbols could not be loaded for ALCXWDM.SYS
Probably caused by : hardware ( ati2mtag+237b0 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: f57f77b0, The address that the exception occurred at
Arg3: efd2d5ec, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
ati2mtag+237b0
f57f77b0 8f ???

TRAP_FRAME: efd2d5ec -- (.trap 0xffffffffefd2d5ec)
ErrCode = 00000000
eax=efd2d704 ebx=00000001 ecx=f1bfe214 edx=00000000 esi=862b5350 edi=85b0f000
eip=f57f77b0 esp=efd2d660 ebp=efd2d758 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ati2mtag+0x237b0:
f57f77b0 8f ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: csrss.exe

MISALIGNED_IP:
ati2mtag+237b0
f57f77b0 8f ???

LAST_CONTROL_TRANSFER: from f5ba567d to f57f77b0

FAILED_INSTRUCTION_ADDRESS:
ati2mtag+237b0
f57f77b0 8f ???

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
efd2d758 f5ba567d 85b0f000 862b5350 efd2d77c ati2mtag+0x237b0
efd2d768 f5bb14f1 862b5350 86354d58 00000001 ati2mtag+0x3d167d
efd2d77c ec3fd916 862b5350 86354d50 863fb550 ati2mtag+0x3dd4f1
efd2d83c 804ef17d 862b5038 86354d40 86354d40 VIDEOPRT!pVideoPortDispatch+0xcc4
efd2d84c 80582096 862b5020 85f40354 efd2d9e4 nt!IopfCallDriver+0x31
efd2d92c 805be14c 862b5038 00000000 85f402b0 nt!IopParseDevice+0xa12
efd2d9a4 805ba7d4 00000000 efd2d9e4 00000240 nt!ObpLookupObjectName+0x53c
efd2d9f8 80574f7b 00000000 00000000 70d75800 nt!ObOpenObjectByName+0xea
efd2da74 805758f2 efd2dbf0 00000000 efd2dbc8 nt!IopCreateFile+0x407
efd2dad0 805790b3 efd2dbf0 00000000 efd2dbc8 nt!IoCreateFile+0x8e
efd2db10 8054137c efd2dbf0 00000000 efd2dbc8 nt!NtOpenFile+0x27
efd2db10 8050061d efd2dbf0 00000000 efd2dbc8 nt!KiFastCallEntry+0xfc
efd2dba0 8057512a efd2dbf0 00000000 efd2dbc8 nt!ZwOpenFile+0x11
efd2dbe8 bf880ead efd2dc44 00000000 efd2dc68 nt!IoGetDeviceObjectPointer+0x40
efd2dcd8 bf8b0c10 00000001 00000001 00000001 win32k!XLATEOBJ_iXlate+0x19c8
efd2dd18 bf8b0b0a 00000001 00000008 efd2dd48 win32k!EngQuerySystemAttribute+0x13b6
efd2dd28 bf8b0a9b 00000001 efd2dd64 0015fd98 win32k!EngQuerySystemAttribute+0x12b0
efd2dd48 bf8b1e0f efd2dd64 8054137c 00050000 win32k!EngQuerySystemAttribute+0x1241
efd2dd50 8054137c 00050000 00000064 00000068 win32k!EngFindResource+0x399
efd2dd50 7c90eb94 00050000 00000064 00000068 nt!KiFastCallEntry+0xfc
0015fdb0 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
ati2mtag+237b0
f57f77b0 8f ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ati2mtag+237b0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: IP_MISALIGNED_ati2mtag.sys

BUCKET_ID: IP_MISALIGNED_ati2mtag.sys

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



last time my pc autorestart..
i also dunno wat happen , so
sifu plz help me out

This post has been edited by blue16: Jun 12 2008, 10:47 AM

no one can help me..

sad.. i dun get any reply..

Hopefully before posting a problem, please state in detail about the current system.

Ok, are you suffering from random reboots in Vista, right?

Check the following:
1) I presume you are using a laptop/desktop with dual-channel capability. Please confirm the RAM brand, size and type on all channels. If they are not the same, get the same type and size for the memory module in each channel.

2) Is the power supply unit is matching according to the motherboard specs? This is to make sure each component of the PC subsystems are working at optimum power consumption.

3) Is there possible misconfiguration of your IDE/ATA hard disk channels? If you have two IDE/ATA devices that are sharing the same channel, make use one device is a Master and the other device is a Slave. This is to avoid possible conflicting direct memory access (DMA) in your HDD driver.

4) Reinstall the drivers if you have recently installed a new hardware. This is your main problem (VISTA_DRIVER_FAULT) when an unknown process "@µ‚" (wierd process name, I guess) tries to access a hardware with a faulty driver. If you know the driver, you can rollback the driver in the System Hardware properties of that hardware with the faulty driver. If you are unsure, try the System Restore and rollback to the last good configuration.

5) Disable File and Printer Sharing in your Network setting. This is to isolate problems related to SRV.SYS. Check the validity of the SRV.SYS to make sure it is coming from Microsoft (in %SystemRoot%\system32\DRIVERS or C:\Windows\System32\drivers\)

6) Check for virus or malware (due to the unknown process "@µ‚")

---

Added on June 15, 2008, 4:57 amFaulty Asus OEM ATI video driver (atkdisp.dll)

http://forum.ncix.com/forums/index.php?mod...unt=5&subpage=1

This post has been edited by eclectice: Jun 15 2008, 04:57 AM

Thanks Eccletice. I try to help out whenever i can, but times are short/bad

As for my Problem, My Pc (desktop) Auto Shut(Totally Shut Down, Yes no blue screen ) as i was browsing internet , Any Solution for this problem ? My Pc is just Few Days Old, Shouldn't have this problem .

Which browser do you use?

Please give more details about your system. I could not help you with this vague problem.

Firefox, What sort of details do u need?

your computer specs

ADDED: did it shutdown properly or straight away power off?

This post has been edited by jiaxun: Jun 16 2008, 09:29 PM

hey guys..i received a BSOD last night TWICE. it happen once..den din bother..restart com..use normaly n den it happened again
BSOD is caused of hardware failure rite?
but...can the hardware failure come in d form of a usb wireless receiver? i bought the dlink DWA-110 yesterday n it wa s working fine. however, later on..while listening to my songs on WMP 11, suddenly my song like hang.. n den after like a few secs..the screen came on.
the 2nd wan was... wen i was about to safely remove hardware for the dlink ting n after disconnect my wireless connection. BUT..before i cld click the safely remove dlink dwa-110, d same ting happened?
any ideas y or how to solve it?

try to reinstall the driver?
sometimes the BSOD can be caused by the software/driver issue.

Try to get the latest dump file from "C:\WINDOWS\minidump" and post it over here.

This post has been edited by eclectice: Jun 16 2008, 09:46 PM

Straight Away Power off same like what happen when electricity failure


Tried to type %systemroot%\minidump in RUN but this appear.



This post has been edited by jassicaskylpm: Jun 16 2008, 10:00 PM

Hmm, you haven't install the The Offline Crash Diagnostic tool yet...hmm, not neccessary since probably no dumps at all...

http://support.microsoft.com/kb/923800

This post has been edited by eclectice: Jun 16 2008, 10:06 PM

It might be due to over heatting. try to check if your fans are working

now seems fine *touchwood*
do i still reinstall or what

can i know what minidump does?
and my pc sometimes hard to boot , dunno why... have to wait for a long time
the starting asus screen appeared, when it come to the bios place "press delete to enter setup"... then it reboot again
the samething just keep on repeating .. i have to turn off the supply and try again... and keep trying til it success loaded winxp

and my pc just auto restarted, and i google around and found this thread in lyn

a minidump (as replied by pm) is generally a log of the cause of the BSOD

Hmm, I have seen this kind of symptom (boot->login->auto-restart loop). Normally, it is due to a faulty hardware. When Windows tries to load the kernel driver of the faulty hardware, it immediately triggers system restart with no memory dumping reports.