我应该咋办,永久除腿毛太长怎么办;我想知道一下该怎么办!!

21:38:24【 转载互联网】 作者: &&|&责编:李强
&&& &为了解决用户可能碰到关于"腿毛没长出来,不知道用什么啊!"相关的问题,突袭网经过收集整理为用户提供相关的解决办法,请注意,解决办法仅供参考,不代表本网同意其意见,如有任何问题请与本网联系。"腿毛没长出来,不知道用什么啊!"相关的详细问题如下:RT,我想知道:腿毛没长出来,不知道用什么啊!===========突袭网收集的解决方案如下===========
解决方案1:发,再用剃刀仔细刮干净,首先要看受否有遗传方面不要频繁剃除,如果一定要剃除,应先用剪刀将其剪短。可以用些比较好的脱毛膏解决方案2:说下呗?解决方案3:真正的永久脱毛,目前只有一种技术可以达到,那就是使用一段时间的脱毛膏,没事的,这是正常的,如果你不想要毛的话就用脱毛膏 从经济的角度来说的话 就可以了直接买镊子,几块钱。喜欢再好点刮刀,但是这种根本去不了跟的哦,还会在长的呢。不要频繁剃除,如果一定要剃除,应先用剪刀将其剪短,再用剃刀仔细刮干净。脱毛的方法其实很多的,激光脱毛不会永久的,身体上的毛毕竟是身体里面的,说的夸张点就是和血液结合的,激光脱毛也只是一时的我用过 矾诺柏思喘 来去除腿毛,是我个人的赶脚真是不赖。我当时也是不敢用!但是后来因为实在不行了,很快就要去相亲了,所以就用了!现在快停用3个月了!没有副作用呢!也没有反弹的现象!还可以吧感觉。晕解决方案4:姜的汁可促进体毛的增长,比如眉毛,一般是切开姜,将汁涂抹在需要加快体毛增长的地方
================可能对您有帮助================
答:用剃刀仔细刮干净,但不要残留根状毛发,否则毛发会倒刺入肉内,刺伤皮肤。===========================================答:毛发,首先要看受否有遗传方面不要频繁剃除,如果一定要剃除,应先用剪刀将其剪短,再用剃刀仔细刮干净。可以用些比较好的脱毛膏,qAd===========================================答:你的雄性激素少啊 都吃点补品把你的雄性激素补回来啊===========================================答:很多人都有,目前还没有根治的办法,除了不利于美观,其他大的问题===========================================答:有人去腿毛,你却要长腿毛,费解啊===========================================答:腿毛长不出的原因一般是毛囊角化症,这是一种相当常见的皮肤问题,它是一种角质化代谢异常的体显性遗传,有50%的机会,会遗传给下一代,症状通常是从青春期开始明显,到30、40岁会愈来愈不明显,一般来说也不会留下什么后遗症。 毛发没有办法生...===========================================答:刮了会重新长出来的,而且会又长又浓===========================================问:还有就是腿毛一定要刮掉吗? 会对皮肤不好吗?看着别的小姑娘腿都好干净好...答:我原来腿上也是这样的,小圈圈摸起来疙疙瘩瘩的。建议你每周去一次角质,可以去除覆盖在外的死皮,然后涂抹润肤乳,如果不够滋润的话可以加一两滴橄榄油,画圈按摩腿部,有助于滋润软化皮肤。这个坚持一个月就可以明显改善毛毛长不出来的问题,...===========================================问:男,腿毛以前太长了刮过,不知道会长出更粗的,刮了两次,后来长的又粗...答:个人认为。。腿毛这个东西。不要太在意。女用脱毛膏很多都带雌性激素的。男士用了对身体不是很好而且效果不明显。如果你真的想去的话。可以在睡觉的时候拿保鲜纸包裹住需要脱毛的地方。然后第二天起来用肥皂清洗。这个应该没拔那么痛。不过效果...===========================================
12345678910您的位置: &
& 有腿毛怎么办
有腿毛怎么办
问:......
答:指导意见:你描述的情况来,可考虑光子脱毛技术。要选择正规的医院。 &&......
问:女生有腿毛怎么办,什么办法能去腿毛,除了激光......
答:指导意见:激光脱毛是目前最先进的一种永久性脱毛方法,具有脱毛针对性强,疗效显著,操作简单,速度快,疼痛轻微,不留疤痕,无副作用的优点.作用于不同部位和深度毛囊,有效去除人体任何部位和深度的毛发.获得理想的脱毛疗效的同时,又能有效保护表皮不受热损伤.表......
问:有腿毛怎么办啊?由于去年夏天的时候,穿短裤不好看,所以就刮了还有胳膊上的越长越长还很黑
......
答:您好!激光脱毛是依据选择性热动力学作用原理,利用最新激光技术除毛。激光机发射的光束会穿透皮肤表层最终被毛囊吸收,通过对激光能量的有选择吸收,使毛囊受到破坏,不能再生长毛发,同时又不损伤周边组织。激光脱毛的过程简单、快捷,治疗后一般不留瘢痕。激光治疗应......
问:问题描述:从小手臂上,腿上甚至是手指和脚趾上都长了许多浓密的黑色汗毛,都不敢穿裙子或短裤,不知道我这个年龄该怎么解决这种问题......
答:你好,你这皮肤多毛考虑雄性激素过盛引起的,可考虑光子脱毛技术. &&......
问:......
答:可以用激光除毛,一次性永久性的脱毛。 &&......
问:问题描述:长了胡子,小腿的毛很长......
答:激光脱毛是目前最先进的一种永久性脱毛方法,具有脱毛针对性强,疗效显著,操作简单,速度快,疼痛轻微,不留疤痕,无副作用的优点.作用于不同部位和深度毛囊,有效去除人体任何部位和深度的毛发.获得理想的脱毛疗效的同时,又能有效保护表皮不受热损伤.表皮吸收激光......
问:病情描述:有冻疮怎么办??????????????????????????????曾经治疗情况和效果:&&第一次生冻疮。。。。。。。。。。。。。。。。......
答:病情分析:应该是你末梢循环差而且保温不够导致的。冬季气温低,末梢血管内的血流也随即变得缓慢,皮下小动脉遇冷收缩,静脉回流不畅,从而发生冻疮。部分患者是因为血管先天性变异、血管狭窄导致血流不畅而诱发冻疮的。所以与每个人的末梢循环也有关系的。指导意见:治......
问:爷爷上年开始觉得眼睛看东西的时候就是很不舒服的,有时候眼睛就是经常流眼泪,感到疼痛的,最近觉得药物多了比以前,就是老豆眼睛有彩色的一层东西,六十到眼科医院就诊,检查后发现......
答:你好,白内障的治疗方法是可以通过手术治疗,老年性白内障发展到视力低于0.3、晶状体混浊在未成熟期、中心核部比较软,适合做超声乳化手术。其优点是切口小,组织损伤少,手术时间短,视力恢复快。&&......
问:这次刚大学毕业不久,到一家公司报道准备工作,可是上星期体检报告出来说我患有乙肝,年纪轻轻的我,怎么会患有乙肝,现在我的心情糟糕透了,本来毕业可以工作赚钱,好好地在事业上施......
答:你好!乙肝携带者和人交往应该小心最好你的身边的人都能注射乙肝疫苗,然后定期注射加强针,那么你以后就要好好的照顾好自己了,不要吃,喝,或作出任何伤害你的肝脏的事情,也不要让自己的免疫系统低落下来,一旦你的免疫系统地落了,那么病毒就会发作。还有要定期检查......
问:我的脸冬天冻了,有痒有红怎么办。用什么好......
答:你是不是每年都会动呢?&&......
问:病情描述:有痘印怎么办,如何治疗&预防?有什么高方法曾经治疗情况和效果:&&无想得到怎样的帮助:&&尽快减少痘印......
答:病情分析:一般痘印色素沉淀是可以适当涂抹维生素E的,指导意见:对于凹洞性痘印可以选择填充法或镭射磨皮;增生性凸疤治疗选用局部皮下注射或镭射等光照疗法。&&......
问:的宝宝耳朵后面有癣怎么办&并有扩散的趋向&我想知道是怎么回事曾经治疗情况和效果:&&未曾就诊过想得到怎样的帮助:&&nb......
答:病情分析:三个月大的宝宝耳朵后面长的很可能是奶癣,也就是湿疹,很少感染真菌引起的癣。指导意见:可用丁酸氢化可的松软膏外用以控制症状,再用氧化锌软膏治疗。但这是治标不治本的办法。治本的办法是避免孩子过敏。如果孩子是吃奶粉的,可让孩子吃一段时间的水解蛋白......
问:病情描述:宝宝一不小心掉地上,头部有水肿怎么办?脑袋一边摸上去软软的怎么办啊?曾经治疗情况和效果:&&无想得到怎样的帮助:&&宝宝......
答:病情分析:您说的这个应该是颅外的血肿指导意见:比较少量的可以自行吸收的,如果较多只能到医院处理。您现在最好是到医院做个CT,以防颅内有出血的情况&&......
问:病情描述:腿部有肌肉怎么办,并且腿根很粗,穿衣服选择很不方便曾经治疗情况和效果:&&无想得到怎样的帮助:&&告诉我不需要药物治疗的......
答:病情分析:考虑到是想进行局部瘦身的情况指导意见:您好,建议进行局部瘦身的话还是应该通过合理的饮食再加上长期坚持不懈的针对性运动,不建议进行其他的瘦身方式&&......
问:病情描述:有痘印怎么办&那个盐水醋调和擦脸&可以美白那个&盐怎么算&&加入水九杯&&醋三杯&nbsp......
答:您好:建议您去正规的整形医院去做激光去痘印,目前最有效的一种方式就是激光去痘印,通过激光祛痘美容中特定波长的激光,则可以对抑制痤疮赖以产生的皮脂过多,杀死导致痤疮的多种细菌,使新生的小痘痘及时隐退。另外,激光还可以有效地刺激皮肤胶原蛋白的再生,使生过......
更多相关推荐
收藏快速问医生,随时免费咨询和挂号Quick access
电脑不定期死机,用了windbg分析,有人可以帮忙分析一下么?我想知道我应该怎么做
电脑不定期死机,用了windbg分析,得到分析结果如下,但我不懂得看,有人可以帮忙解释一下么?我想知道我应该怎么做
最近一次死机的分析:
Microsoft (R) Windows Debugger Version 6.11. Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\tam\Desktop\Mini.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\temp*/download/symbols Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: .x86fre.vistasp2_gdr.9 Machine Name: Kernel base = 0x PsLoadedModuleList = 0x82324c70 Debug session time: Mon Jan 25 23:38:10.596 2010 (GMT+8) System Uptime: 0 days 3:28:07.771 Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ... ******************************************************************************* *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {f8cb9c34, 0, }
Probably caused by : ntkrpamp.exe ( nt!ObpCloseHandleTableEntry+20 )
Followup: MachineOwner ---------
1: kd& !analyze -v ******************************************************************************* *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced.& This cannot be protected by try-except, it must be protected by a Probe.& Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: f8cb9c34, memory referenced. Arg2: , value 0 = read operation, 1 = write operation. Arg3: , If non-zero, the instruction address which referenced the bad memory &&& address. Arg4: , (reserved)
Debugging Details: ------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from
Unable to read MiSystemVaType memory at
FAULTING_IP:
nt!ObpCloseHandleTableEntry+20 87400&&&&&&& cmp&&&& dword ptr [eax+74h],0
MM_INTERNAL_CODE:& 2
CUSTOMER_CRASH_COUNT:& 1
DEFAULT_BUCKET_ID:& VISTA_DRIVER_FAULT
BUGCHECK_STR:& 0x50
PROCESS_NAME:& csrss.exe
CURRENT_IRQL:& 0
TRAP_FRAME:& a8d87c64 -- (.trap 0xffffffffa8d87c64) ErrCode =
eax=f8cb9bc0 ebx=aa68b818 ecx= edx=84875d60 esi=84875d60 edi=91c95030 eip= esp=a8d87cd8 ebp=a8d87d14 iopl=0&&&&&&&& nv up ei ng nz na pe nc cs=0008& ss=0010& ds=0023& es=0023& fs=0030& gs=0000&&&&&&&&&&&& efl= nt!ObpCloseHandleTableEntry+0x20: 87400&&&&&&& cmp&&&& dword ptr [eax+74h],0 ds:c34=???????? Resetting default scope
LAST_CONTROL_TRANSFER:& from 8225adb4 to 822a536d
STACK_TEXT:&
a8d87c4c 8225adb4 cb9c34
nt!MmAccessFault+0x10a a8d87c4c 0c34
nt!KiTrap0E+0xdc a8d87d14 fea530 aa68b818 879d2d90 nt!ObpCloseHandleTableEntry+0x20 a8d87d44 9d2d90 91c01 nt!ObpCloseHandle+0x73 a8d87d58 000c0c 007bfe00 77385e74 nt!NtClose+0x20 a8d87d58 00c0c 007bfe00 77385e74 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 007bfe00 00 x77385e74
STACK_COMMAND:& kb
FOLLOWUP_IP:
nt!ObpCloseHandleTableEntry+20 87400&&&&&&& cmp&&&& dword ptr [eax+74h],0
SYMBOL_STACK_INDEX:& 2
SYMBOL_NAME:& nt!ObpCloseHandleTableEntry+20
FOLLOWUP_NAME:& MachineOwner
MODULE_NAME: nt
IMAGE_NAME:& ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:& 4a77feb3
FAILURE_BUCKET_ID:& 0x50_nt!ObpCloseHandleTableEntry+20
BUCKET_ID:& 0x50_nt!ObpCloseHandleTableEntry+20
Followup: MachineOwner ---------
上一次死机的分析:
Microsoft (R) Windows Debugger Version 6.11. Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\tam\Desktop\Mini.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\temp*/download/symbols Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: .x86fre.vistasp2_gdr.9 Machine Name: Kernel base = 0x PsLoadedModuleList = 0x82162c70 Debug session time: Thu Jan 14 17:21:18.781 2010 (GMT+8) System Uptime: 0 days 5:34:44.594 Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ... ******************************************************************************* *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0fc083, b1a93bb0, 0}
Probably caused by : ntkrpamp.exe ( nt!ObReferenceObjectSafe+14 )
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 0x.& 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: c0000005, The exception code that was not handled Arg2: 820fc083, The address that the exception occurred at Arg3: b1a93bb0, Trap Frame Arg4:
Debugging Details: ------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
nt!ObReferenceObjectSafe+14 820fc083 f00fb137&&&&&&& lock cmpxchg dword ptr [edi],esi
TRAP_FRAME:& b1a93bb0 -- (.trap 0xffffffffb1a93bb0) ErrCode =
eax=020dc857 ebx=b876c430 ecx=020dc857 edx=0063ffea esi=020dc858 edi=0063ffea eip=820fc083 esp=b1a93c24 ebp=b1a93c50 iopl=0&&&&&&&& nv up ei pl nz na po nc cs=0008& ss=0010& ds=0023& es=0023& fs=0030& gs=0000&&&&&&&&&&&& efl= nt!ObReferenceObjectSafe+0x14: 820fc083 f00fb137&&&&&&& lock cmpxchg dword ptr [edi],esi ds:ffea=???????? Resetting default scope
CUSTOMER_CRASH_COUNT:& 1
DEFAULT_BUCKET_ID:& VISTA_DRIVER_FAULT
BUGCHECK_STR:& 0x8E
PROCESS_NAME:& SearchIndexer.e
CURRENT_IRQL:& 0
LAST_CONTROL_TRANSFER:& from 8225740b to 820fc083
STACK_TEXT:&
b1a93c28 be19e0 85be19e0
nt!ObReferenceObjectSafe+0x14 b1a93c50
ad7c6740 nt!AlpcpDisconnectPort+0x13c b1a93c68 4c040 b1a93cc4
nt!AlpcpDoPortCleanup+0xf b1a93c74
ad7ce0 001f0001 nt!AlpcpClosePort+0x23 b1a93cc4
ad7c0 001f0001 nt!ObpDecrementHandleCount+0x146 b1a93d14 8228506b a9bd2548 af072640 ad7c6740 nt!ObpCloseHandleTableEntry+0x234 b1a93d44 8228574f ad7c1
nt!ObpCloseHandle+0x73 b1a93d58 000b20 65e74 nt!NtClose+0x20 b1a93d58 00b20 65e74 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 00 65e74
STACK_COMMAND:& kb
FOLLOWUP_IP:
nt!ObReferenceObjectSafe+14 820fc083 f00fb137&&&&&&& lock cmpxchg dword ptr [edi],esi
SYMBOL_STACK_INDEX:& 0
SYMBOL_NAME:& nt!ObReferenceObjectSafe+14
FOLLOWUP_NAME:& MachineOwner
MODULE_NAME: nt
IMAGE_NAME:& ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:& 4a77feb3
FAILURE_BUCKET_ID:& 0x8E_nt!ObReferenceObjectSafe+14
BUCKET_ID:& 0x8E_nt!ObReferenceObjectSafe+14
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 0x.& 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: c0000005, The exception code that was not handled Arg2: 820fc083, The address that the exception occurred at Arg3: b1a93bb0, Trap Frame Arg4:
Debugging Details: ------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
nt!ObReferenceObjectSafe+14 820fc083 f00fb137&&&&&&& lock cmpxchg dword ptr [edi],esi
TRAP_FRAME:& b1a93bb0 -- (.trap 0xffffffffb1a93bb0) ErrCode =
eax=020dc857 ebx=b876c430 ecx=020dc857 edx=0063ffea esi=020dc858 edi=0063ffea eip=820fc083 esp=b1a93c24 ebp=b1a93c50 iopl=0&&&&&&&& nv up ei pl nz na po nc cs=0008& ss=0010& ds=0023& es=0023& fs=0030& gs=0000&&&&&&&&&&&& efl= nt!ObReferenceObjectSafe+0x14: 820fc083 f00fb137&&&&&&& lock cmpxchg dword ptr [edi],esi ds:ffea=???????? Resetting default scope
CUSTOMER_CRASH_COUNT:& 1
DEFAULT_BUCKET_ID:& VISTA_DRIVER_FAULT
BUGCHECK_STR:& 0x8E
PROCESS_NAME:& SearchIndexer.e
CURRENT_IRQL:& 0
LAST_CONTROL_TRANSFER:& from 8225740b to 820fc083
STACK_TEXT:&
b1a93c28 be19e0 85be19e0
nt!ObReferenceObjectSafe+0x14 b1a93c50
ad7c6740 nt!AlpcpDisconnectPort+0x13c b1a93c68 4c040 b1a93cc4
nt!AlpcpDoPortCleanup+0xf b1a93c74
ad7ce0 001f0001 nt!AlpcpClosePort+0x23 b1a93cc4
ad7c0 001f0001 nt!ObpDecrementHandleCount+0x146 b1a93d14 8228506b a9bd2548 af072640 ad7c6740 nt!ObpCloseHandleTableEntry+0x234 b1a93d44 8228574f ad7c1
nt!ObpCloseHandle+0x73 b1a93d58 000b20 65e74 nt!NtClose+0x20 b1a93d58 00b20 65e74 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 00 65e74
STACK_COMMAND:& kb
FOLLOWUP_IP:
nt!ObReferenceObjectSafe+14 820fc083 f00fb137&&&&&&& lock cmpxchg dword ptr [edi],esi
SYMBOL_STACK_INDEX:& 0
SYMBOL_NAME:& nt!ObReferenceObjectSafe+14
FOLLOWUP_NAME:& MachineOwner
MODULE_NAME: nt
IMAGE_NAME:& ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:& 4a77feb3
FAILURE_BUCKET_ID:& 0x8E_nt!ObReferenceObjectSafe+14
BUCKET_ID:& 0x8E_nt!ObReferenceObjectSafe+14
Followup: MachineOwner ---------
再上一次死机的分析:
Microsoft (R) Windows Debugger Version 6.11. Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\tam\Desktop\Mini.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\temp*/download/symbols Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: .x86fre.vistasp2_gdr.9 Machine Name: Kernel base = 0x PsLoadedModuleList = 0x82122c70 Debug session time: Mon Jan& 4 19:19:32.425 2010 (GMT+8) System Uptime: 0 days 8:02:50.584 Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ... ******************************************************************************* *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904aa, c51745d0, c51742cc, }
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFile+8e5 )
Followup: MachineOwner ---------
1: kd& !analyze -v ******************************************************************************* *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *******************************************************************************
NTFS_FILE_SYSTEM (24) &&& If you see NtfsExceptionFilter on the stack then the 2nd and 3rd &&& parameters are the exception record and context record. Do a .cxr &&& on the 3rd parameter and then kb to obtain a more informative stack &&& trace. Arguments: Arg1: 001904aa Arg2: c51745d0 Arg3: c51742cc Arg4:
Debugging Details: ------------------
EXCEPTION_RECORD:& c51745d0 -- (.exr 0xffffffffc51745d0) ExceptionAddress:
(nt!MiCheckControlArea+0x0000024b) && ExceptionCode: c0000005 (Access violation) & ExceptionFlags:
NumberParameters: 2 && Parameter[0]:
&& Parameter[1]: 000f0000 Attempt to read from address 000f0000
CONTEXT:& c51742cc -- (.cxr 0xffffffffc51742cc) eax= ebx=000f0000 ecx=82143d00 edx= esi= edi=84ee3528 eip= esp=c5174698 ebp=c51746a8 iopl=0&&&&&&&& nv up ei pl nz na pe nc cs=0008& ss=0010& ds=0023& es=0023& fs=0030& gs=0000&&&&&&&&&&&& efl= nt!MiCheckControlArea+0x24b:
8b33&&&&&&&&&&& mov&&&& esi,dword ptr [ebx]& ds:0=???????? Resetting default scope
CUSTOMER_CRASH_COUNT:& 1
DEFAULT_BUCKET_ID:& VISTA_DRIVER_FAULT
PROCESS_NAME:& firefox.exe
CURRENT_IRQL:& 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
EXCEPTION_PARAMETER1:&
EXCEPTION_PARAMETER2:& 000f0000
READ_ADDRESS: GetPointerFromAddress: unable to read from
Unable to read MiSystemVaType memory at
FOLLOWUP_IP:
Ntfs!NtfsDeleteFile+8e5 8847e60e e96cffffff&&&&& jmp&&&& Ntfs!NtfsDeleteFile+0x856 (8847e57f)
FAULTING_IP:
nt!MiCheckControlArea+24b
8b33&&&&&&&&&&& mov&&&& esi,dword ptr [ebx]
BUGCHECK_STR:& 0x24
LAST_CONTROL_TRANSFER:& from 820c50bc to
STACK_TEXT:&
cc50bc 84ee0
nt!MiCheckControlArea+0x24b c24faa2 adb80000 bdcf0 nt!MmUnmapViewInSystemCache+0x59b c0c463d 00 nt!CcUnmapVacb+0x170 c2c49a 00 nt!CcUnmapVacbArray+0x1cc c7e60e 847b10e4 00000 nt!CcPurgeCacheSection+0xde c9d694 aefbc3e8 bad6f008 acbe4d08 Ntfs!NtfsDeleteFile+0x8e5 c1c95a aefbc3e8 d537626 Ntfs!NtfsCommonCleanup+0x1e35 c0b81d8 aefbc398
ffffffff Ntfs!NtfsCommonCleanupCallout+0x1d c0b82d1 aefbc398
ffffffff nt!KiSwapKernelStackAndExit+0x118 aefbc328 00
nt!KiSwitchKernelStackAndCallout+0x31
SYMBOL_STACK_INDEX:& 5
SYMBOL_NAME:& Ntfs!NtfsDeleteFile+8e5
FOLLOWUP_NAME:& MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME:& Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP:& 49e0192a
STACK_COMMAND:& .cxr 0xffffffffc51742 kb
FAILURE_BUCKET_ID:& 0x24_Ntfs!NtfsDeleteFile+8e5
BUCKET_ID:& 0x24_Ntfs!NtfsDeleteFile+8e5
Followup: MachineOwner ---------
1: kd& !analyze -v ******************************************************************************* *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& * *******************************************************************************
NTFS_FILE_SYSTEM (24) &&& If you see NtfsExceptionFilter on the stack then the 2nd and 3rd &&& parameters are the exception record and context record. Do a .cxr &&& on the 3rd parameter and then kb to obtain a more informative stack &&& trace. Arguments: Arg1: 001904aa Arg2: c51745d0 Arg3: c51742cc Arg4:
Debugging Details: ------------------
EXCEPTION_RECORD:& c51745d0 -- (.exr 0xffffffffc51745d0) ExceptionAddress:
(nt!MiCheckControlArea+0x0000024b) && ExceptionCode: c0000005 (Access violation) & ExceptionFlags:
NumberParameters: 2 && Parameter[0]:
&& Parameter[1]: 000f0000 Attempt to read from address 000f0000
CONTEXT:& c51742cc -- (.cxr 0xffffffffc51742cc) eax= ebx=000f0000 ecx=82143d00 edx= esi= edi=84ee3528 eip= esp=c5174698 ebp=c51746a8 iopl=0&&&&&&&& nv up ei pl nz na pe nc cs=0008& ss=0010& ds=0023& es=0023& fs=0030& gs=0000&&&&&&&&&&&& efl= nt!MiCheckControlArea+0x24b:
8b33&&&&&&&&&&& mov&&&& esi,dword ptr [ebx]& ds:0=???????? Resetting default scope
CUSTOMER_CRASH_COUNT:& 1
DEFAULT_BUCKET_ID:& VISTA_DRIVER_FAULT
PROCESS_NAME:& firefox.exe
CURRENT_IRQL:& 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
EXCEPTION_PARAMETER1:&
EXCEPTION_PARAMETER2:& 000f0000
READ_ADDRESS: GetPointerFromAddress: unable to read from
Unable to read MiSystemVaType memory at
FOLLOWUP_IP:
Ntfs!NtfsDeleteFile+8e5 8847e60e e96cffffff&&&&& jmp&&&& Ntfs!NtfsDeleteFile+0x856 (8847e57f)
FAULTING_IP:
nt!MiCheckControlArea+24b
8b33&&&&&&&&&&& mov&&&& esi,dword ptr [ebx]
BUGCHECK_STR:& 0x24
LAST_CONTROL_TRANSFER:& from 820c50bc to
STACK_TEXT:&
cc50bc 84ee0
nt!MiCheckControlArea+0x24b c24faa2 adb80000 bdcf0 nt!MmUnmapViewInSystemCache+0x59b c0c463d 00 nt!CcUnmapVacb+0x170 c2c49a 00 nt!CcUnmapVacbArray+0x1cc c7e60e 847b10e4 00000 nt!CcPurgeCacheSection+0xde c9d694 aefbc3e8 bad6f008 acbe4d08 Ntfs!NtfsDeleteFile+0x8e5 c1c95a aefbc3e8 d537626 Ntfs!NtfsCommonCleanup+0x1e35 c0b81d8 aefbc398
ffffffff Ntfs!NtfsCommonCleanupCallout+0x1d c0b82d1 aefbc398
ffffffff nt!KiSwapKernelStackAndExit+0x118 aefbc328 00
nt!KiSwitchKernelStackAndCallout+0x31
SYMBOL_STACK_INDEX:& 5
SYMBOL_NAME:& Ntfs!NtfsDeleteFile+8e5
FOLLOWUP_NAME:& MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME:& Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP:& 49e0192a
STACK_COMMAND:& .cxr 0xffffffffc51742 kb
FAILURE_BUCKET_ID:& 0x24_Ntfs!NtfsDeleteFile+8e5
BUCKET_ID:& 0x24_Ntfs!NtfsDeleteFile+8e5
Followup: MachineOwner
All replies
請閱讀下面這個 Microsoft 幫助和支持, 那裏面有關於你所遇到問題的詳細說明.
易宝典:Windows常见蓝屏故障分析(MVP 撰稿) Folding@Home
您好: &&&&&&& 请建议在保证硬件没有问题的情况下用杀毒软件先给PC做一次Full Scan以排除病毒的可能性。报告里面提到火狐那就卸载火狐浏览器重新安装一遍。至于Ntfs.sys有可能该文件已损坏或丢失!用安装盘启动后修复一下试试看。也可以参考一下:/question/9846505.html}

我要回帖

更多关于 我应该歌词 的文章

更多推荐

版权声明:文章内容来源于网络,版权归原作者所有,如有侵权请点击这里与我们联系,我们将及时删除。

点击添加站长微信