Maplestory BSOD

[Joel96]

Hi guys, i installed windows 7 32-bit only my laptop recently.. and i installed maplestory to play also, when i go in to maplestory a box appeared and it says maplestory is incompatible with the version of windows. But i still click run program... and the ahn lab(gameguard) appeared loaded.... in maplestory, when i choose and click the gateway my laptop go in to Blue Screen Of Death and it restarted... is there anyway to fix tis?

 

[zigzag3143]

Hi guys, i installed windows 7 32-bit only my laptop recently.. and i installed maplestory to play also, when i go in to maplestory a box appeared and it says maplestory is incompatible with the version of windows. But i still click run program... and the ahn lab(gameguard) appeared loaded.... in maplestory, when i choose and click the gateway my laptop go in to Blue Screen Of Death and it restarted... is there anyway to fix tis?

We could be more useful if we had the actual DMP file that was created when the computer crashed. use these instructions to find and upload it. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html


ken

 

[Joel96]

BSOD

Hi when i click on the maplestory icon a box appeared and it says that maplestory is incompatible with the version of Windows but i still click run program... After that Ahn Lab(gameguard) appeared and it loaded.... When i am in maplestory while choosing gateway when i clicked malaysia BSOD appeared.

Here is the DMP file

 

[Joel96]

Ok got it

heres the dmp file... i also will post it in the crashes and debugging forum.

 

[zigzag3143]

Hi when i click on the maplestory icon a box appeared and it says that maplestory is incompatible with the version of Windows but i still click run program... After that Ahn Lab(gameguard) appeared and it loaded.... When i am in maplestory while choosing gateway when i clicked malaysia BSOD appeared.

Here is the DMP file

The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Let us know the results

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\032710-25646-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82a38000 PsLoadedModuleList = 0x82b80810
Debug session time: Sat Mar 27 04:04:47.359 2010 (GMT-4)
System Uptime: 0 days 1:27:50.029
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 82a7d377, adaf4cc0, 0}

***** 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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************

 

[Joel96]

erm hey tis time when i update it, it says that update completed but i dont understand about
-The open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center ) could u explain to me?

 

[Joel96]

erm hey r u thr? i'm waiting for your reply

 

[JMH]

erm hey tis time when i update it, it says that update completed but i dont understand about
-The open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center ) could u explain to me?

Hi Joel,
zigzag 3143 asked that you contact a Microsoft Support Professional via email, online or phone.They may be able to help you re the missing symbols issue.
Refer top right hand corner Windows 7 Solution Center
Hope that answers your question.
Let us know the result.
Jan.
View attachment 65168

 

[Joel96]

erm hey... i reinstalled my win 7 and chng it to 64-bit liao... its compatible... thx for the help~

 

[JMH]

erm hey... i reinstalled my win 7 and chng it to 64-bit liao... its compatible... thx for the help~

Joel,
Thanks for reporting back.
We shall mark your thread as completed.