Various BSOD with fresh install of Windows 7 Pro 64bit

Sorry about long delay, been busy with family. Here is an image of the program at the particular place you asked for. Everything looks ok to me I think?

Link to JPG file: https://onedrive.live.com/redir?resi...nt=photo%2cjpg

I have a Corsair CX600 with a Sapphire HD 3850 AGP card. The power supply be causing an issue with the GPU?

Well yes it could because like all the other components if the volts are less than or more than 5% of the required value ie 12, 5, 3.3 then the device is not going to work properly if at all.
You may have seen that quoted in the link within the ditty I sent. Power Supply 101: A Reference Of Specifications - Power Supplies see point 2
The 5v and 12v rails on yours are teetering on the edge of the lower limit (see pic) and who is to say that a slight fluctuation in the mains voltage doesn't make this drop out and affect the machine? As you may also know that even tiny changes in volts to say the CPU can have drastic and quite large changes to the operating frequency (overclocking) and hence it follows the heat produced and so on and so on

The other thing I might add is the PSU large enough for what you are using it for? this is a handy calculator and keep in mind it is best to be at least 20% over the total wattage to be on the safe side of power supply.
eXtreme Power Supply Calculator though this may not still be conclusive.

Well the load limit really is ok it is the voltages that count in that as itstates in that link the 5% discrepancy is really important because of the finetolerance that any component will work with.



So I suppose we can just battle on and hope it is something else fort ehtime being they are still within range but only just.

Code:

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

Code:

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff80002867000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  52954dbb

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lxreferenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
usbccgp+85b2
fffff880`026085b2 4c8b6940       mov     r13,qword ptr [rcx+40h]

EXCEPTION_RECORD:  fffff88005f6a418 -- (.exr 0xfffff88005f6a418)
ExceptionAddress: fffff880026085b2 (usbccgp+0x00000000000085b2)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000040
Attempt to read from address 0000000000000040

CONTEXT:  fffff88005f69c70 -- (.cxr 0xfffff88005f69c70;r)
rax=fffffa80056b7950 rbx=fffffa80056f0b58 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000001 rdi=0000000000000008
rip=fffff880026085b2 rsp=fffff88005f6a650 rbp=0000000000000000
 r8=fffffa80056f6b00  r9=0000000000000000 r10=fffff88002608854
r11=0000000000000000 r12=0000000000000000 r13=fffffa80056f6b58
r14=0000000000000000 r15=00000000c0000120
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053 gs=002b            efl=00010297
usbccgp+0x85b2:
fffff880`026085b2 4c8b6940       mov     r13,qword ptr [rcx+40h]ds:002b:00000000`00000040=????????????????
Last set context:
rax=fffffa80056b7950 rbx=fffffa80056f0b58 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000001 rdi=0000000000000008
rip=fffff880026085b2 rsp=fffff88005f6a650 rbp=0000000000000000
 r8=fffffa80056f6b00  r9=0000000000000000 r10=fffff88002608854
r11=0000000000000000 r12=0000000000000000 r13=fffffa80056f6b58
r14=0000000000000000 r15=00000000c0000120
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053 gs=002b            efl=00010297
usbccgp+0x85b2:
fffff880`026085b2 4c8b6940       mov     r13,qword ptr [rcx+40h]ds:002b:00000000`00000040=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x7E

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880026085b2

STACK_TEXT:  
fffff880`05f6a650 00000000`00000000 : fffffa80`056f0b58 00000000`00000000fffffa80`03d5dda0 fffffa80`056e9c60 : usbccgp+0x85b2


FOLLOWUP_IP: 
usbccgp+85b2
fffff880`026085b2 4c8b6940       mov     r13,qword ptr [rcx+40h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  usbccgp+85b2

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  usbccgp.sys

STACK_COMMAND:  .cxr 0xfffff88005f69c70 ; kb

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner

It is now going to be a run through the other stuff in the machine mate andthe marked dumps are relating to a USB driver update which looks like it wasdone via Windows so we had better look at the board manufacturer and inparticular the chipset.
Unfortunately I cannot find the driver support for that board on the Gigabyte site so have you got any disks that came with the board - at least it is a start.

Mate does this mean you intend installing XP as well if so please don't. Can you please tell us what media you have for Windows 7?
What I think you need to do is to either get a new drive or clean all the original on another machine before you install the 7.

I shall await your reply because we need to know what that media is and how old is that drive?

My 2 cents for this, if the attached zip file is accurate (I doubt it a lot),

• I saw a few drivers causing a few BSOD's, 1 of them was from ZoneAlarm
• If the hosts file from the attached zip file is still accurate, then it is suggested to remove what it contains, I believe it is for a bypass?

Hmm didn't notice this one before and maybe the machine is just too old mate as this suggests a problem with the board.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880026085b2, fffff88005f6a418, fffff88005f69c70}
*** WARNING: Unable to verify timestamp for Alpham164.sys
*** ERROR: Module load completed but symbols could not be loaded for Alpham164.sys
Probably caused by : Alpham164.sys ( Alpham164+6ba1 )
Followup: MachineOwner

Would you please run the DM Log Collector tool again and upload the zip file for up to date information :)