2 installs on same machine

T

Tim B

Hello,

I have a Windows 7 machine that blue screens regularly after about an hour
of use. As part of the troubleshooting of this issue, I would like to do a
second install on another existing partition, as a dual boot setup. The
version is 64-bit pro OEM. Would MS licensing allow this?

Thanks,

Tim B
 
T

Tester

Before doing that, you want to investigate why you are having this Blue
Screen of death. Could it that you have installed a new driver that is
not compatible? Could it be that you have installed a new RAM module
that is defective or incompatible. Could it that you installed a new
program that had incompatible DLLs in conflict with your existing ones.

If you don't find these things out, then you will never know it.

As to re-installing on a new partition, the answer is YES you can do it
because it is still the same machine that can be used by only one person
at any one time.

How about resetting the machine to factory settings? Some OEMs have
this facility by hiding the image from normal use or protecting it from
corruption.

hth
 
T

Tim B

Tim said:
Hello,

I have a Windows 7 machine that blue screens regularly after about an
hour of use. As part of the troubleshooting of this issue, I would like
to do a second install on another existing partition, as a dual boot
setup. The version is 64-bit pro OEM. Would MS licensing allow this?

Thanks,

Tim B

"Tester" wrote in message
Before doing that, you want to investigate why you are having this Blue
Screen of death. Could it that you have installed a new driver that is
not compatible? Could it be that you have installed a new RAM module
that is defective or incompatible. Could it that you installed a new
program that had incompatible DLLs in conflict with your existing ones.

If you don't find these things out, then you will never know it.

As to re-installing on a new partition, the answer is YES you can do it
because it is still the same machine that can be used by only one person
at any one time.

How about resetting the machine to factory settings? Some OEMs have
this facility by hiding the image from normal use or protecting it from
corruption.

hth


Tester, thanks for the reply. The blue screens have been happening for
several months, and I'm not sure what I may have installed that may have
brought them on. But around the time of the start of the blue screens, I
did remove an ssd that I had installed as an extra drive.

I recently tested my RAM and it was fine. By doing a second install and
seeing if the same issue occurred again, I was hoping to determine if the
issue is hardware related.

This machine was assembled by me, so no factory settings or restore image.

Tim B
 
S

Sunny Bard

Tester said:
Before doing that, you want to investigate why you are having this Blue
Screen of death.
Errr ... he said he wanted to perform a second install *BECAUSE* of the
bluescreen, maybe to have a usable temporary installation while he fixes
the first installation, maybe to help diagnose the BSOD.
 
C

Char Jackson

The blue screens have been happening for
several months, and I'm not sure what I may have installed that may have
brought them on. But around the time of the start of the blue screens, I
did remove an ssd that I had installed as an extra drive.

I recently tested my RAM and it was fine. By doing a second install and
seeing if the same issue occurred again, I was hoping to determine if the
issue is hardware related.

This machine was assembled by me, so no factory settings or restore image.
You'll probably want this handy little (free) utility to help you
analyze the BSOD's.

<http://www.nirsoft.net/utils/blue_screen_view.html>

As you may know, the STOP code as well as the offending file
information can be key to discovering the cause of the crashes.
Armed with that info, Google is your friend, or post back here.
 
R

R. C. White

Hi, Tim.

Your computer is putting up that blue screen in a desperate attempt to TELL
you "where it hurts". But Windows comes set - by default - to simply reboot
when it puts up the BSOD. (It also writes about the problem in its log
file, but I've never learned how to read those.) Trouble is, the reboot
happens so quickly that all you see is the blue flash on the screen, with no
chance to read it. As we all learn early in our computer experience, a
simple reboot does fix many transient glitches, so I suppose this default
setting is good for most users, especially newbies. But to diagnose what
the BSOD is trying to tell you, you need to change the default setting so
that you can read what it's trying to tell you. That's easy to do - after
you mouse-click your way down to that page:

Start | Control Panel | System | Advanced system settings (you'll need to
furnish Administrator credentials to get past here) | Advanced (tab) |
Startup and recovery / Settings button.

Finally, we are at the right page. Under System failure, UNcheck the box
for Automatically restart. Then OK your way out. Done!

Next time the BSOD happens, the blue screen will stay up until YOU push the
hardware Reset button, so you'll have all the time you need to read that
page and write down the important information. About half the page is
"boilerplate" which sounds important but is seldom helpful and often
misleading. But you should see a STOP code and some TEXT (probably
ALL_CAPS) and some long hexadecimal numbers. THOSE are the important codes
that you need. Even if they don't make sense to you, copy them verbatim and
post them here. Some of the gurus who read this newsgroup (not me!) can
read those codes and point you in the right direction. Or, since you built
your own system, you probably can Bingle for the codes and decipher them
yourself. (You might want to start at http://www.aumha.org/a/stop.htm ;
that page hasn't been updated for a while, but most of the codes haven't
changed in decades.)

But, that might not be the right troubleshooting path, in your case. You
said, "I have a Windows 7 machine that blue screens regularly after about an
hour of use." My immediate suspicion with that symptom is HEAT. Something
in your environment might be causing your computer to overheat to the point
of failure, and it takes about an hour for it to get that hot. Dust bunnies
clogging your computer's fans or vents, perhaps? Maybe a can of compressed
air - judiciously applied - will solve your BSOD problem. ;<}

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-2010)
Windows Live Mail 2011 (Build 15.4.3508.1109) in Win7 Ultimate x64 SP1


