BSOD IRQL_LESS_THAN_OR_EQUAL using Pinnacle Studio 14

[maurice99]

Pinnacle Studio 14 installed perfectly on this W7, but then struck BSOD frequently during rendering of disk images, and I suspect my attempts to implement the various fixes sugegsted elsewhere have fouled up thie installation.

If I can't get it working on re-installed W7 I shall try installing WinXP instead.

Many thanks for your fast responses - much appeciated!

Since then, I have re-installed W7 (Home) from scratch and done a complete software update.
Then re-installed Pinnacle Studio 14;no problem with there.

Despite all that, when I started my annual use of Studio recently, I got one BSOD whilst editing a video track, and three (all at different times) whilst creating a 4GB DVD image on hard drive (for output to a DVD).

The BSOD error was something like: IRQL_LESS_THAN_OR_EQUAL

You can see the W7 BSOD minidump for both occasions here:

1st was when editing:
http://dl.dropbox.com/u/10969499/bsod-110311-15178-01.dmp

2nd when rendering --> |Dvd file on internal drive:
http://dl.dropbox.com/u/10969499/bsod-110611-16317-01.dmp

(After the 3 BSOD's when generating the 4GB file, the 4th attempt succeeded and wrote the file to the DVD.)

What can be the problem with just reading from, rendering, and writing to an internal drive?

 

[zigzag3143]

Since then, I have re-installed W7 (Home) from scratch and done a complete software update.
Then re-installed Pinnacle Studio 14;no problem with there.

Despite all that, when I started my annual use of Studio recently, I got one BSOD whilst editing a video track, and three (all at different times) whilst creating a 4GB DVD image on hard drive (for output to a DVD).

The BSOD error was something like: IRQL_LESS_THAN_OR_EQUAL

You can see the W7 BSOD minidump for both occasions here:

1st was when editing:
http://dl.dropbox.com/u/10969499/bsod-110311-15178-01.dmp

2nd when rendering --> |Dvd file on internal drive:
http://dl.dropbox.com/u/10969499/bsod-110611-16317-01.dmp

(After the 3 BSOD's when generating the 4GB file, the 4th attempt succeeded and wrote the file to the DVD.)

What can be the problem with just reading from, rendering, and writing to an internal drive?

Two problems


1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
http://support.asus.com/download.as...D LE&p=1&s=32&os=29&hashedid=e7Zic83PvQSr80Lm

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOTbefore).

2- Memory exceptions

These crashes were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org/#downiso

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[maurice99]

OK - many thanks!

The ASACPI.sys driver currently there is dated 2005-03-29!
I shall install the later one, as suggested.

Running memtest-86 V3.4 showed a few errors, so am taking that up with the PC supplier (as still under warranty).
Guess the video editor really stresses memory, as I've had no problems otherwise.

In the meantime I shall press on with the DVD through the BSOD's - as I did last year (and eventually finished it), as I'm pushed for time these next few weeks and don't have time for complicated system re-hashes..

Thanks once again for your help; much appreciated....

 

[maurice99]

Strange - after runing memtest 2 days ago I have had no more BSOD's!
It's as if Memtest has cleaned up the memory (or whatever).

Fingers crossed...

 

[maurice99]

Two problems


1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
http://support.asus.com/download.as...D LE&p=1&s=32&os=29&hashedid=e7Zic83PvQSr80Lm

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOTbefore).

OK - I have now replaced faulty RAM, and downloaded that driver offer.

But what the download gives is a folder containing other folders.
When you say 'install it', what is the procedure?

N.B. In the d/l folders I see a file:

MB_WIN7_ATK/64/WIN7/Asacpi.sys (14/5/09 9KB)

whereas in C:\Windows\System32\drivers I see a file:

ASACPI.sys (29/3/05 8KB)
(note the difference in use of upper case)

Do you mean simply replace the latter with the former?
What about the difference in upper case letters?

 

[zigzag3143]

OK - I have now replaced faulty RAM, and downloaded that driver offer.

But what the download gives is a folder containing other folders.
When you say 'install it', what is the procedure?

N.B. In the d/l folders I see a file:

MB_WIN7_ATK/64/WIN7/Asacpi.sys (14/5/09 9KB)

whereas in C:\Windows\System32\drivers I see a file:

ASACPI.sys (29/3/05 8KB)
(note the difference in use of upper case)

Do you mean simply replace the latter with the former?
What about the difference in upper case letters?

I am unsure and since I dont have an ASUS board cant investigate. What does the instructions say?

 

[maurice99]

I am unsure and since I dont have an ASUS board cant investigate. What does the instructions say?

Well, i couldn't find any instructions , but found an 'application', with which I extracted from the download package., then executed the application in the latter, and that did something very fast and did a system restart.
After the restart I find:

C:\Windows\System32\drivers\ASACPI.sys - a 16KB file with a date of 4/12/11 (Dec.4 here in UK).

So - perhaps that did the trick? Is there a simple way of testing that new driver?

At least the system appears to be working OK. Fingers crossed!
Many thanks for responding - much appreciated...

Merry Xmas to all...

 

[Elmer BeFuddled]

Just my 2p's worth. The date 4/12/11 is the date you installed. If you look at the actual drivers properties (it's in C:\Windows\System32\drivers**), the details tab will give you its actual date.

The capitalisation makes/means nothing.

HTH. A fellow Brit.

**You knew that.

 

[zigzag3143]

Well, i couldn't find any instructions , but found an 'application', with which I extracted from the download package., then executed the application in the latter, and that did something very fast and did a system restart.
After the restart I find:

C:\Windows\System32\drivers\ASACPI.sys - a 16KB file with a date of 4/12/11 (Dec.4 here in UK).

So - perhaps that did the trick? Is there a simple way of testing that new driver?

At least the system appears to be working OK. Fingers crossed!
Many thanks for responding - much appreciated...

Merry Xmas to all...

Thanks EBF and Merry Christmas to all.

Ken

 

[maurice99]

Just my 2p's worth. The date 4/12/11 is the date you installed. If you look at the actual drivers properties (it's in C:\Windows\System32\drivers**), the details tab will give you its actual date.

Jeez, another senior moment!

The 'create' date is 2009/5/14, which I believe is the date of the latest driver.

 

[Elmer BeFuddled]

Jeez, another senior moment!

We all get 'em! And that's the newer/latest/good enough driver.