ECD Creator 9 & Windows Vista

[Sam67_uk]

Just did a clean install of Vista Home Premium and installed EMC 9 Suite as a complete install. Rebooted PC on completion, but get a blue screen BAD_POOL_CALLER. PC goes round in circles until you choose "last known good configuration" then it will boot into Vista OK.

 

When you click on the Roxio icon to start off the program nothing happens. So far nothing but problems with Roxio, not impressed

 

Tried reinstalled it for the second time, same problem again.

 

Anyone any ideas?

 

Thanks

 

Sam

[tbrewst]

Depending on which V9 you have it's not Vista compatible yet.Do a search of these forums regarding Vista and you'll see what I mean.

[Sam67_uk]

Depending on which V9 you have it's not Vista compatible yet.Do a search of these forums regarding Vista and you'll see what I mean.

 

 

Its the full retail boxed version of Easy Media Creator 9 Suite which according to the box is compatible with Vista and was bought as a deal with vista.

[gi7omy]

There is a problem with a 0 day Vista patch (that is one issued on the day of release). Check here

 

http://kb.roxio.com/content/kb/Creator/000131CR

[silver]

There is a problem with a 0 day Vista patch (that is one issued on the day of release). Check here

 

http://kb.roxio.com/content/kb/Creator/000131CR

 

It's probably the same issue. "BAD_POOL_CALLER" is the result of a memory addressing issue or bad RAM. Drivers are loaded into RAM on boot and unfortunately they don't all play well together.

[Sam67_uk]

It's probably the same issue. "BAD_POOL_CALLER" is the result of a memory addressing issue or bad RAM. Drivers are loaded into RAM on boot and unfortunately they don't all play well together.

 

 

Thanks for the link. I uninstalled that particular windows update and rebooted and then installed EMC9 again, this time I did a custom install, only installing the parts of the program I knew I'd use. Before I rebooted I clicked on the roxio icon and the program loaded fine, great I thought, now I'll reboot. On reboot the same BAD_POOL_CALLER blue screen appeared again

 

On reboot, last know good config didn't work. Thank goodness for system restore!! So I know it's not the MS KB update causing the problem.

 

What a nice piece of software (not!)

 

Sam

[silver]

Thanks for the link. I uninstalled that particular windows update and rebooted and then installed EMC9 again, this time I did a custom install, only installing the parts of the program I knew I'd use. Before I rebooted I clicked on the roxio icon and the program loaded fine, great I thought, now I'll reboot. On reboot the same BAD_POOL_CALLER blue screen appeared again

 

On reboot, last know good config didn't work. Thank goodness for system restore!! So I know it's not the MS KB update causing the problem.

 

What a nice piece of software (not!)

 

Sam

 

I'm actually really starting to like it. Admittedly I'm not exactly the "average user" and I've tweaked it a little here and there. Now it's running at least as fast as XPSP2 if not in fact faster. Note that I really am not going to install any but the most innocuous updates. All I've put in on this system was the updated nVidia PCI-E driver, audio driver and ATI video drivers. Haven't even loaded an AV yet though that gets done right before I hit the rack.

 

You might also find this interesting :

 

http://windowsvistablog.com/blogs/windowsv...nvironment.aspx

 

Did you happen to clear the startup and services in MSCONFIG ?

[Sam67_uk]

I'm actually really starting to like it. Admittedly I'm not exactly the "average user" and I've tweaked it a little here and there. Now it's running at least as fast as XPSP2 if not in fact faster. Note that I really am not going to install any but the most innocuous updates. All I've put in on this system was the updated nVidia PCI-E driver, audio driver and ATI video drivers. Haven't even loaded an AV yet though that gets done right before I hit the rack.

 

You might also find this interesting :

 

http://windowsvistablog.com/blogs/windowsv...nvironment.aspx

 

Did you happen to clear the startup and services in MSCONFIG ?

 

Ohh I like Windows Vista, it's EMC9 I don't like

 

I've been doing a bit of RAM swapping. I have 3 slots 1GB, 512MB and 256MB to give 1.75GB total. To cut a very long story short, the only chip which is stable and doesn't give the error is the 512MB one. Any of the other 2 chips installed either togather or on their own gives me the error. I've tried them in different memory slots, same error. I can run EMC9 when I eventually get into Windows. Of course I can't run Vista on 512MB RAM no matter what Microsoft say!

 

It's very frustrating when all the RAM happily lived together until ROXIO came along then all these problems. I can't see why they should appear with just one program. Now I have to go to the expense of buying a GB of RAM just to see whether I can cure the problem or not!

