Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashing upon startup #12

Open
zzbeastszz opened this issue Mar 19, 2017 · 3 comments
Open

Crashing upon startup #12

zzbeastszz opened this issue Mar 19, 2017 · 3 comments

Comments

@zzbeastszz
Copy link

My computer freezes upon starting hyperbone

Windows 10 v10.0.14393
I7-5930k

@mudbeegit
Copy link

i have the same issues

@ranlincang
Copy link

win7 x64 bsod when start to execute "net start hyperbone" every time.
Unable to load image ??\F:\code\新建文件夹\bin\x64\Win7Debug\HyperBone.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for HyperBone.sys


  •                                                                         *
    
  •                    Bugcheck Analysis                                    *
    
  •                                                                         *
    

Use !analyze -v to get detailed debugging information.

BugCheck 20001, {1, 21, 0, 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 ***






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



Probably caused by : HyperBone.sys ( HyperBone!VmExitTripleFault+85 )

Followup: MachineOwner

@ranlincang
Copy link

033119-15225-01.zip
minidump
HyperBone-master.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants