Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000044DriverPacks BASEslipstreamerpublic2006-05-28 18:172006-05-29 14:09
Assigned ToBashratTheSneaky 
StatusclosedResolutionunable to reproduce 
PlatformOSOS Version
Product Version6.05 
Target VersionFixed in Version 
Summary0000044: BSOD: setupdd.sys
DescriptionI should have mentioned this one before, but I'll tell you why I didn't. As you know, I've been testing the heck out of your stripstreamer and so, I've been using VMWare lots lately. The following BSOD can be reproduced using all dp, M1, runonceex and KTD all. I've reproduced this in CP605, but for whatever reason didn't think much of it til I came across it again in 605. Both times were in VMware. And from what I remember, the error was cleared when NOT using KTD or when using only some KTD, though I don't recall which. I will TRY to test later with different packs. :)
TagsNo tags attached.
Destination OS Platform
Installation Platformdisc (CD/DVD)
DriverPacks Method1
DriverPacks Finisher MethodRunOnceEx
Attached Files? file icon bsodvm.bmp [^] (921,654 bytes) 2006-05-28 18:18

- Relationships
related to 0000042resolvedBashratTheSneaky TXTSETUP.SIF: Invalid entries in [DiskSpaceRequirements] 

-  Notes
BashratTheSneaky (administrator)
2006-05-29 13:34

Impossibly caused by the DriverPacks, unless by bug 0000042. Please check this: [^] Note that this incorrectly functioning RAM can also result in 'corrupt RAM' inside VMWare, since VMWare simply reserves a certain chunk of your memory, which might contain the corrupt part!
BashratTheSneaky (administrator)
2006-05-29 13:37

This one confirms the faulty RAM thing described in my previous note: [^]

Or perhaps it's this one: [^]
razormoon (reporter)
2006-05-29 14:02

I know it's a funky error. I only get with M1 and KTD ALL. There seems to be no issue with this, other than me posting it and it being in VMware.
BashratTheSneaky (administrator)
2006-05-29 14:08

Well... it might disappear when you use a different Windows XP disc as source...

By the way, to verify that you do NOT have faulty RAM, you could use Memtest86+ ( [^]).

- Issue History
Date Modified Username Field Change
2006-05-28 18:17 razormoon New Issue
2006-05-28 18:17 razormoon DriverPacks => all
2006-05-28 18:17 razormoon DriverPacks Method => 1
2006-05-28 18:17 razormoon Finishing Method => RunOnceEx
2006-05-28 18:17 razormoon Installation Platform => disc (CD/DVD)
2006-05-28 18:18 razormoon File Added: bsodvm.bmp
2006-05-29 13:34 BashratTheSneaky Note Added: 0000147
2006-05-29 13:34 BashratTheSneaky Relationship added related to 0000042
2006-05-29 13:37 BashratTheSneaky Note Added: 0000148
2006-05-29 14:02 razormoon Note Added: 0000150
2006-05-29 14:08 BashratTheSneaky Note Added: 0000151
2006-05-29 14:08 BashratTheSneaky Resolution open => unable to reproduce
2006-05-29 14:09 BashratTheSneaky Status new => assigned
2006-05-29 14:09 BashratTheSneaky Assigned To => BashratTheSneaky
2006-05-29 14:09 BashratTheSneaky Status assigned => closed

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker