Bug Launcher or FTB causing Blue Screen

  • Please make sure you are posting in the correct place. Server ads go here and modpack bugs go here
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
S

Simonqwadjke

New Member
Jul 29, 2019
25
0
0
Well for the past months I have been having frequent bsod errors, I know you think that this is unrelated to FTB but please read on.

This error only happens when playing feed the beast and no other time at all, this lead me to believe that the launcher is messing with the system and causing it to crash.
It crashes with bsod error IRQL_NOT_LESS_OR_EQUAL every single time.
Also before you flame me on this one saying I have faulty software or hardware, I want you to also keep in mind, I recently bought two new hard disks, SSD for main system drive for extra speed and stability plus its a whole new freshly installed windows that have not been tampered with in any way.
First time playing FTB on this new system with new hard drives and just about 20-30 minutes in I crash with blue scree.

If the developers could please take a look at this and help me troubleshoot the error.
 
You might wanna hop on IRC(the Chat tab at the top of the page) and talk to prog. (Note, might take a while for them to get to you.)
 
IRQL_NOT_LESS_OR_EQUAL

Explanation:

This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Click to expand...

Most likely dodgy RAM or driver.
The reason you're only getting this in FTB is that it uses a LOT of RAM making it more likely to hit the bad spot.

For RAM do this:
http://www.cnet.com/how-to/test-your-ram-with-windows-memory-diagnostic-tool/

For dodgy driver, update EVERYTHING

OR you've got a POS SSD that can't handle the constant read/write operations Minecraft generates, try running on a RAM-disk to solve this.

And one last thing, it is NOT FTB causing a bsod, it may trigger it but FTB/MC is not at fault you DO have faulty hardware or software.
 
You must log in or register to reply here.
Top Bottom