Jump to content

4.2 Install - Crashing System [Unrelated to SB]


Recommended Posts

Edit-

 

Update

I've been getting BSOD regularly since upgrading from WIN 7 to WIN 10 on 18 JAN.

 

It has been hard to pinpoint exactly why- but one indicator seems to be when installing ANY new software. 

 

Speckfire did some analysis on my dump files: It seems to be related to one file, snapman.sys - a file related to an older hard drive imaging program called Acronis True Image, most likely used during my PC build (custom build) seven years ago, to image my hard drive. 

 

I have uninstalled the program 12hrs ago with no BSOD since. 

 

This may be the solution (I really damn hope so!) but to be clear this had nothing to do with SB.

 

 

 

===========================================

 

At various points, the install is causing my system to crash. 

 

Install 1 - Made it 50% through the Bundle

Install 2 - 75%

Install 3 - SB program install ~ 75%

Install 4 - SB Program Install ~25%

Install 5 - SB Program Install ~80%

Install 5 - Bundle ~25%

Install 6 - 100% install, crashed on updating Codemeter (I updated it separately, so I should be ok. 4.2 loads)

 

WIN 10 Blue Screen of Death - K MODE Exception Not Handled

WIN 10 Blue Screen of Death - ATTEMPTED SWITCH FROM DPC

 

 

No driver is listed as a culprit

 

Ran a memory diagnostic - no issues

Ensured that 'Quick Startup' is disabled. 

 

I did also just upgrade to WIN 10 home, last week. 

Edited by Apocalypse 31
Link to post
Share on other sites
  • Apocalypse 31 changed the title to 4.2 Install - Crashing System
2 minutes ago, Retro said:

I don't think that's the same issue.. certainly a 'you are not allowed to install this software' measure would not be to BSOD the PC?

For me it did. Untill switching to the dev-mode

Link to post
Share on other sites

Maybe, instead of the bundle installer, use the traditional method?

(At least until we got this sorted; and if that one crashes too, then we know that the problem isn't with the bundle installer.)

Link to post
Share on other sites

The bundle installer itself checks the version number of Pro PE apps in the registry, downloads installer files, hashes files to verify they are good if already there, and executes the installers/uninstallers.  It doesn't do anything exotic, nothing that would cause a kernel error.  Is it possible to temporarily disable your AV software during install?  What AV software is running?

 

Thanks!

Link to post
Share on other sites
1 hour ago, Ssnake said:

Do you happen to have a Windows S version?

I don't think we support these.

I do not. 

 

Having this issue consistently now - right around 95% install on SB Setup

 

Have disabled anti-virus, firewall, and running the exe as admin. 

 

I'm getting BSOD: ATTEMPTED SWITCH FROM DPC

Edited by Apocalypse 31
Link to post
Share on other sites

You mentioned you recently upgraded to windows 10.  It's possible some of the hardware in the pc does not like it.  Did you try tracking down windows 10 certified drivers to install or did windows 10 just download what it needed itself?

Link to post
Share on other sites

I just installed to another drive. It worked.

 

Then it crashed when installing codemeter.

 

EDIT - Codemeter is currently installed in ProgramFiles. I was told that this is not a great location to install....anything in WIN 10

Edited by Apocalypse 31
Link to post
Share on other sites
  • Apocalypse 31 changed the title to 4.2 Install - Crashing System [Unrelated to SB]

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...