thx for the answer, nevertheless, my issue doesn't seems to be linked to a VST or i don't know excatly to determine it (if you have a simple way to do it..).
My last try to get an error on screen was quiet apocaliptic... corruption of NTFS structure following the crash. That's explain the delay in my asnwer (time to recover FS... i would like also to 'limit' the number of test even if a backup of my pc is currently on going....)
so let come back the initial issue: the last module which is loaded is "wave_wrap.AEX". then the programm (Pre7.0) is freezing, then crash leading to direct bios reboot (no additional message in between).
any idea, proposal ?
Thk you for the info. seems to match my case indeed.
i will try it (after end of my baclup :-/ ) and i will keep you post
Please do report - on your success!
For info: for user of HP product with Realtek audio componant:
i have found on HP site a driver update from 5.10.00.5211 to 5.10.005229
this update is announced as " Improves compatibility with Adobe Premier and Premier Elements video editing software."
Good candidate too ..
I will try this update first and if no improvement, then try the wave_warp.aex patch.
Good find. NLE programs, like PrE and PrPro, interact more closely with both the video driver and the audio driver, than almost any other programs will. That is why updating these is very important. Just a simple OS update, or hot-fix, can render them obsolete instantly. That is one reason that I have my Windows update set to manual, with just a reminder. I always know what I am updateing, and when the update is being done. I immediately test PrPRo, to check that nothing got broken along the way. That is better than having an automatic update happen, without my knowledge, and finding out later, that things are broken. When I update, I always plan on updating both the video and audio driver.
Good luck, and hope that this update helps you,
Indeed the audio driver has solved the issue.The crash was so strong (even no blue screen of death) that i was a little bit surprised that only a driver compatibility lead to such a result.
May be the update reference will be usefull for someone else.
Thank you for support and now that i can see how is looking like your (beautiful) product, i will be able to use it and have more question to ask to support !
You can close the frame. and again thank you for quick and efficient support.
I've had various driver issues reboot (no BSOD, just an instant reboot). Always, the Event Viewer has come to the rescue, at least pointing me to a driver. Now, the trail went cold at that point, as the OS did not furnish the details on WHICH driver, so one then needs to do much more detective work. In a perfect world, with a perfect OS, one could follow the trail, and find that it was caused by _____.dll, and then a Search would turn up more info on that, so one would know what to update, or at least address.
Good luck, and glad that things worked well,