首页
社区
课程
招聘
[求助]驱动开发遇到蓝屏问题
发表于: 2016-10-26 11:18 4565

[求助]驱动开发遇到蓝屏问题

2016-10-26 11:18
4565
驱动安装启动后,启动IE会导致蓝屏。用windbg查看dump文件。但是看不懂,求指点
文件内容如下:
16.kd:x86> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 02dd5064, address which referenced memory

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  7601.17514.amd64fre.win7sp1_rtm.101119-1850

SYSTEM_MANUFACTURER:  VMware, Inc.

VIRTUAL_MACHINE:  VMware

SYSTEM_PRODUCT_NAME:  VMware Virtual Platform

SYSTEM_VERSION:  None

BIOS_VENDOR:  Phoenix Technologies LTD

BIOS_VERSION:  6.00

BIOS_DATE:  05/20/2014

BASEBOARD_MANUFACTURER:  Intel Corporation

BASEBOARD_PRODUCT:  440BX Desktop Reference Platform

BASEBOARD_VERSION:  None

DUMP_TYPE:  1

BUGCHECK_P1: 18

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff88002dd5064

READ_ADDRESS:  00000018 

CURRENT_IRQL:  0

FAULTING_IP: 
ProxyDriver!ProxyClassifyFn+54 [e:\visual_studio_test\proxydriver\proxydriver\callout.c @ 26]
fffff880`02dd5064 8b4018          mov     eax,dword ptr [eax+18h]

CPU_COUNT: 1

CPU_MHZ: 8f6

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CPU_MICROCODE: 6,0,0,0 (F,M,S,R)  SIG: 29'00000000 (cache) 29'00000000 (init)

BUGCHECK_STR:  0xD1

ANALYSIS_SESSION_HOST:  DESKTOP-A5HRKIU

ANALYSIS_SESSION_TIME:  10-26-2016 11:09:37.0398

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

IP_IN_FREE_BLOCK: 0

LAST_CONTROL_TRANSFER:  from 00000000 to 00000000

STACK_TEXT:  
00000000 00000000 00000000 00000000 00000000 0x0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ProxyDriver!ProxyClassifyFn+54 [e:\visual_studio_test\proxydriver\proxydriver\callout.c @ 26]
fffff880`02dd5064 8b4018          mov     eax,dword ptr [eax+18h]

FAULT_INSTR_CODE:  8318408b

FAULTING_SOURCE_LINE:  e:\visual_studio_test\proxydriver\proxydriver\callout.c

FAULTING_SOURCE_FILE:  e:\visual_studio_test\proxydriver\proxydriver\callout.c

FAULTING_SOURCE_LINE_NUMBER:  26

FAULTING_SOURCE_CODE:  
    22: 	UINT32   index;
    23: 	UINT32   LocalIPADDRv4, remoteIPADDRv4;
    24: 	USHORT   LocalPort, remotePort;
    25: 
>   26: 	if (!(classifyOut->rights & FWPS_RIGHT_ACTION_WRITE))
    27: 	{
    28: 		LOG(("write right not set!\n"));
    29: 		return;
    30: 	}
    31: 


SYMBOL_NAME:  ProxyDriver!ProxyClassifyFn+54

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ProxyDriver

IMAGE_NAME:  ProxyDriver.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  580f2644

BUCKET_ID:  INVALID_KERNEL_CONTEXT_0xD1

DEFAULT_BUCKET_ID:  INVALID_KERNEL_CONTEXT_0xD1

PRIMARY_PROBLEM_CLASS:  INVALID_KERNEL_CONTEXT

FAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXT_0xD1

TARGET_TIME:  2016-10-25T15:23:50.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2010-11-20 17:30:02

BUILDDATESTAMP_STR:  101119-1850

BUILDLAB_STR:  win7sp1_rtm

BUILDOSVER_STR:  6.1.7601.17514.amd64fre.win7sp1_rtm.101119-1850

ANALYSIS_SESSION_ELAPSED_TIME: 7f4

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:invalid_kernel_context_0xd1

FAILURE_ID_HASH:  {f238e05f-b115-b8c8-bf03-0d507e32cac6}

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

[注意]传递专业知识、拓宽行业人脉——看雪讲师团队等你加入!

收藏
免费 0
支持
分享
最新回复 (6)
雪    币: 2291
活跃值: (938)
能力值: ( LV8,RANK:130 )
在线值:
发帖
回帖
粉丝
2
都给你定位到了出错的源代码行数了
classifyOut空指针了
2016-10-26 11:26
0
雪    币: 3
活跃值: (10)
能力值: ( LV2,RANK:10 )
在线值:
发帖
回帖
粉丝
3
是的,问题是不懂为什么会造成空指针的情况。。。代码是原原本本从书上下来的。。
2016-10-26 11:31
0
雪    币: 248
活跃值: (3789)
能力值: ( LV2,RANK:10 )
在线值:
发帖
回帖
粉丝
4
classifyOut判断一下是不是空指针
这是个代理驱动吗?
2016-10-26 14:55
0
雪    币: 3
活跃值: (10)
能力值: ( LV2,RANK:10 )
在线值:
发帖
回帖
粉丝
5
还不算吧,只是自己写的一个,想测试一下
status = RegisterCalloutForLayer(
		&FWPM_LAYER_ALE_CONNECT_REDIRECT_V4,
		&PROXY_ALE_CONNECT_REDIRECT_CALLOUT_V4,
		ProxyClassifyFn,
		ProxyNotifyFn,
		ProxyFlowDeleteFn,
		&gAleConnectCalloutId,
		&gAleConnectFilterId
		);

这个是callout的注册函数。

不加return能不让他蓝屏吗?
2016-10-26 15:05
0
雪    币: 3
活跃值: (10)
能力值: ( LV2,RANK:10 )
在线值:
发帖
回帖
粉丝
6
classifyout 这个指针为空。是什么原因造成的?怎么解决 有人解答下吗!
2016-10-26 15:54
0
雪    币: 364
活跃值: (1721)
能力值: ( LV4,RANK:50 )
在线值:
发帖
回帖
粉丝
7
看看在那有值,那被修改
2016-10-26 17:02
0
游客
登录 | 注册 方可回帖
返回
//