MantisBT - DriverPacks BASE
View Issue Details
0000044DriverPacks BASEslipstreamerpublic2006-05-28 18:172006-05-29 14:09
razormoon 
BashratTheSneaky 
normalcrashalways
closedunable to reproduce 
6.05 
 
disc (CD/DVD)
all
1
RunOnceEx
0000044: BSOD: setupdd.sys
I 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. :)
No tags attached.
related to 0000042resolved BashratTheSneaky TXTSETUP.SIF: Invalid entries in [DiskSpaceRequirements] 
? bsodvm.bmp (921,654) 2006-05-28 18:18
http://bugtracker.driverpacks.net/file_download.php?file_id=25&type=bug
Issue History
2006-05-28 18:17razormoonNew Issue
2006-05-28 18:17razormoonDriverPacks => all
2006-05-28 18:17razormoonDriverPacks Method => 1
2006-05-28 18:17razormoonFinishing Method => RunOnceEx
2006-05-28 18:17razormoonInstallation Platform => disc (CD/DVD)
2006-05-28 18:18razormoonFile Added: bsodvm.bmp
2006-05-29 13:34BashratTheSneakyNote Added: 0000147
2006-05-29 13:34BashratTheSneakyRelationship addedrelated to 0000042
2006-05-29 13:37BashratTheSneakyNote Added: 0000148
2006-05-29 14:02razormoonNote Added: 0000150
2006-05-29 14:08BashratTheSneakyNote Added: 0000151
2006-05-29 14:08BashratTheSneakyResolutionopen => unable to reproduce
2006-05-29 14:09BashratTheSneakyStatusnew => assigned
2006-05-29 14:09BashratTheSneakyAssigned To => BashratTheSneaky
2006-05-29 14:09BashratTheSneakyStatusassigned => closed

Notes
(0000147)
BashratTheSneaky   
2006-05-29 13:34   
Impossibly caused by the DriverPacks, unless by bug 0000042. Please check this: http://support.microsoft.com/?kbid=330181. [^] 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!
(0000148)
BashratTheSneaky   
2006-05-29 13:37   
This one confirms the faulty RAM thing described in my previous note: http://support.microsoft.com/?kbid=171003. [^]

Or perhaps it's this one: http://support.microsoft.com/kb/873159/en-us. [^]
(0000150)
razormoon   
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.
(0000151)
BashratTheSneaky   
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+ (http://www.memtest.org/ [^]).