[PD-dev] [ pure-data-Bugs-1508138 ] program crash leads to system crash
SourceForge.net
noreply at sourceforge.net
Sun Jun 18 22:01:13 CEST 2006
Bugs item #1508138, was opened at 2006-06-18 15:47
Message generated for change (Comment added) made by jmmmp
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1508138&group_id=55736
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: Open
Resolution: None
Priority: 5
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: João Miguel Pais (jmmmp)
Date: 2006-06-18 22: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 19: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&group_id=55736
More information about the Pd-dev
mailing list