Blue Screen after every new product installation

[Guest]

Everytime I install a new program, Norton 2007, QuickBooks Pro 2007, Roxio
Creator 9 Suite, I get an blue screen on startup with a different error.
This time the error was win32K.sys page_fault_in_nonpaged_area. It takes me
three times or more to get my computer to reboot so I can do a system restore
before I installed the new program. I have a Toshiba laptop with Vista
premium with Intel Core 2 CPU T5200 1.60 GHZ with 2038 ram installed. I
can't use any of these new programs. Going nuts. Thanks.

 

[Kerry Brown]

Test your RAM.

www.memtest.org

Let the test run for several hours.

 

[Betty]

Are you sure it's compatible with Vista?? I don't remember being this afraid
of trying new things with Win XP. What's so odd is I just bought a new
computer when Win 98 was coming out, another new computer when Win XP was
coming out and now another new computer when Vista came out. LOL

Betty

 

[Lang Murphy]

Betty,

The main point of this NG is to help folks who are experiencing problems.
You're not often going to find posts in here of folks going "Hey, another
great day with Vista." As another poster pointed out, this may be a "Bad
RAM" issue. Maybe not, but not every problem reported in here is even
related to "Vista the OS." Most are device driver issues, legacy hw issues,
or just malcontents spreading FUD.

How's Vista working for you? If you're afraid to try "new" things, remember,
not all existing SW is Vista ready. For good or ill. Make sure you have a
system restore point before installing anything that's not logoed for Vista.
(And probably even those that are... I would've done that with XP too...)
Then, if you have a problem, you can roll back to your previous system
restore point and carry on with nothing lost but whatever time you took to
install the "new" software/hardware/whatever.

Lang

 

[Kerry Brown]

All of the programs listed in the OP have problems in XP let alone Vista.
Nevertheless intermittent, different errors on startup is almost always bad
RAM, closely followed by a bad hard drive. Vista uses a scheme where it
loads into different areas of RAM each time it is loaded. This trick stops a
lot of malware that is hard coded to certain memory locations. It also
causes bad RAM to be very obvious with many different errors on boot up.
Marginal RAM that previously worked for years in XP now seems to go bad.
What is really happening is that XP always loaded into the same spot in
memory and the location that's bad never had program code loaded into it so
it was never noticed that it was bad.

 

[Guest]

Lang,

I've had to do a system restore after every install of my new products.
That lets me back into my computer, but the point is I am out the money I've
spent on these products. All of the products are "Vista" ready and the
technical support for the products are basically useless so no refunds! That
is why I am asking this group for help.

 

[Kerry Brown]

Did you test your RAM?

 

[Zim Babwe]

First of all get rid of Norton 2007. Download AVG FREE, that is a much
better antivirus and it's free. The current version works with Vista (I
have it on my PC) and has a small footprint. Norton is bloated, complex,
causes system problems, slows down your system, and is just plain nasty.

 

[Thor]

Amen, Zim Babwe, Amen!

Thor

"Zim Babwe"

First of all get rid of Norton 2007. Download AVG FREE, that is a much
better antivirus and it's free. The current version works with Vista (I
have it on my PC) and has a small footprint. Norton is bloated, complex,
causes system problems, slows down your system, and is just plain nasty.

 

[Guest]

Yes, no problems

Did you test your RAM?

 

[Guest]

I did, thank u

First of all get rid of Norton 2007. Download AVG FREE, that is a much
better antivirus and it's free. The current version works with Vista (I
have it on my PC) and has a small footprint. Norton is bloated, complex,
causes system problems, slows down your system, and is just plain nasty.

 

[Kerry Brown]

If removing Norton didn't fix the problem I'd test the hard drive next. It
may be a software problem but from your original post it sounds more like
hardware to me.