首页
社区
课程
招聘
[旧帖] 求助大神帮忙解决一下ce修改游戏后蓝屏的解决办法!! 0.00雪花
发表于: 2016-3-12 11:16 6202

[旧帖] 求助大神帮忙解决一下ce修改游戏后蓝屏的解决办法!! 0.00雪花

2016-3-12 11:16
6202
最近玩了一款单机游戏,由于难道太高,打算用ce修改一下在玩,结果游戏直接退出,在进直接蓝屏,重启进入依旧蓝屏!求助大神帮忙!
dump分析结果如下:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

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

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.130704-0421
Machine Name:
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
Debug session time: Sun Mar  6 21:32:38.421 2016 (UTC + 8:00)
System Uptime: 0 days 3:54:28.179
Loading Kernel Symbols
...............................................................
...............................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, b8338d70, 0, 0}

Probably caused by : win32k.sys ( win32k!StubGdiAlloc+a )

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

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: b8338d70
Arg3: 00000000
Arg4: 00000000

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

BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  csrss.exe

LAST_CONTROL_TRANSFER:  from bf800c51 to bf805a2f

STACK_TEXT:  
b49f1008 bf800c51 00000009 0000003c 6d737355 win32k!StubGdiAlloc+0xa
b49f1020 bf837850 89899ea8 bf83e534 e1b0d510 win32k!ExAllocateFromPagedLookasideList+0x27
b49f1028 bf83e534 e1b0d510 b9ebb170 00000002 win32k!AllocSMS+0xb
b49f10b8 bf80f5ef b9ebb170 00000002 00000000 win32k!xxxInterSendMsgEx+0x15f
b49f1104 bf80eda9 b9ebb170 00000002 00000000 win32k!xxxSendMessageTimeout+0x11f
b49f1128 bf8465ba b9ebb170 00000002 00000000 win32k!xxxSendMessage+0x1b
b49f1164 bf846570 b9ebb170 e1b0d510 b9e40818 win32k!xxxDW_SendDestroyMessages+0x35
b49f1194 bf846cf7 b9e40818 004f010a 00000083 win32k!xxxDW_SendDestroyMessages+0x77
b49f11e4 bf80afae 00000000 b9e40818 00000010 win32k!xxxDestroyWindow+0x390
b49f123c bf80d3f8 b9e40818 00000010 00000000 win32k!xxxRealDefWindowProc+0x1bd
b49f1260 bf83f117 b9e40818 00000010 00000000 win32k!xxxDefWindowProc+0x107
b49f12d0 bf802dd1 e1b0d510 e1b0d510 00000000 win32k!xxxReceiveMessage+0x301
b49f12fc bf83e90e 00000200 00000000 00000000 win32k!xxxSleepThread+0x8a
b49f1398 bf80f5ef b9ebb170 00000002 00000000 win32k!xxxInterSendMsgEx+0x7f6
b49f13e4 bf80eda9 b9ebb170 00000002 00000000 win32k!xxxSendMessageTimeout+0x11f
b49f1408 bf8465ba b9ebb170 00000002 00000000 win32k!xxxSendMessage+0x1b
b49f1444 bf846570 b9ebb170 e1b0d510 b9e40818 win32k!xxxDW_SendDestroyMessages+0x35
b49f1474 bf846cf7 b9e40818 004f010a 00000083 win32k!xxxDW_SendDestroyMessages+0x77
b49f14c4 bf80afae 00000000 b9e40818 00000010 win32k!xxxDestroyWindow+0x390
b49f151c bf80d3f8 b9e40818 00000010 00000000 win32k!xxxRealDefWindowProc+0x1bd
b49f1540 bf83f117 b9e40818 00000010 00000000 win32k!xxxDefWindowProc+0x107
b49f15b0 bf802dd1 e1b0d510 e1b0d510 00000000 win32k!xxxReceiveMessage+0x301
b49f15dc bf83e90e 00000200 00000000 00000000 win32k!xxxSleepThread+0x8a
b49f1678 bf80f5ef b9e5d5e0 00000002 00000000 win32k!xxxInterSendMsgEx+0x7f6
b49f16c4 bf80eda9 b9e5d5e0 00000002 00000000 win32k!xxxSendMessageTimeout+0x11f
b49f16e8 bf8465ba b9e5d5e0 00000002 00000000 win32k!xxxSendMessage+0x1b
b49f1724 bf846570 b9e5d5e0 e1b0d510 b9e40818 win32k!xxxDW_SendDestroyMessages+0x35
b49f1754 bf846cf7 b9e40818 004f010a 00000083 win32k!xxxDW_SendDestroyMessages+0x77
b49f17a4 bf80afae 00000000 b9e40818 00000010 win32k!xxxDestroyWindow+0x390
b49f17fc bf80d3f8 b9e40818 00000010 00000000 win32k!xxxRealDefWindowProc+0x1bd
b49f1820 bf83f117 b9e40818 00000010 00000000 win32k!xxxDefWindowProc+0x107
b49f1890 bf802dd1 e1b0d510 e1b0d510 00000000 win32k!xxxReceiveMessage+0x301
b49f18bc bf83e90e 00000200 00000000 00000000 win32k!xxxSleepThread+0x8a
b49f1958 bf80f5ef b9e5d5e0 00000002 00000000 win32k!xxxInterSendMsgEx+0x7f6
b49f19a4 bf80eda9 b9e5d5e0 00000002 00000000 win32k!xxxSendMessageTimeout+0x11f
b49f19c8 bf8465ba b9e5d5e0 00000002 00000000 win32k!xxxSendMessage+0x1b
b49f1a04 bf846570 b9e5d5e0 e1b0d510 b9e40818 win32k!xxxDW_SendDestroyMessages+0x35
b49f1a34 bf846cf7 b9e40818 004f010a 00000083 win32k!xxxDW_SendDestroyMessages+0x77
b49f1a84 bf80afae 00000000 b9e40818 00000010 win32k!xxxDestroyWindow+0x390
b49f1adc bf80d3f8 b9e40818 00000010 00000000 win32k!xxxRealDefWindowProc+0x1bd
b49f1b00 bf83f117 b9e40818 00000010 00000000 win32k!xxxDefWindowProc+0x107
b49f1b70 bf802dd1 e1b0d510 e1b0d510 00000000 win32k!xxxReceiveMessage+0x301
b49f1b9c bf83e90e 00000200 00000000 00000000 win32k!xxxSleepThread+0x8a
b49f1c38 bf80f5ef b9ebb170 00000002 00000000 win32k!xxxInterSendMsgEx+0x7f6
b49f1c84 bf80eda9 b9ebb170 00000002 00000000 win32k!xxxSendMessageTimeout+0x11f
b49f1ca8 bf8465ba b9ebb170 00000002 00000000 win32k!xxxSendMessage+0x1b
b49f1ce4 bf846570 b9ebb170 e1b0d510 b9e40818 win32k!xxxDW_SendDestroyMessages+0x35
b49f1d14 bf846cf7 b9e40818 004f010a 00000083 win32k!xxxDW_SendDestroyMessages+0x77
b49f1d64 bf80afae 00000000 b9e40818 00000010 win32k!xxxDestroyWindow+0x390
b49f1dbc bf80d3f8 b9e40818 00000010 00000000 win32k!xxxRealDefWindowProc+0x1bd
b49f1de0 bf83f117 b9e40818 00000010 00000000 win32k!xxxDefWindowProc+0x107
b49f1e50 bf802dd1 e1b0d510 e1b0d510 00000000 win32k!xxxReceiveMessage+0x301
b49f1e7c bf83e90e 00000200 00000000 00000000 win32k!xxxSleepThread+0x8a
b49f1f18 bf80f5ef b9e5d5e0 00000002 00000000 win32k!xxxInterSendMsgEx+0x7f6
b49f1f64 bf80eda9 b9e5d5e0 00000002 00000000 win32k!xxxSendMessageTimeout+0x11f
b49f1f88 bf8465ba b9e5d5e0 00000002 00000000 win32k!xxxSendMessage+0x1b
b49f1fc4 bf846570 b9e5d5e0 e1b0d510 b9e40818 win32k!xxxDW_SendDestroyMessages+0x35
b49f1ff4 bf846cf7 b9e40818 004f010a 00000083 win32k!xxxDW_SendDestroyMessages+0x77
b49f2044 bf80afae 00000000 b9e40818 00000010 win32k!xxxDestroyWindow+0x390
b49f209c bf80d3f8 b9e40818 00000010 00000000 win32k!xxxRealDefWindowProc+0x1bd
b49f20c0 bf83f117 b9e40818 00000010 00000000 win32k!xxxDefWindowProc+0x107
b49f2130 bf802dd1 e1b0d510 e1b0d510 00000000 win32k!xxxReceiveMessage+0x301
b49f215c bf83e90e 00000200 00000000 00000000 win32k!xxxSleepThread+0x8a
b49f21f8 bf80f5ef b9e5d5e0 00000002 00000000 win32k!xxxInterSendMsgEx+0x7f6
b49f2244 bf80eda9 b9e5d5e0 00000002 00000000 win32k!xxxSendMessageTimeout+0x11f
b49f2268 bf8465ba b9e5d5e0 00000002 00000000 win32k!xxxSendMessage+0x1b
b49f22a4 bf846570 b9e5d5e0 e1b0d510 b9e40818 win32k!xxxDW_SendDestroyMessages+0x35
b49f22d4 bf846cf7 b9e40818 004f010a 00000083 win32k!xxxDW_SendDestroyMessages+0x77
b49f2324 bf80afae 00000000 b9e40818 00000010 win32k!xxxDestroyWindow+0x390
b49f237c bf80d3f8 b9e40818 00000010 00000000 win32k!xxxRealDefWindowProc+0x1bd
b49f23a0 bf83f117 b9e40818 00000010 00000000 win32k!xxxDefWindowProc+0x107
b49f2410 bf802dd1 e1b0d510 e1b0d510 00000000 win32k!xxxReceiveMessage+0x301
b49f243c bf83e90e 00000200 00000000 00000000 win32k!xxxSleepThread+0x8a
b49f24d8 bf80f5ef b9e5d5e0 00000002 00000000 win32k!xxxInterSendMsgEx+0x7f6
b49f2524 bf80eda9 b9e5d5e0 00000002 00000000 win32k!xxxSendMessageTimeout+0x11f

STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!StubGdiAlloc+a
bf805a2f ff750c          push    dword ptr [ebp+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!StubGdiAlloc+a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52f43e77

FAILURE_BUCKET_ID:  0x7f_8_win32k!StubGdiAlloc+a

BUCKET_ID:  0x7f_8_win32k!StubGdiAlloc+a

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

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

收藏
免费 0
支持
分享
最新回复 (3)
雪    币: 15
活跃值: (135)
能力值: ( LV2,RANK:10 )
在线值:
发帖
回帖
粉丝
2
其实我也是想同求助的....
2016-3-12 11:49
0
雪    币: 44
活跃值: (186)
能力值: ( LV2,RANK:10 )
在线值:
发帖
回帖
粉丝
3
什么单机游戏这么牛B呀?????
2016-3-12 12:09
0
雪    币: 190
活跃值: (10)
能力值: ( LV2,RANK:10 )
在线值:
发帖
回帖
粉丝
4
是魅影传奇3半单机版!
2016-3-12 13:39
0
游客
登录 | 注册 方可回帖
返回
//