冒险岛一点大区就蓝屏

Posted 2023-02-14

我家的冒险岛怎么开了一选择风之大陆就蓝屏啊,高手来!已经重下过了~但是还是这样~急啊

现在冒险岛 很多人都有个小宠物！ 做个漂亮的发型 手戴几个戒指 全身一套现金装备 有事没事的喇叭漫天飞 其实那些人的点券都是刷出来的``其实这么多的东西，你只要30多块就可以拥有。 ­转入正题，先准备冒险岛游戏充值卡一张(充值卡可以在网吧或者小报亭购买）。方法是利用漏洞！[细节方法见下文]。方法已经更新。­在冒险岛游戏充值页面下，隐藏了一个叫 zgshenda 的资料处理中心的数据文件，它是用来记录充过的充值卡的,当然它是没有办法直接访问的，不过我们可以通过它实现刷点券的目的! ­首先，你要准备一张没有用过的充值卡，随便多少钱都可以.想刷的快点就用面值大一点的。省钱就用10元面值的充值卡。最好是用30面值的，数据不能过多的访问。 ­去充值：用户帐号 注意！！：首先不能直接填你的账号，要填 zgshenda 冒险岛原码账号 ­重新输入帐户 同样填 zgshenda 冒险岛原码账号 接着输入充值卡卡号 填你准备的充值卡卡号 ­充值卡密码 填你准备的充值卡密码 ­这样会弹出是不是给账号 zgshenda 充值，然后点“确定”了，开始跳转页面了，因为 zgshenda 是系统数据号！系统会告诉你给账户 zgshenda 充值失败！ ­接下来是关键了：现在刷新页面，系统就会提示出错:页面不能刷新，别管它，然后按返回键，返回冲值页面，重复上面的步骤，帐户还填 zgshenda 卡还是填你购买的卡号和密码继续冲，系统将会和刚才一样出现充值失败。这样反复15次 ­最后一次：账号填你自己的账号，注意 最后一次一定要填写自己账号，系统会提示冲值成功！这样会造成个假象，充值系统会打一个假的封包，这样之前刷的都会充入你自己的冒险岛帐号！ ­总数是你重复冲15次的总和。那么你的点卷就翻15倍了 10快的回变成150快！­注意: ­1.刷出的点券可购买游戏商城里的现金道具. ­2.最后一次一定要填你自己的账号,这样才能充到你自己的账号上。 ­3.建议刷点券次数不要过多，同一IP大量充值容易被SD发现 ­4.充值过的点卡系统会提示，此卡无效 ­只建议刷到10倍!~ 参考技术A 这是用WinDBG工具检测蓝屏原因后的分析结果
　　
　　Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
　　Copyright (c) Microsoft Corporation. All rights reserved.
　　
　　
　　Loading Dump File [C:\WINDOWS\Minidump\Mini052709-06.dmp]
　　Mini Kernel Dump File: Only registers and stack trace are available
　　
　　Symbol search path is: *** Invalid ***
　　****************************************************************************
　　* Symbol loading may be unreliable without a symbol search path. *
　　* Use .symfix to have the debugger choose a symbol path. *
　　* After setting your symbol path, use .reload to refresh symbol locations. *
　　****************************************************************************
　　Executable search path is:
　　*********************************************************************
　　* Symbols can not be loaded because symbol path is not initialized. *
　　* *
　　* The Symbol Path can be set by: *
　　* using the _NT_SYMBOL_PATH environment variable. *
　　* using the -y <symbol_path> argument when starting the debugger. *
　　* using .sympath and .sympath+ *
　　*********************************************************************
　　Unable to load image ntoskrnl.exe, Win32 error 0n2
　　*** WARNING: Unable to verify timestamp for ntoskrnl.exe
　　*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
　　Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
　　Product: WinNt, suite: TerminalServer SingleUserTS
　　Machine Name:
　　Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
　　Debug session time: Wed May 27 22:06:16.000 2009 (GMT+8)
　　System Uptime: 0 days 0:13:54.740
　　*********************************************************************
　　* Symbols can not be loaded because symbol path is not initialized. *
　　* *
　　* The Symbol Path can be set by: *
　　* using the _NT_SYMBOL_PATH environment variable. *
　　* using the -y <symbol_path> argument when starting the debugger. *
　　* using .sympath and .sympath+ *
　　*********************************************************************
　　Unable to load image ntoskrnl.exe, Win32 error 0n2
　　*** WARNING: Unable to verify timestamp for ntoskrnl.exe
　　*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
　　Loading Kernel Symbols
　　...............................................................
　　......................................................
　　Loading User Symbols
　　Loading unloaded module list
　　..............
　　*******************************************************************************
　　* *
　　* Bugcheck Analysis *
　　* *
　　*******************************************************************************
　　
　　Use !analyze -v to get detailed debugging information.
　　
　　BugCheck C2, 7, cd4, b5218475, b697280c
　　
　　***** Kernel symbols are WRONG. Please fix symbols to do analysis.
　　
　　*** WARNING: Unable to verify timestamp for EQSysSecure.sys
　　*** ERROR: Module load completed but symbols could not be loaded for EQSysSecure.sys
　　*** WARNING: Unable to verify timestamp for safeboxkrnl.sys
　　*** ERROR: Module load completed but symbols could not be loaded for safeboxkrnl.sys
　　*** WARNING: Unable to verify timestamp for swenum.sys
　　*** ERROR: Module load completed but symbols could not be loaded for swenum.sys
　　*************************************************************************
　　*** ***
　　*** ***
　　*** Your debugger is not using the correct symbols ***
　　*** ***
　　*** In order for this command to work properly, your symbol path ***
　　*** must point to .pdb files that have full type information. ***
　　*** ***
　　*** Certain .pdb files (such as the public OS symbols) do not ***
　　*** contain the required information. Contact the group that ***
　　*** provided you with these symbols if you need this command to ***
　　*** work. ***
　　*** ***
　　*** Type referenced: nt!_KPRCB ***
　　*** ***
　　*************************************************************************
　　*************************************************************************
　　*** ***
　　*** ***
　　*** Your debugger is not using the correct symbols ***
　　*** ***
　　*** In order for this command to work properly, your symbol path ***
　　*** must point to .pdb files that have full type information. ***
　　*** ***
　　*** Certain .pdb files (such as the public OS symbols) do not ***
　　*** contain the required information. Contact the group that ***
　　*** provided you with these symbols if you need this command to ***
　　*** work. ***
　　*** ***
　　*** Type referenced: nt!_KPRCB ***
　　*** ***
　　*************************************************************************
　　*********************************************************************
　　* Symbols can not be loaded because symbol path is not initialized. *
　　* *
　　* The Symbol Path can be set by: *
　　* using the _NT_SYMBOL_PATH environment variable. *
　　* using the -y <symbol_path> argument when starting the debugger. *
　　* using .sympath and .sympath+ *
　　*********************************************************************
　　*********************************************************************
　　* Symbols can not be loaded because symbol path is not initialized. *
　　* *
　　* The Symbol Path can be set by: *
　　* using the _NT_SYMBOL_PATH environment variable. *
　　* using the -y <symbol_path> argument when starting the debugger. *
　　* using .sympath and .sympath+ *
　　*********************************************************************
　　Probably caused by : EQSysSecure.sys ( EQSysSecure+6c2e )
　　
　　Followup: MachineOwner
　　---------
　　
　　1: kd> !analyze -v
　　*******************************************************************************
　　* *
　　* Bugcheck Analysis *
　　* *
　　*******************************************************************************
　　
　　BAD_POOL_CALLER (c2)
　　The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
　　Arguments:
　　Arg1: 00000007, Attempt to free pool which was already freed
　　Arg2: 00000cd4, (reserved)
　　Arg3: b5218475, Memory contents of the pool block
　　Arg4: b697280c, Address of the block of pool being deallocated
　　
　　Debugging Details:
　　------------------
　　
　　***** Kernel symbols are WRONG. Please fix symbols to do analysis.
　　
　　*************************************************************************
　　*** ***
　　*** ***
　　*** Your debugger is not using the correct symbols ***
　　*** ***
　　*** In order for this command to work properly, your symbol path ***
　　*** must point to .pdb files that have full type information. ***
　　*** ***
　　*** Certain .pdb files (such as the public OS symbols) do not ***
　　*** contain the required information. Contact the group that ***
　　*** provided you with these symbols if you need this command to ***
　　*** work. ***
　　*** ***
　　*** Type referenced: nt!_KPRCB ***
　　*** ***
　　*************************************************************************
　　*************************************************************************
　　*** ***
　　*** ***
　　*** Your debugger is not using the correct symbols ***
　　*** ***
　　*** In order for this command to work properly, your symbol path ***
　　*** must point to .pdb files that have full type information. ***
　　*** ***
　　*** Certain .pdb files (such as the public OS symbols) do not ***
　　*** contain the required information. Contact the group that ***
　　*** provided you with these symbols if you need this command to ***
　　*** work. ***
　　*** ***
　　*** Type referenced: nt!_KPRCB ***
　　*** ***
　　*************************************************************************
　　*********************************************************************
　　* Symbols can not be loaded because symbol path is not initialized. *
　　* *
　　* The Symbol Path can be set by: *
　　* using the _NT_SYMBOL_PATH environment variable. *
　　* using the -y <symbol_path> argument when starting the debugger. *
　　* using .sympath and .sympath+ *
　　*********************************************************************
　　*********************************************************************
　　* Symbols can not be loaded because symbol path is not initialized. *
　　* *
　　* The Symbol Path can be set by: *
　　* using the _NT_SYMBOL_PATH environment variable. *
　　* using the -y <symbol_path> argument when starting the debugger. *
　　* using .sympath and .sympath+ *
　　*********************************************************************
　　
　　ADDITIONAL_DEBUG_TEXT:
　　Use '!findthebuild' command to search for the target build information.
　　If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
　　
　　FAULTING_MODULE: 804d8000 nt
　　
　　DEBUG_FLR_IMAGE_TIMESTAMP: 4939205b
　　
　　BUGCHECK_STR: 0xc2_7
　　
　　CUSTOMER_CRASH_COUNT: 6
　　
　　DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
　　
　　LAST_CONTROL_TRANSFER: from 8054c583 to 804faf43
　　
　　STACK_TEXT:
　　WARNING: Stack unwind information not available. Following frames may be wrong.
　　b697278c 8054c583 000000c2 00000007 00000cd4 nt+0x22f43
　　b69727dc 8054c95f b697280c 00000000 b6972854 nt+0x74583
　　b69727ec b520dc2e b697280c b520ddda b5258d00 nt+0x7495f
　　b6972854 b7431eb7 0000018c 00000000 00000000 EQSysSecure+0x6c2e
　　b6972d30 8054262c 0426dd40 0000018c 00000000 safeboxkrnl+0xaeb7
　　b6972d64 7c92e514 badb0d00 0426dd18 00000000 nt+0x6a62c
　　b6972d68 badb0d00 0426dd18 00000000 00000000 0x7c92e514
　　b6972d6c 0426dd18 00000000 00000000 00000000 swenum+0xd00
　　b6972d70 00000000 00000000 00000000 00000000 0x426dd18
　　
　　
　　STACK_COMMAND: kb
　　
　　FOLLOWUP_IP:
　　EQSysSecure+6c2e
　　b520dc2e ?? ???
　　
　　SYMBOL_STACK_INDEX: 3
　　
　　SYMBOL_NAME: EQSysSecure+6c2e
　　
　　FOLLOWUP_NAME: MachineOwner
　　
　　MODULE_NAME: EQSysSecure
　　
　　IMAGE_NAME: EQSysSecure.sys
　　
　　BUCKET_ID: WRONG_SYMBOLS
　　
　　Followup: MachineOwner
这就是驱动不兼容的问题，在某些程序下启动就会蓝屏，就像惠普的CQ45系列的笔记本一样装了XP很容易蓝屏
下个显卡就搞定了、莪也有过这种经历…… 参考技术B 你打开安装目录的试试帮你调试的！ 希望可以帮到你O(∩_∩)O~