Your PC ran into a problem and needs to restart?

Discuss music production with Ableton Live.
Post Reply
fjg3003
Posts: 1
Joined: Mon Jan 16, 2017 11:38 pm

Your PC ran into a problem and needs to restart?

Post by fjg3003 » Mon Jan 16, 2017 11:48 pm

So this is something new to me, "Your PC ran into a problem and needs to restart, we're just gathering some error info...." and then there it says "Stop Code: DRIVER_IRQL_NOT_LESS_OR_EQUAL" and underneath that it said "What failed: WDF01000.sys"

I have no idea what this means and it has happened multiple times already. It usually happens when i'm running ABLETON LIVE and or when I connect the the launchpad or launchkey(is it ok to use both at the same time?) to my laptop via USB. I reinstalled the program and it still happens.I don't know what causes this, I already cleaned and backed up everything to an external drive.

I have a Dell Inspiron 13-7359 Signature edition with 8GB of ram and 256 SSD and using windows 10.

I kindly appreciate any help or comment as i'm new to this software.

thanks :D

yur2die4
Posts: 7333
Joined: Sat Oct 03, 2009 3:02 am
Location: Menasha, Wisconsin
Contact:

Re: Your PC ran into a problem and needs to restart?

Post by yur2die4 » Mon Jan 16, 2017 11:58 pm

Have you contacted Ableton support? I think these are the kinds of things they might be good at troubleshooting. (Possibly Novation)

albieg
Posts: 19
Joined: Thu Nov 17, 2016 1:15 pm

Re: Your PC ran into a problem and needs to restart?

Post by albieg » Tue Jan 17, 2017 11:17 am

Your PC is generating an unhandled exception which cannot be resolved by the kernel, therefore the computer needs to stop with what is called, historically, a BSOD (Blue screen of death). That's the equivalent of a Linux Kernel panic, which means an unexpected error which is unrecoverable and leads to a complete halt of the operating system after a short stint in a special kernel mode that is used to gather information and inform the user of a critical, unrecoverable error.

BSODs happen for a number of extremely different reasons, some of them less than obvious. A number of them are hardware related, and in this case it seems so. The component which is experiencing the failure is the Kernel Mode Framework Driver, which manages drivers which have a low level interaction with the kernel. It looks like the framework is unable to handle some kernel mode hardware properly. Again, it can be for a number of reasons.

Understanding which driver (or component) can be is a bit tricky. However, if your computer is configured to generate Minidumps (procedure on Ten Forums here for Win10, it's not much different for other Windows OSes) you can analyze your minidump (which should be generated inside the \Windows\Minidump folder) online here:

http://www.osronline.com/page.cfm?name=Analyze

Since the upload is limited to 40MB, you cannot analyze full memory dumps. Minidumps contain a reduced image of the memory of your PC at the time of the crash, including the most important stuff, which means the stack of the instructions which were executed by the processor just before the crash. Based on the severity of the error, sometimes dumps aren't generated.

It should be noted, however, that sometimes hardware problems are created by particular conditions which can influence the correct operation of the involved hardware: power problems, usb root hub problems (including low power and bad handling of multiple peripherals connected to the same hub), driver problems, bad handling of power settings due to power management, RAM problems (unlikely in this case) and other malfunctions. The dump analysis may give important information related to the specific hardware which is involved in the crash. Additional info may be gathered from the Event Viewer, in system and application view. The analysis of different dumps may help gathering additional info.

Full dumps can be analysed with WinDBG, which does the same job of the analysis online but requires installation and configuration whenever used with the proper set of symbols.

Post Reply