Roblox Player crashes on clean install of Windows 10!!!

Join Date: 2015-06-15
Post Count: 14

#182881157Tuesday, February 02, 2016 2:45 PM GMT

Roblox Player crashes on start after being installed in a fresh, clean installation of Windows, with only Firefox installed. Endless install loop when trying to play Roblox Games. Pushing Play only downloads another and another and another installer. I lost count of how many times I tried. It was working before. Builder's Club ----> GOOD-BYE!! Roblox Player ----> You'd better get your act together!! Developers: Please PM me for the debug dump file.

nityesha

Join Date: 2015-06-15
Post Count: 14

#182881416Tuesday, February 02, 2016 2:56 PM GMT

Microsoft Troubleshooter determines the Roblox Player as an incompatible program with Windows 10!! This is on a fresh and clean installation of Windows. Builderman's post does not let me send mail to him. Could they care less??? Does anyone care for the dump file? --- I believe all the developers are still on a long vacation. Break instruction exception - code 80000003 (first chance)

nityesha

Join Date: 2015-06-15
Post Count: 14

#182883340Tuesday, February 02, 2016 4:24 PM GMT

Since I switched to machine with AMD FX-6300 processor, Roblox did not work anymore. Anyone who has this CPU with Roblox working?

ReiDaTecnologia

Join Date: 2014-09-07
Post Count: 6

#182883480Tuesday, February 02, 2016 4:29 PM GMT

If you continue on windows 7 none of this would have happened!

RabidApocalypse

Join Date: 2012-03-03
Post Count: 188

#182901050Tuesday, February 02, 2016 11:12 PM GMT

Probably some bug in ROBLOX or Windows 10. It's not your CPU. ROBLOX ran 100% on my second PC with an FX-8350.My main build with my i7 4790k and 980 Ti destroy every game, lol.

nityesha

Join Date: 2015-06-15
Post Count: 14

#182933552Wednesday, February 03, 2016 3:37 PM GMT

Thanks for your encouragement, RabidApocalypse :-)

nityesha

Join Date: 2015-06-15
Post Count: 14

#182933649Wednesday, February 03, 2016 3:40 PM GMT

Already reported the issue to Microsoft. A Microsoft technician spent one hour via remote access trying to fix the problem, but no avail. :-(