Can you provide system details (brand, model, board, chipset, etc.)? It may help.
What type of boot media are you using (USB flash drive/CD)? Does it error with both types?
You should be fine with the 32-bit version.
Blue Screen When Booting with TeraByte WinPE
-
TeraByte Support(PP)
- Posts: 1646
- Joined: Fri Aug 12, 2011 12:51 am
Re: Blue Screen When Booting with TeraByte WinPE
Built by me...
•CPU: Intel Wolfdale Core 2 Duo E8500 3.16 GHz
•Mobo: Gigabyte GA-EP45-UD3R
•Chipset: Intel P45 + ICH10R
•RAM: G. Skill DDR2 800MHz 5-5-5-15 (2GB x 2)
•GPU: MSI 460GTX 768 MB
•Optical Drive: Sony Optiarc AD-7220S DVD±R/RW
•OS: Windows 7 Home Premium x64 SP1
•Intel Rapid Storage Technology v11.7.0.1013 (RAID + AHCI driver)
NO overclocking or weird RAM timings!
I've been using CD-RW media.
•CPU: Intel Wolfdale Core 2 Duo E8500 3.16 GHz
•Mobo: Gigabyte GA-EP45-UD3R
•Chipset: Intel P45 + ICH10R
•RAM: G. Skill DDR2 800MHz 5-5-5-15 (2GB x 2)
•GPU: MSI 460GTX 768 MB
•Optical Drive: Sony Optiarc AD-7220S DVD±R/RW
•OS: Windows 7 Home Premium x64 SP1
•Intel Rapid Storage Technology v11.7.0.1013 (RAID + AHCI driver)
NO overclocking or weird RAM timings!
I've been using CD-RW media.
-
TeraByte Support
- Posts: 3629
- Joined: Thu May 05, 2011 10:37 pm
Re: Blue Screen When Booting with TeraByte WinPE
You've always have had the option of using dmraid via typing "1
startraid=dmraid" at the boot prompt. Or creating a customized version with
that already enabled.
However you should try 2.92.
"pablo" wrote in message news:8791@public.image...
TAC109 wrote:
"I'm interested to know what problems you are having with versions of IFL
later than 2.89, thanks."
It's v2.79, not v2.89.
With v2.80, there was a change from using dmraid by default, to using mdadm
by default. IFL would no longer recognize my drives properly and was
unusable on my desktop. Tom Pfeifer of Terabyte Support was kind enough to
send me a custom ISO that worked with v2.80 and that's what I've been using
for the last year and a half along with IFW v2.80.
There were also a couple of bugs with my system and IFL that were cured with
workarounds.
startraid=dmraid" at the boot prompt. Or creating a customized version with
that already enabled.
However you should try 2.92.
"pablo" wrote in message news:8791@public.image...
TAC109 wrote:
"I'm interested to know what problems you are having with versions of IFL
later than 2.89, thanks."
It's v2.79, not v2.89.
With v2.80, there was a change from using dmraid by default, to using mdadm
by default. IFL would no longer recognize my drives properly and was
unusable on my desktop. Tom Pfeifer of Terabyte Support was kind enough to
send me a custom ISO that worked with v2.80 and that's what I've been using
for the last year and a half along with IFW v2.80.
There were also a couple of bugs with my system and IFL that were cured with
workarounds.
-
TeraByte Support(TP)
- Posts: 305
- Joined: Wed Aug 31, 2011 4:22 pm
Re: Blue Screen When Booting with TeraByte WinPE
pablo wrote:
> TAC109 wrote:
> "I'm interested to know what problems you are having with versions
> of IFL later than 2.89, thanks."
>
> It's v2.79, not v2.89.
>
> With v2.80, there was a change from using dmraid by default, to using mdadm
> by default. IFL would no longer recognize my drives properly and was
> unusable on my desktop. Tom Pfeifer of Terabyte Support was kind enough to
> send me a custom ISO that worked with v2.80 and that's what I've been using
> for the last year and a half along with IFW v2.80.
On the IFL issue:
The 'mdadm' utility has been updated with fixes several times since IFL 2.80, and IFL 2.92 is currently using the latest released version 3.3.2. But if you're still having this problem with IFL 2.92, please create a report and email it to support (support@terabyteunlimited.com) so we can look at the captured 'mdadm' log messages and other data in the report.
To create the report, just boot IFL 2.92 normally (without any boot parameters), and then create the IFL report. If needed, see this KB article for how to create a report: http://www.terabyteunlimited.com/kb/article.php?id=585
> TAC109 wrote:
> "I'm interested to know what problems you are having with versions
> of IFL later than 2.89, thanks."
>
> It's v2.79, not v2.89.
>
> With v2.80, there was a change from using dmraid by default, to using mdadm
> by default. IFL would no longer recognize my drives properly and was
> unusable on my desktop. Tom Pfeifer of Terabyte Support was kind enough to
> send me a custom ISO that worked with v2.80 and that's what I've been using
> for the last year and a half along with IFW v2.80.
On the IFL issue:
The 'mdadm' utility has been updated with fixes several times since IFL 2.80, and IFL 2.92 is currently using the latest released version 3.3.2. But if you're still having this problem with IFL 2.92, please create a report and email it to support (support@terabyteunlimited.com) so we can look at the captured 'mdadm' log messages and other data in the report.
To create the report, just boot IFL 2.92 normally (without any boot parameters), and then create the IFL report. If needed, see this KB article for how to create a report: http://www.terabyteunlimited.com/kb/article.php?id=585
Re: Blue Screen When Booting with TeraByte WinPE
After updating IFW to v2.95, I decided to burn a new TBWinPE disk using AIK v3.1 (Win 7, SP1). The 32-bit recovery disk worked just fine and, for the heck of it, I thought I'd give the 64-bit disk another try with AIK 3.1. I really thought that it would blue screen my machine, but I was pleasantly surprised to find that it worked just as well as the 32-bit version. I don't know what changed, but it's nice to have a 64-bit disk that works.
I'm using TBWinPE exclusively now for restores and I've thrown out all my IFL disks. IFL just isn't compatible with my system and I'll never use it again. IFD still works but it's slow and doesn't have all the nice features of TBWinPE.
I'm using TBWinPE exclusively now for restores and I've thrown out all my IFL disks. IFL just isn't compatible with my system and I'll never use it again. IFD still works but it's slow and doesn't have all the nice features of TBWinPE.