#21  
Old 5th August 2015, 06:07 AM
the_randomizer's Avatar
the_randomizer the_randomizer is offline
Alpha Tester
Project Supporter
Senior Member
 
Join Date: Sep 2008
Location: USA
Posts: 1,134
Default

Then gee, maybe not update to Windows 10 or rollback to 7? There's no solution for the crash, might as well go back to the previous OS, if it ain't broke, why fix it?
__________________
My rig:
CPU: Intel Core i7 4470 3.4 GHz to 3.9 GHz
Video card:: MSI nVidia GTX 970 4 GB GDDR5
OS: Windows 7 Professional 64-bit
RAM: 16 GB DDR3 SDRAM 10600
HDD: 2 x Western Digital 1 TB HDDs
Monitor: 23" Asus Full HD LED

Oh, and Snes9x > Zsnes in every way
Reply With Quote
  #22  
Old 5th August 2015, 09:12 AM
DaMan69 DaMan69 is offline
Member
 
Join Date: Feb 2015
Posts: 77
Default

Quote:
Originally Posted by the_randomizer View Post
Hey, hey, hey, don't be a douche.
Sorry dude, didn't mean to flip you off. I meant �� is a reason to upgrade.
Reply With Quote
  #23  
Old 5th August 2015, 10:07 AM
Ambient_Malice Ambient_Malice is offline
Senior Member
 
Join Date: Dec 2014
Posts: 179
Default

Quote:
Originally Posted by the_randomizer View Post
Then gee, maybe not update to Windows 10 or rollback to 7? There's no solution for the crash, might as well go back to the previous OS, if it ain't broke, why fix it?
What do you mean there's no solution? It's as simple as finding the commit that started triggering BSODs somewhere between 1.7 and 2.1.
Reply With Quote
  #24  
Old 5th August 2015, 10:27 AM
LuigiBlood LuigiBlood is offline
Alpha Tester
Project Supporter
Junior Member
 
Join Date: Jul 2015
Posts: 19
Default

Quote:
Originally Posted by the_randomizer View Post
Then gee, maybe not update to Windows 10 or rollback to 7? There's no solution for the crash, might as well go back to the previous OS, if it ain't broke, why fix it?
You repeat way too much to be a simple opinion, man. We get it.

Quote:
Originally Posted by Ambient_Malice View Post
What do you mean there's no solution? It's as simple as finding the commit that started triggering BSODs somewhere between 1.7 and 2.1.
And this.
I remember having BSODs on 1.7.0.50 on Windows 7. (leaked, and made sure it's not the virus one)
Since then it's fixed with that update but still. If that info helps out...
EDIT: Also it's not always when booting a ROM. Tends to be a timed "bomb".

Last edited by LuigiBlood; 5th August 2015 at 10:30 AM.
Reply With Quote
  #25  
Old 6th August 2015, 08:05 AM
retroben's Avatar
retroben retroben is offline
Alpha Tester
Project Supporter
Senior Member
 
Join Date: Jul 2013
Posts: 681
Default

Cool,you use that one too?

I actually nabbed it the brief moment it was on emucr that one fateful day.
Reply With Quote
  #26  
Old 6th August 2015, 02:36 PM
LuigiBlood LuigiBlood is offline
Alpha Tester
Project Supporter
Junior Member
 
Join Date: Jul 2015
Posts: 19
Default

Quote:
Originally Posted by retroben View Post
Cool,you use that one too?

I actually nabbed it the brief moment it was on emucr that one fateful day.
I didn't even know it was on EmuCR. I got it from somewhere else.
Reply With Quote
  #27  
Old 13th August 2015, 09:02 PM
NUK3 TH3 WHAL35 NUK3 TH3 WHAL35 is offline
Senior Member
 
Join Date: Jan 2015
Posts: 121
Default

Quote:
Originally Posted by medievil View Post
forget what I posted above.. I had win 7 comp enabled... disable it and back to blue screen crash win32kfull.sys error
Have you been able to go full screen? Every time I go full screen I get an error message saying ChangeWindow Exception in the form of a d3d8 error. Then it's followed by an Exception Caught error line: 265. I can play fine... in windowed mode. Any compatibility mode I run it in results in the same error.
Reply With Quote
  #28  
Old 13th August 2015, 10:19 PM
V1del V1del is offline
Project Supporter
Senior Member
 
Join Date: Feb 2012
Posts: 442
Default

Jabo's seems to have a problem with Win10, you can use another video plugin like glide64 which has better compatibility anyway
Reply With Quote
  #29  
Old 15th August 2015, 08:25 PM
NUK3 TH3 WHAL35 NUK3 TH3 WHAL35 is offline
Senior Member
 
Join Date: Jan 2015
Posts: 121
Default

Thanks V1del!

I probably should have figured it out on my own, but I'v been busy playing PC games and putting them through the ringer on Windows 10 . My issues were 2 things. 1, I couldn't choose a game within the list in the emu without a program must close error. 2, I couldn't go Full Screen without getting an Exception error. I still can't choose a game within the emu (I can only go through File, Open...), but can NOW go Full Screen using GLideN64 (haven't really tried others yet).
Reply With Quote
  #30  
Old 15th August 2015, 11:37 PM
TONPumper TONPumper is offline
Junior Member
 
Join Date: Jan 2014
Posts: 13
Default

I can't get Project64 to detect my xbox controller. I went to the site to download the driver again, but it didn't have one for Windows 10. I see that there is a driver installed but my roms complain there is no controller. I can play The Binding of Isaac with the controller with no problems.
Reply With Quote
Reply

Tags
crashes, windows 10

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT. The time now is 03:54 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.