"Tim B" wrote in message
Hello,

I have a Windows 7 machine that blue screens regularly after about an hour
of use. As part of the troubleshooting of this issue, I would like to do a
second install on another existing partition, as a dual boot setup. The
version is 64-bit pro OEM. Would MS licensing allow this?

Thanks,

Tim B
 
C

Char Jackson

Your computer is putting up that blue screen in a desperate attempt to TELL
you "where it hurts". But Windows comes set - by default - to simply reboot
when it puts up the BSOD. ....
But to diagnose what
the BSOD is trying to tell you, you need to change the default setting so
that you can read what it's trying to tell you.
RC,
Good info but I wanted to remind you that the program I linked earlier
in this thread, Nirsoft's Blue Screen View, is able to read all of the
crash dumps and recreate all of the BSOD screens after the fact. So
technically, you don't need to change the default 'reboot' behavior if
you don't want to.
 
R

R. C. White

Hi, Char.

Thanks for that info. I haven't tried that app so I can't comment on it.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-2010)
Windows Live Mail 2011 (Build 15.4.3508.1109) in Win7 Ultimate x64 SP1


"Char Jackson" wrote in message

Your computer is putting up that blue screen in a desperate attempt to TELL
you "where it hurts". But Windows comes set - by default - to simply
reboot
when it puts up the BSOD. ....
But to diagnose what
the BSOD is trying to tell you, you need to change the default setting so
that you can read what it's trying to tell you.
RC,
Good info but I wanted to remind you that the program I linked earlier
in this thread, Nirsoft's Blue Screen View, is able to read all of the
crash dumps and recreate all of the BSOD screens after the fact. So
technically, you don't need to change the default 'reboot' behavior if
you don't want to.
 
T

Tim B

Just as a follow-up, I'd like to mention that I did a diagnostic on my hard
drive anc found it had some unrepairable bad blocks. I RMA'ed it and cloned
my old drive to the new one, and no troubles since.

"Tim B" wrote in message
Hello,

I have a Windows 7 machine that blue screens regularly after about an hour
of use. As part of the troubleshooting of this issue, I would like to do a
second install on another existing partition, as a dual boot setup. The
version is 64-bit pro OEM. Would MS licensing allow this?

Thanks,

Tim B
 
R

R. C. White

Hi, Tim.

Thanks for the feedback. Glad you got it fixed. ;<)

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-2010)
Windows Live Mail 2011 (Build 15.4.3508.1109) in Win7 Ultimate x64 SP1


"Tim B" wrote in message
Just as a follow-up, I'd like to mention that I did a diagnostic on my hard
drive anc found it had some unrepairable bad blocks. I RMA'ed it and cloned
my old drive to the new one, and no troubles since.

"Tim B" wrote in message
Hello,

I have a Windows 7 machine that blue screens regularly after about an hour
of use. As part of the troubleshooting of this issue, I would like to do a
second install on another existing partition, as a dual boot setup. The
version is 64-bit pro OEM. Would MS licensing allow this?

Thanks,

Tim B
 
S

Seum

R. C. White said:
Hi, Tim.

Thanks for the feedback. Glad you got it fixed. ;<)

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-2010)
Windows Live Mail 2011 (Build 15.4.3508.1109) in Win7 Ultimate x64 SP1


"Tim B" wrote in message
Just as a follow-up, I'd like to mention that I did a diagnostic on my hard
drive anc found it had some unrepairable bad blocks. I RMA'ed it and cloned
my old drive to the new one, and no troubles since.

"Tim B" wrote in message
Hello,

I have a Windows 7 machine that blue screens regularly after about an hour
of use. As part of the troubleshooting of this issue, I would like to do a
second install on another existing partition, as a dual boot setup. The
version is 64-bit pro OEM. Would MS licensing allow this?

Thanks,

Tim B
I tried to install a Win2K OS on a new Win 7 machine and it did not
work. I inquired about this and was told that MS was responsible. I also
learned that you could copy the existing Win 7 to another drive
temporarily, then remove the Win 7 and replace it with the Win2k.
Finally re-install Win 7 on a different partition, so you have 2 OSs on
the same machine. A lot of work though.
 
R

Rob

I tried to install a Win2K OS on a new Win 7 machine and it did not
work. I inquired about this and was told that MS was responsible. I also
learned that you could copy the existing Win 7 to another drive
temporarily, then remove the Win 7 and replace it with the Win2k.
Finally re-install Win 7 on a different partition, so you have 2 OSs on
the same machine. A lot of work though.
"I inquired about this and was told that MS was responsible."

Well, the problem really is: "How would an 11 year old operating
system (Windows 2000) installation CD know anything about an
existing later OS, such as Win7?"
It has always been the case that a later MS OS can be installed in
addition to an earlier one, but not the other way around.
It can be done though, you just need to search for the methods
available, such as this one, which is not difficult:

http://www.thpc.info/dual/win7/dualboot_win7+2k_on_win7.html
HTH
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top