You are not logged in. Please login or register.
DriverPacks.net Forum » DriverPack Mass Storage » [fixed] I have a Blue Screen of Death by this 801 pack
I have a BOD (Blue Screen of Death) by this pakettes
DP_MassStorage_wnt5_x86-32_801
Chipset= North Bridge: VIA VT8763 Apollo PT800
South Bridge: VIA VT8237
some older chipset of via to:
North Bridge: AMD-751
South Bridge: VIA VT82C686A
but this one have a BOD also by pack 7.12.1 and 7.12 and so more
is this maybe to ficks,of are thy to old...
Thanks any way.Doei
Hey, you may want to give the latest nightly a try, then.
(link to old file pulled)
Please report back!
Thanks Helmi,i give it a try.
but give some time,so i can try both pc's.
see you soon,and thanks again.
Yo Helmi.
i testit both pc's and this is the report back:
On this pc:Chipset= North Bridge: VIA VT8763 Apollo PT800
South Bridge: VIA VT8237
it don't works,again a BOD by T34..
=======================================
On this one:North Bridge: AMD-751
South Bridge: VIA VT82C686A
It works fine.it was amazing,i jump a meter into the air,super
Thanks a lot..
can we get the HWID's of the one that failed please?
can we get the HWID's
and thats mean's???explain if you will..
hardware id??
Last edited by Babyboy (2008-02-07 09:47:49)
Yeah, HardWare ID.
See the link in our sigs for a tool to obtain them.
It will also be created in the log files after a successful installation but seeing as your fails, you'll have to somehow install Windows w/o the DriverPacks on it in order to run it...
I will look at VIA drivers tomorrow.
I cannot remember that I needed F6 floppy on machines which used really old arena 4in1, and the old apollo and such did not need F6 either? (talking pentium three here)
And nowadays we have at least one report telling us the new drivers make it impossible to install on OLDer (and real antique) hardware which runs pentium three, and this poster has another machine that would use an older appollo driver? (and it won't go)
now, if 7092 did NOT make it NO-GO on older VIA, then I have to look at what could be that different in the updated driver. (And I recently got a still newer driver anyhow.. maybe it fixes issues?).
I cannot say I can fix it, but I will try..
Mind you, it could also be a chipset issue..
Jaak wrote:Mind you, it could also be a chipset issue..
I don.t vink so, by this pack DPM711 it works fine
and the chipset pack is the same.
========================================
[ North Bridge: VIA VT8763 Apollo PT800 ]
North Bridge Properties:
North Bridge VIA VT8763 Apollo PT800
Supported FSB Speeds FSB400, FSB533, FSB800
Supported Memory Types DDR-200 SDRAM, DDR-266 SDRAM, DDR-333 SDRAM, DDR-400 SDRAM
In-Order Queue Depth 12
[ South Bridge: VIA VT8237 ]
South Bridge Properties:
South Bridge VIA VT8237
Revision 00
Package Type 539 Pin BGA
Package Size 2.7 cm x 2.7 cm
Process Technology 0.22 um
Core Voltage 2.5 V
AC'97 Audio Controller:
Audio Controller Type VIA 8233/8235/8237/8251
Codec Name Analog Devices AD1888/AD1980
Codec ID 41445370h
S/PDIF Output Supported
========================================================================================
Motherboard
CPU Type Intel Celeron D 330, 2666 MHz (20 x 133)
Motherboard Name Asus P4V8X-X (5 PCI, 1 AGP, 3 DDR DIMM, Audio, LAN)
Motherboard Chipset VIA VT8763 Apollo PT800
System Memory 512 MB (DDR SDRAM)
BIOS Type Asus AMI (08/12/04)
Communication Port Communications Port (COM1)
Storage
IDE Controller VIA Bus Master IDE Controller
Storage Controller SCSI/RAID Host Controller
Storage Controller VIA RAID Controller - 3149
Floppy Drive Floppy disk drive
Disk Drive WDC WD3200JB-00KFA0 (298 GB, IDE)
Optical Drive BENQ DVD DD DW1650 (DVD+R9:8x, DVD-R9:4x, DVD+RW:16x/8x, DVD-RW:16x/6x, DVD-ROM:16x, CD:48x/32x/48x DVD+RW/DVD-RW)
Optical Drive PB1036M LHR592T SCSI CdRom Device
SMART Hard Disks Status OK
is this what you must have.....
I tried MassStorage pack 8025 and the HDD in my notebook (Clevo M660SE - http://www.clevo.com.tw/en/products/pro … ductid=23) will not be found... Chipset is VIA VN896 + VT8237A
Hardware IDs are here:
===========
PCI devices
===========
PCI\VEN_1106&DEV_0364&SUBSYS_00000000&REV_00\3&61AAA01&0&00 : VIA Standard Host Bridge
PCI\VEN_1106&DEV_0571&SUBSYS_06641558&REV_07\3&61AAA01&0&79 : VIA Bus Master IDE Controller - 0571
PCI\VEN_1106&DEV_0591&SUBSYS_06641558&REV_80\3&61AAA01&0&78 : VIA Serial ATA Controller - 0591
PCI\VEN_1106&DEV_1364&SUBSYS_00000000&REV_00\3&61AAA01&0&01 : VIA Standard Host Bridge
PCI\VEN_1106&DEV_2364&SUBSYS_00000000&REV_00\3&61AAA01&0&02 : VIA Standard Host Bridge
PCI\VEN_1106&DEV_287E&SUBSYS_00000000&REV_00\3&61AAA01&0&8F : VIA Ultra VLINK Controller
PCI\VEN_1106&DEV_3038&SUBSYS_06641558&REV_A0\3&61AAA01&0&80 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_06641558&REV_A0\3&61AAA01&0&81 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_06641558&REV_A0\3&61AAA01&0&82 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_06641558&REV_A0\3&61AAA01&0&83 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3065&SUBSYS_06641558&REV_7C\3&61AAA01&0&90 : VIA Rhine II Fast Ethernet Adapter
PCI\VEN_1106&DEV_3104&SUBSYS_06641558&REV_86\3&61AAA01&0&84 : VIA USB Enhanced Host Controller
PCI\VEN_1106&DEV_3288&SUBSYS_32881106&REV_10\4&A3ED729&0&0898: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_1106&DEV_3337&SUBSYS_00000000&REV_00\3&61AAA01&0&88 : VIA Standard PCI to ISA Bridge
PCI\VEN_1106&DEV_3364&SUBSYS_00000000&REV_00\3&61AAA01&0&03 : VIA Standard Host Bridge
PCI\VEN_1106&DEV_3371&SUBSYS_06641558&REV_01\4&1FEB96E4&0&0008: VIA Chrome9 HC IGP Family
PCI\VEN_1106&DEV_337A&SUBSYS_00000000&REV_00\3&61AAA01&0&99 : VIA Standard PCI to PCI Bridge
PCI\VEN_1106&DEV_337B&SUBSYS_00000000&REV_00\3&61AAA01&0&98 : VIA Standard PCI to PCIE Bridge
PCI\VEN_1106&DEV_4364&SUBSYS_00000000&REV_00\3&61AAA01&0&04 : VIA Standard Host Bridge
PCI\VEN_1106&DEV_5364&SUBSYS_00000000&REV_00\3&61AAA01&0&05 : VIA I/O APIC Interrupt Controller
PCI\VEN_1106&DEV_6364&SUBSYS_00000000&REV_00\3&61AAA01&0&06 : VIA Security Device
PCI\VEN_1106&DEV_7364&SUBSYS_00000000&REV_00\3&61AAA01&0&07 : VIA Standard Host Bridge
PCI\VEN_1106&DEV_A364&SUBSYS_00000000&REV_80\3&61AAA01&0&10 : VIA PCI to PCI Bridge Controller
PCI\VEN_1106&DEV_B198&SUBSYS_00000000&REV_00\3&61AAA01&0&08 : VIA CPU to AGP2.0/AGP3.0 Controller
PCI\VEN_1106&DEV_C364&SUBSYS_00000000&REV_80\3&61AAA01&0&18 : VIA PCI to PCI Bridge Controller
PCI\VEN_1524&DEV_0730&SUBSYS_06641558&REV_00\4&1A598D38&0&2099: ENE PCI Memory Stick Card Reader Controller
PCI\VEN_1524&DEV_0750&SUBSYS_06641558&REV_00\4&1A598D38&0&2199: SDA Standard Compliant SD Host Controller
PCI\VEN_1524&DEV_0751&SUBSYS_06641558&REV_00\4&1A598D38&0&2399: ENE PCI Secure Digital / MMC Card Reader Controller
28 matching device(s) found.
===========
USB devices
===========
USB\ROOT_HUB\4&11C3EC64&0 : USB Root Hub
USB\ROOT_HUB\4&247D9D09&0 : USB Root Hub
USB\ROOT_HUB\4&37374DAE&0 : USB Root Hub
USB\ROOT_HUB\4&3AA505C6&0 : USB Root Hub
USB\ROOT_HUB20\4&29B31F01&0 : USB Root Hub
USB\VID_0BDA&PID_8187\0015AF4C01C6 : Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter
USB\VID_152D&PID_2338\308241768019 : USB Mass Storage Device
USBSTOR\DISK&VEN_SAMSUNG&PROD_HD160JJ&REV_0-41\308241768019&0: SAMSUNG HD160JJ USB Device
8 matching device(s) found.
I cannot remember that I needed F6 floppy on machines which used really old arena 4in1, and the old apollo and such did not need F6 either? (talking pentium three here)
No, they don't.
Only sporting your common standard IDE interface that does not make Windows need special drivers to be fed to reckognize.
Still have one of these boxes around here, btw 
I have this tool:save_hwids
first this in a second.
the system cannot find the path specified
but nothing shows up.my notepad give's no info..
it stays empty.....
here is basically same pack, with an INI edit
DP_MassStorage_wnt5_x86-32_8026nightly.7z
http://dev.driverpacks.thesneaky.com/dr … nightly.7z
[V4] section in version 7092 listed a single HWID.
That's what I do here now. In 8026nightly I let TXTmode use just this one HWID 7092 had in the INI.
The [V3] section is active again.
@Jaak please when you edit the .ini make sure you don't leave blank lines. 
There is a blank line before V2 section.
LOL.
cdob had suggested to remove V4 alltogether. That were many blanks.
The Point is this this. V\4 in Older pack 7091 used single HWID for TXTmode even while the INF supported more than that.
When the new driver was introduced, the full list got back in.
I could just as well only remove PCI\VEN_1106&DEV_0591
MassStorage 8026 works for me now
Skeptik?
are you volunteer for another edit?
I would like you to try this 8026 with more HWIDs in V4
(quote> I could just as well only remove PCI\VEN_1106&DEV_0591 < end quote)
I will upload a 8026via2
Thats good news Skeptik, good job Jaak!
Last edited by JakeLD (2008-02-09 04:07:29)
pulled
If skeptik and babybow can test this new testpack, we would find out if it was that 0591 messing it up.
8028nightly
http://dev.driverpacks.thesneaky.com/dr … nightly.7z
That pack includes Sil Image 3135 Helmi REQuested in new folder [S3] and the REQuested windows update version in [S7B] for 3114Raid5.
The Via [V4] section no longer has PCI\VEN_1106&DEV_0591
(I put the other HWIDs back in)
I also changed the modetags where they was wrong. (proof of that in other topic)
Babyboy can first test the 8028nightly version, and only if that fails he should try 8026nightly, because we MUST at least try with as many HWIDs as we can.
In other words, I will not move 8026nightly out of reach yet.
This is all done:
DP_MassStorage_wnt5_x86-32_8025 (Wedsday)
I tray the pakkets of today:
DP_MassStorage_wnt5_x86-32_8026nightly
DP_MassStorage_wnt5_x86-32_8027_ViaV4_S7BWU
But also:
DP_MassStorage_wnt5_x86-32_711
All in combinatie:
DP_Chipset_wnt5_x86-32_7101
DP_CPU_wnt5_x86-32_7041
DP_Graphics_A_wnt5_x86-32_710
DP_Graphics_B_wnt5_x86-32_7121
DP_Graphics_C_wnt5_x86-32_712
DP_LAN_wnt5_x86-32_7121
DP_Sound_A_wnt5_x86-32_712
DP_Sound_B_wnt5_x86-32_712
DP_WLAN_wnt5_x86-32_712
and 3rd party DriverPacks
DP_Input_wnt5_x86-32_070923
DP_Monitor_wnt5_x86-32_070827
DP_TV_wnt5_x86-32_709
DP_USB_wnt5_x86-32_60831
And al this testing end in a BOD on T34
when i unzip everything no error's shows up.
pakkets looks oke..
=============================================
when a did this combie try,its all working again.
DP_Chipset_wnt5_x86-32_7101
DP_CPU_wnt5_x86-32_7041
DP_Graphics_A_wnt5_x86-32_710
DP_Graphics_B_wnt5_x86-32_710
DP_Graphics_C_wnt5_x86-32_7091
DP_LAN_wnt5_x86-32_7101
DP_MassStorage_wnt5_x86-32_711
DP_Sound_A_wnt5_x86-32_711
DP_Sound_B_wnt5_x86-32_7101
DP_WLAN_wnt5_x86-32_7092
and 3rd party DriverPacks
DP_Input_wnt5_x86-32_070923
DP_Monitor_wnt5_x86-32_070827
DP_TV_wnt5_x86-32_709
DP_USB_wnt5_x86-32_60831
It,s up to you guys,i losse the track(spoor kwijt)
===================================================
This one fiks't the pc chipset:
North Bridge: AMD-751
South Bridge: VIA VT82C686A
DP_MassStorage_wnt5_x86-32_8025
That's working fine now..
Will you that i tested this pakkets to??
DP_MassStorage_wnt5_x86-32_8028nightly
Mijn pc explode almost..
@ babyboy
Did you make a clean copy from the CD before you used a new testpack?
In the tutorial we do not say so, but a fresh clean copy of the CD works best.
We also advise to delete the QSC folder when you try a new testpack.
Je bent vrij nieuw, en je raakt het spoor kwijt.
If you can, put a clean copy of the CD in a folder, and make a second copy in a working folder.
Try 8028 with txtmode and mass storage selected, and use a CDRW to test the install.
If that works, tell us about it, and call it a day.
If it doesn't work, delete the working copy, and make a new copy of your stored CD-copy
move 8028 out of DriverPacks folder, and put 8026 in.
delete the QSC folder, and slipstream the working folder.
re-use the CDRW for the new burn.
test that.
If this also does not work.. then I don't know what will, but I will at least know that it was not some mixup between different packs that messes you up.
Did you make a clean copy from the CD before you used a new testpack?
Yes i do..
============================================
when i make a new driverpack for a windows cd i remove all old historie.
this 2 folders i don't remove:driverpack and 3 rd driverpack
=================
Last edited by Babyboy (2008-02-09 17:55:44)
als de uwe bijna explodeert, dan had je het geschreeuw in mijn hard disk daarnet moeten horen toen ik twee ISOs setup liet draaien in elk een van de VPC2007 vensters.
Ik ben bezig het nieuwe pack in verschillende windowsen te testen, want we leerden iets over enkele eigenaardigheden.
JA, als je kan, laat het ff koelen, en doe morgen een nieuwe.
-----
My hard disk screeched while I tested ISOs in two VPC boxes.
We learned about some peculiarities, and I am testing all windows versions before I upload what I tested.
(WE is Jeff and I. We was looking for peculiarities, and found some. We hope to fix the case sensitivity issue.)
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.024 seconds, 11 queries executed ]
