Bugs item #1508138, was opened at 2006-06-18 09:47 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1508138...
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: pd-extended Group: v0.39.2
Status: Closed Resolution: Invalid
Priority: 5 Private: No Submitted By: João Miguel Pais (jmmmp) Assigned to: Nobody/Anonymous (nobody) Summary: program crash leads to system crash
Initial Comment: If pd crashes once (for whichever reason it may be), when the program is loaded again a system error occurs, and a blue screen appears. The error message of the blue screen is
IRQL_NOT_LESS_OR_EQUAL *** STOP: 0X0000000A (0X00000004, 0X00000002, 0X00000000, 0X804E39A7)
Therefore, if pd crashes, it is necessary to reboot the system in order to avoid a system crash (logging out doesn't help).
Pd-ext 0.39-2 t3 XP Prof
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-12 00:55
Message: Logged In: YES user_id=27104 Originator: NO
a STOP 0x0A message generally means either bad drivers or bad hardware. Microsoft says "Typically, this error occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software. "
http://support.microsoft.com/kb/314063
Pd really shouldn't be able to cause a blue screen on its own, I think that even Windows isn't that bad.
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig) Date: 2006-10-10 09:13
Message: Logged In: YES user_id=564396
"I don't have a patch, because it was corrected already (I don't remember now)."
does this mean that it works now? can we close this?
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody) Date: 2006-06-19 02:49
Message: Logged In: NO
then also try to test your RAM sanity, with software like memtest86.... it could be a bad bank of ram...
----------------------------------------------------------------------
Comment By: João Miguel Pais (jmmmp) Date: 2006-06-18 16:01
Message: Logged In: YES user_id=1523458
The problem has nothing to do with audio, as actually in most of the cases I didn't had audio on. I don't have a patch, because it was corrected already (I don't remember now). But the error that made pd crash the first time might had to do with a cpu overload (or whatever is it called) due to an infinite loop. Which kind of hardware info is necessary? I guess saying IBM Thinkpad R51 1,6Mhz 1GbRam doesn't help much.
----------------------------------------------------------------------
Comment By: Thomas Grill (xovo) Date: 2006-06-18 13:24
Message: Logged In: YES user_id=350252
Although the information given about the crash is close to nothing (for whichever reason that may be), it's almost certainly a driver bug, not a pure pd bug. You should include info about what you are doing (include patches,
description etc.) and about your hardware. And you should try to find newer/ different drivers for your audio hardware and see if the problem persists.
----------------------------------------------------------------------
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1508138...