Jump to content











Photo
- - - - -

BSOD by a script!


  • Please log in to reply
14 replies to this topic

#1 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 June 2008 - 04:22 PM

I have at the moment the strange, but reproduceable case that running Create ISO causes a BSOD.

Irq not less or equal <-- That's a driver related - not an application related error.
Where do we have a driver in Create ISO?
Nowhere!

So i guess this has something do with you, Super-Peter and your Buildmodel. :thumbup:

;)

#2 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 02 June 2008 - 04:44 PM

I have at the moment the strange, but reproduceable case that running Create ISO causes a BSOD.

Irq not less or equal <-- That's a driver related - not an application related error.
Where do we have a driver in Create ISO?
Nowhere!

So i guess this has something do with you, Super-Peter and your Buildmodel. ;)

:thumbup:

Thanks for the congratulations :thumbup:

buildModel.script version 54 is unchanged since a long time. Therefore I think that it cannot be responsible primarily.
But of course, whenever there is a doubt that something I initiated is responsible for some issues, I want to examine the topic.

Please try to build a list what you have changed (not only new scripts, but also options) since it ran well.

How do you reproduce?
Or occurs it every time you try to build an ISO?
Try to use BootSDI instead of CreateISO.

BTW: 'Drivers' in CreateISO maybe used by mkisofs internally.

Peter

#3 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 June 2008 - 05:10 PM

Thanks for the congratulations ;)

buildModel.script version 54 is unchanged since a long time. Therefore I think that it cannot be responsible primarily.

Please try to build a list what you have changed (not only new scripts, but also options) since it ran well.

How do you reproduce?
Or occurs it every time you try to build an ISO?
Try to use BootSDI instead of CreateISO.

BTW: 'Drivers' in CreateISO maybe used by mkisofs internally.

Peter

It happend 3 out of 4 builds before i made the connection that WB is the guilty party.
I then ran another 2 times Create ISO without rebuilding the project. Just clicking create ISO. BSOD

I don't think that you did anything new to or with your buildmodel.
The point is simply that there is/should be no way, how this error can occur.
If it would happen with SDI script, i would say ok. There is a installing and using of a driver.
But where is there a driver in Create ISO, or connected to it?

:thumbup:

#4 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 June 2008 - 05:14 PM

If i run create ISO script after i deleted Target temp and workbench, i get a few error messages, but no BSOD.

;)

#5 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 02 June 2008 - 05:18 PM

The point is simply that there is/should be no way, how this error can occur.
If it would happen with SDI script, i would say ok. There is a installing and using of a driver.
But where is there a driver in Create ISO, or connected to it?

;)

Currently in answering this question I am as 'stupid' as you: No idea.
Maybe it helps if you really try BootSDI several times.

Another suggestion:
Comment out the start of mkisofs.
BTW: subsequent CreateISO you can only make after 'ReOpen'. I do not know what happens if you run CreateISO twice w/o ReOpen.

I'm still thinking that it depends on your system.
If it is a special constellation of your project, maybe we can find the reason inside WinBuilder / scripts.
But it is also propably that it depends on something in the OS core of your system:

If you google, you find a lot of topics 'Until now everything has been ok, but since some days I get an Irq not less or equal'

Peter

#6 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 June 2008 - 05:29 PM

If you google, you find a lot of topics 'Until now everything has been ok, but since some days I get an Irq not less or equal'

I know driver conflicts can be caused by nothing more than a bit flipping over in the registry.
But there are still drivers needed to BSOD.
And since i can trigger this with the push of a button, means one of the two drivers in question must be utilized by that script.

;)


PS: Only two changes. Replaced MMCscript v9 with v11 and added regCompact.script

#7 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 02 June 2008 - 05:47 PM

IPS: Only two changes. Replaced MMCscript v9 with v11 and added regCompact.script

And as experienced programmer / bug hunter you already reversed these changes and got the same result?

Peter

#8 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 June 2008 - 06:31 PM

And as experienced programmer / bug hunter you already reversed these changes and got the same result?

Peter

I did a new build without both. No BSOD.
added MMC without rebuild. No BSOD.
added regcompact without rebuild. NO BSOD.

So the only thing we know for sure is that, there is a constellation of settings which can make Create ISO trigger a BSOD.

Will try another build with all in.

;)

#9 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 02 June 2008 - 06:35 PM

I did a new build without both. No BSOD.
added MMC without rebuild. No BSOD.
added regcompact without rebuild. NO BSOD.

So the only thing we know for sure is that, there is a constellation of settings which can make Create ISO trigger a BSOD.

Will try another build with all in.

;)

That's a good intermediate result!

Peter :thumbup:

#10 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 June 2008 - 06:56 PM

Build with all in. No BSOD.
So 3 out of 5 caused a BSOD. :thumbup:

;)

#11 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 02 June 2008 - 07:00 PM

Build with all in. No BSOD.
So 3 out of 5 caused a BSOD. :thumbup:

;)

My assumption that something in your host system is wrong, is changing to a statement!

Peter

#12 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 June 2008 - 07:29 PM

My assumption that something in your host system is wrong, is changing to a statement!

Nothing against that idea, but it takes two to tango!
And the other one is somewhere in WB.

;)

#13 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 02 June 2008 - 07:33 PM

Nothing against that idea, but it takes two to tango!
And the other one is somewhere in WB.

:thumbup:

Tell me where (or how to find the place), and I'll try to change ;)

Peter

#14 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 02 June 2008 - 07:37 PM

Let's stop kidding.

If it is not an issue of your system (and I asssume that it is an issue of your system):
What are the known facts?
How can we continue?

The first question should be answered as detailled as possible, by you (please just collect, do not link to other posts).
Then you and me and perhaps some othe forum's members can try to anser question #2.

Peter

#15 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 June 2008 - 08:08 PM

IF i would have been smart, i would have saved the always crash build, before doing other tests. ;)

If i happen to produce another one, i will send you a copy.

:thumbup:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users