又蓝了，求帮助（8月21号更新）

网络安全

wei581314 发表于 2011-8-21 12:07
你的意思是说，看蓝屏文件是跟搜狗浏览器很大关系是吧？

其中有一次与搜狗可能有关，但三次蓝屏文件中有两次崩溃代码中没有搜狗的影子，三次蓝屏中有两次是同一个蓝屏代码，所以需要重做系统以确定是否硬盘（也有可能内存条）不兼容。

笙儿

wei581314 发表于 2011-8-21 11:47
求帮助啊

仔细排查下是否因为硬件、驱动、软件、系统等方面引起的冲突。然后再硬件版区或者应用交流版区贴出详细情况请求帮助。

wei581314

网络安全 发表于 2011-8-21 12:11
其中有一次与搜狗可能有关，但三次蓝屏文件中有两次崩溃代码中没有搜狗的影子，三次蓝屏中有两次是同一个 ...

搜狗那个应该是16号那个。另外两个时间早的那个MJ说是跟网银驱动有关，照你说的，应该21号这个也跟网银有关了。硬件肯定是兼容的，因为买了不到一个月的品牌机，我等下看工行有没有新的u盾的驱动。

wei581314

自己顶上去，帮帮忙啊。

七宝

wei581314 发表于 2011-8-21 20:33
自己顶上去，帮帮忙啊。

要不联系kefu@360.cn邮箱，要一个远程qq，看吧

wowocock

和第一次蓝屏是原因一样
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.x86fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0x8444a000 PsLoadedModuleList = 0x84592830
Debug session time: Sun Aug 21 00:06:15.775 2011 (GMT+8)
System Uptime: 0 days 15:49:24.258
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
............
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 832f7a20, The pool entry we were looking for within the page.
Arg3: 832f7aa0, The next pool entry.
Arg4: 18100012, (reserved)

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

Unable to load image \SystemRoot\system32\DRIVERS\Chip_smc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Chip_smc.sys
*** ERROR: Module load completed but symbols could not be loaded for Chip_smc.sys
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
*** WARNING: Unable to verify timestamp for Hookport.sys
*** ERROR: Module load completed but symbols could not be loaded for Hookport.sys

BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 845b2718
Unable to read MiSystemVaType memory at 84592180
832f7a20

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  1

IRP_ADDRESS:  019ae898

LAST_CONTROL_TRANSFER:  from 844ec34b to 845691b6

STACK_TEXT:  
c1599878 844ec34b 832f7a28 00000000 dce1f34f nt!ExFreePoolWithTag+0x1b1
c15998c4 844b2eff 019ae8d8 c159990c c1599904 nt!IopCompleteRequest+0xe6
c1599910 973f4247 939ae898 8a614bb8 8a614f40 nt!IopfCompleteRequest+0x3b4
c159992c 979fa57e 8a614bb8 019ae898 75b93b68 SMCLIB!SmartcardDeviceControl+0xa1
WARNING: Stack unwind information not available. Following frames may be wrong.
c1599948 844864bc 8a614b00 939ae898 c159999c Chip_smc+0x57e
c1599960 8503b0da 972050d8 97206014 75b93b68 nt!IofCallDriver+0x63
c1599978 97201a41 8a61e828 9cea0b98 8a46c490 Wdf01000!imp_WdfRequestSend+0x254
c15999c4 85054072 75d07778 6315f460 00000024 scfilter!WdfScFilter_EvtIoDeviceControl+0x351
c15999e8 850553d0 75d07778 6315f460 00000024 Wdf01000!FxIoQueueIoInternalDeviceControl::Invoke+0x30
c1599a18 850579ac 6315f460 9cea0b98 8a2f8880 Wdf01000!FxIoQueue::DispatchRequestToDriver+0x31d
c1599a34 85058a36 8a2f8800 00000000 8a485f40 Wdf01000!FxIoQueue::DispatchEvents+0x3be
c1599a54 8505a824 9cea0b98 989f7038 8a61e708 Wdf01000!FxIoQueue::QueueRequest+0x1ec
c1599a78 85049a3f 939ae898 c1599a9c 844864bc Wdf01000!FxPkgIo::Dispatch+0x27d
c1599a84 844864bc 8a61e708 939ae898 939ae898 Wdf01000!FxDevice::Dispatch+0x7f
c1599a9c 8468844e 989f7038 939ae898 939ae950 nt!IofCallDriver+0x63
c1599abc 846a523f 8a61e708 989f7038 00000000 nt!IopSynchronousServiceTail+0x1f8
c1599b58 846a7a1a 8a61e708 939ae898 00000000 nt!IopXxxControlFile+0x6aa
c1599b8c 9231e156 000001dc 0000020c 00000000 nt!NtDeviceIoControlFile+0x2a
c1599c10 85136a41 000001dc 0000020c 00000000 klif+0x31156
c1599d04 8448d3ea 000001dc 0000020c 00000000 Hookport+0x4a41
c1599d04 771c6344 000001dc 0000020c 00000000 nt!KiFastCallEntry+0x12a
0123ef3c 00000000 00000000 00000000 00000000 0x771c6344


STACK_COMMAND:  kb

FOLLOWUP_IP:
SMCLIB!SmartcardDeviceControl+a1
973f4247 807d0f00        cmp     byte ptr [ebp+0Fh],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  SMCLIB!SmartcardDeviceControl+a1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SMCLIB

IMAGE_NAME:  SMCLIB.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc718

FAILURE_BUCKET_ID:  0x19_20_SMCLIB!SmartcardDeviceControl+a1

BUCKET_ID:  0x19_20_SMCLIB!SmartcardDeviceControl+a1

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

小飞侠.net

wei581314 发表于 2011-8-21 13:20
搜狗那个应该是16号那个。另外两个时间早的那个MJ说是跟网银驱动有关，照你说的，应该21号这个也跟网银有 ...

虾米牌的U盾，我的是深蓝色的U盾....平时不用就卸载了。