DriverPacks.net Forum - [solved] BSOD 0x7B using UBCD4Win on VIA P4M266A motherboard

Re: [solved] BSOD 0x7B using UBCD4Win on VIA P4M266A motherboard

2008-06-07T02:59:17Z

I am using the posted from Dietmar ntdetect.com, what _exactly_ it does/does not I don't think is published, at least it helps when USB bus is reset, windows not to lose connection to the USB disk.
It cures most of the 0x7B BSODs when starting from USB.
http://www.911cd.net/forums//index.php? … 1&st=0
http://www.msfn.org/board/0x0000007B-Bl … ntry738009

In my case it had nothing to do with mass storage pack. Even if booting PE from the CD, with USB disk was attached resulted in 7B. I just didn't expect USB disk to affect it, and blamed the last changed thing- mass storage pack.
Remove USB disk- boots OK, add it, replace ntdetect.com on the CD- boots OK.
Start from the USB disk- 7B, replace ntdetect.com - OK.
Just another silly BIOS.

The interesting part was that 7B usually means inaccessible _BOOT_ device, and the USB disk was not such.

Similar issue- boot XP setup from USB. On most systems if you don't have the driver for SATA controller, it simply won't show the disks attached to it.
However, on some systems it will bluescreen 7B, even with the other ntdetect.com. Add the needed driver for SATA, even though booting from USB stick/disk- no more 7B.

Sorry for the late reply, board didn't send me email for the reply.

Re: [solved] BSOD 0x7B using UBCD4Win on VIA P4M266A motherboard

2008-06-03T05:28:18Z

so you are useing an alternate NTDETECT.COM (I assume the one from the 2k3 servicepack)

you do this to support USB boot

and you find that it is interfereing with the mass storage driver support?

Is that correct?

Re: [solved] BSOD 0x7B using UBCD4Win on VIA P4M266A motherboard

2008-06-02T22:30:19Z

Ohh bugger

It bluescreens because of the USB disk connected, no matter if you boot PE from USB or the CD.
Putting the modified NTDETECT.COM on the USB disk and boot from it- no BSOD. May try to put it on the CD too, curious what would happen.

This is something new to me, 0x7B is not inaccessible _BOOT_ device only. Other storage controllers are also playing role.
Similar issues had people, when booting XP Setup from USB, even with the modified NTDETECT.COM, but missing or something wrong with the drivers for their SATA/SCSI controler.

edit: yep, with the modified NTDETECT.COM it started fine from CD too, with USB disk connected.

[solved] BSOD 0x7B using UBCD4Win on VIA P4M266A motherboard

2008-06-02T21:26:55Z

original topic title was
BSOD 0x7B using UBCD4Win and 8.05 mass storage DP on VIA P4M266A m/b
------------------------------------------------------------------------------------------

Getting 0x0000007B on Asus P4VP-MX motherboard with VT8235 south bridge.
DP base is the latest as well as the mass storage pack- 8.05.

Here is some Hardware IDs, pulled them from the installed a while ago XP, which had mass storage pack version 7.12 integrated. It used videX32.sys.
Added at the bottom a few IDs as reported by Device manager.

=========== 
PCI Devices 
=========== 
PCI\VEN_1106&DEV_0571&SUBSYS_80A11043&REV_06\2&EBB567F&0&89 : VIA Bus Master IDE Controller - 0571
PCI\VEN_1106&DEV_3038&SUBSYS_80A11043&REV_80\2&EBB567F&0&80 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_80A11043&REV_80\2&EBB567F&0&81 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_80A11043&REV_80\2&EBB567F&0&82 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3059&SUBSYS_810F1043&REV_50\2&EBB567F&0&8D : Multimedia Audio Controller
PCI\VEN_1106&DEV_3065&SUBSYS_80FF1043&REV_74\2&EBB567F&0&90 : VIA Rhine II Fast Ethernet Adapter #2
PCI\VEN_1106&DEV_3104&SUBSYS_80A11043&REV_82\2&EBB567F&0&83 : VIA USB Enhanced Host Controller
PCI\VEN_1106&DEV_3148&SUBSYS_00000000&REV_00\2&EBB567F&0&00 : VIA Standard Host Bridge
PCI\VEN_1106&DEV_3177&SUBSYS_00000000&REV_00\2&EBB567F&0&88 : VIA Standard PCI to ISA Bridge
PCI\VEN_1106&DEV_B091&SUBSYS_00000000&REV_00\2&EBB567F&0&08 : VIA CPU to AGP Controller
PCI\VEN_5333&DEV_8D04&SUBSYS_807B1043&REV_00\3&8A00C89&0&0008: Video Controller (VGA Compatible)
PCI_HAL\PNP0A03\0                                           : PCI bus
12 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\3&1BA3757E&0                                   : USB Root Hub
USB\ROOT_HUB\3&2E5D2623&0                                   : USB Root Hub
USB\ROOT_HUB\3&8E9C4D9&0                                    : USB Root Hub
USB\ROOT_HUB20\3&3456F08&0                                  : USB Root Hub
USB\VID_046D&PID_C016\4&263E72A6&0&2                        : USB Human Interface Device
USB\VID_05E3&PID_0702\4&E55CC72&0&3                         : USB Mass Storage Device
USBSTOR\DISK&VEN_SAMSUNG&PROD_SP0411N&REV_0811\5&A904FC7&0  : SAMSUNG SP0411N USB Device
7 matching device(s) found.
 
============= 
Input Devices 
============= 
HID\VID_046D&PID_C016\5&24C1E5AE&0&0000                     : HID-compliant mouse
1 matching device(s) found.
 
============ 
ACPI Devices 
============ 
ROOT\ACPI_HAL\0000                                          : Standard PC
1 matching device(s) found.


==============================================
Hardware IDs:
PCI\VEN_1106&DEV_0571&SUBSYS_80A11043&REV_06
PCI\VEN_1106&DEV_0571&SUBSYS_80A11043
PCI\VEN_1106&DEV_0571&CC_01018A
PCI\VEN_1106&DEV_0571&CC_0101
=============================================
Compatible IDs:
PCI\VEN_1106&DEV_0571&REV_06
PCI\VEN_1106&DEV_0571
PCI\VEN_1106&CC_01018A
PCI\VEN_1106&CC_0101
PCI\VEN_1106
PCI\CC_01018A
PCI\CC_0101
==============================================
Matching ID:
pci\ven_1106&dev_0571

I see PCI\VEN_1106&DEV_0571 matches VIAIDE in txtsetup.sif, but why the BSOD?
I tried to comment out all relevant entries in txtsetup.sif about VIAIDE, hoping that it will use PCIIDE instead, but BSOD 7B again.
Tried from CD and USB boot- same result. As far as I remember I had no issues with BartPE disks months ago on thise machines, when mass storage pack was 7.something.

Or is it another driver which causing the BSOD?