[gi7omy]

Could be anything really stressing the RAM there - I've seen it happen out of the blue on other machines (it's fine if left alone and you don't do anything, but falls over when you start)

 

Vista is a lot more demanding - add in something that really loads things up like video rendering and the RAM will fall over. A quick check - back down the bus speed a notch or two and see if it will stabilise

[grandpabruce]

Could be anything really stressing the RAM there - I've seen it happen out of the blue on other machines (it's fine if left alone and you don't do anything, but falls over when you start)

 

Vista is a lot more demanding - add in something that really loads things up like video rendering and the RAM will fall over. A quick check - back down the bus speed a notch or two and see if it will stabilise

 

I don't know what mobo he has, but if it has 4 slots, and only 3 are used, the DIMMs will run in single channel mode. That and the fact that you should only install identical type and size DIMM pairs in each channel.

 

Since my mobo only takes the first generation DDR RAM and not the DDR2 RAM, maybe this doesn't apply anymore.

[silver]

Ohh I like Windows Vista, it's EMC9 I don't like

I personally like a challenge. I wonder if Roxio does ?

 

I've been doing a bit of RAM swapping. I have 3 slots 1GB, 512MB and 256MB to give 1.75GB total. To cut a very long story short, the only chip which is stable and doesn't give the error is the 512MB one. Any of the other 2 chips installed either togather or on their own gives me the error. I've tried them in different memory slots, same error. I can run EMC9 when I eventually get into Windows.

And no problems at all during the installation ? I'm thinking memory configuration issue here.

 

Of course I can't run Vista on 512MB RAM no matter what Microsoft say!

The definition of the term "run" has many interpretations. Look at Dubya ! (Rot row ! He said the D-word !) I ran Windows 2000 Pro on a P1 - 100 MHz proc for a little bit out of necessity. Combined with 768MB of RAM, it functioned albeit pretty slowly.

 

It's very frustrating when all the RAM happily lived together until ROXIO came along then all these problems. I can't see why they should appear with just one program. Now I have to go to the expense of buying a GB of RAM just to see whether I can cure the problem or not!

I'd run the Vista RAM diags. Also are you running an nForce 3-based motherboard by any chance ? If that's the case I'd recommend getting 2X1GB sticks that are twins. Running unmatched memory in a motherboard designed to run in a dual channel configuration is asking for trouble. I know as I had a MSI nForce 3 motherboard. Had one pair of top notch GEIL DIMM's and wanted to add a third 512 DIMM howver the the timing was 2.5 vs. the CL2 of the GEIL. The whole system slowed down and errors became something of a concern when I heaped up the RAM. And as you can already see, Vista really heaps it up ! What I'm getting at is that your system may have difficulty with all of the memory addressing that's going on. Particularly if you have a video card that has less than 256MB of RAM and might be addressing your RAM. With a 128MB card it wasn't even an issue with XP however cards with workarounds such as TurboCache and such marketing BS can be another source of problems. I trust the chipset manufacturers to make decent chipsets to address the RAM however when a video card starts doing it, well they simply are designed to peacefully co-exist in my opinion.

 

Could be anything really stressing the RAM there - I've seen it happen out of the blue on other machines (it's

fine if left alone and you don't do anything, but falls over when you start)

Vista is a lot more demanding - add in something that really loads things up like video rendering and the RAM will fall over. A quick check - back down the bus speed a notch or two and see if it will stabilise

We're thinking along the same lines here though I believe that the bus speed should automatically clock down. Particularly if it's an AMD system where the northbridge controller is on the proc. I'm wondering if his video card isn't placing stuff in RAM. The new-ish cards by ATI and nVidia use things like Turbo-cache and other such nonsense to offset the cost of memory increasing the price of the card. Unfortunately I have an ATI X600 w/256MB RAM w.TurboCache and now my system is using 512MB after being left on all day. Fortunately that's well down from the 768 that it was using earlier during indexing. Anyway, one way of checking this would be to disable the Vista theme engine and change the systems theme back to Windows Classic mode.

[gi7omy]

The problem I had was an AMD - if run at full speed XP BSODed (now there's a nice word - think I'll copyleft it). The mobo set the bus speed at CPU default - what happened was one stick of RAM couldn't manage and fell over. Dropping the clock down to run it at about .2 GHz less cured the problem (brought the FSB down a notch or two because they're clock-locked).

The difference in performance - negligible

 

Vista is a resource hog and will stress out components that just can't cope. Toss in, as I said, any app that makes demands on the system and it's a guaranteed BSOD