|
|
i recently transplanted my rig into a new Silverstone TJ09
case.... (heh its awesome), all went well except now every 4 out of 5
boots results in a weird boot problem, when it gets to the black X64
loading screen the hard drive will spin down and spin up, but basically
its stuck there and never get to windows.
i found out that i actually had a system drive with bad sectors, as well
as a flakey ram dim, so replaced both. did fresh format and install of
X64. exact same problem. hard drive full-surface scan is fine... tried
another format and install, same problem.... its sometimes fine for a
few boots - then after a while it happens. usually a few boots after i
install nForce4 X64 system drivers and graphics drivers. (but they have
worked with this hardware before fine).
i have DFI Lanparty SLI-DR Expert, AMD X24200+, 2x1GB Kingston DDR, XFX
7950GT w/heatpipe, 150GB raptor OS disk, 150GB sata 2nd disk, all temps
cool....
i've been trying to fix this for almost a week with the help of another
ng and have drawn a blank. the only thing that hass actually changed
since the problem is the case... that sounds completely absurd that a
case could cause that.... but maybe the mobo was damaged or something...?
|
|
This is not much to go by, isn't there anything in your 'Event Viewer'?
You could try and download the IDE/SATA driver ( or the complete set of
system drivers? ) from the manufacturer's site, it may have been 'shaky' all
along but for some reason something triggers the error now, and not before.
You could also try and clean the Install Disk and the drive as well.
Tony. . .
"cgimofo" <gimp[ at ]fake.com> wrote in message
news:f43g1f$ls6$1[ at ]lust.ihug.co.nz...
[Quoted Text] > i recently transplanted my rig into a new Silverstone TJ09
> case.... (heh its awesome), all went well except now every 4 out of 5
> boots results in a weird boot problem, when it gets to the black X64
> loading screen the hard drive will spin down and spin up, but basically
> its stuck there and never get to windows.
>
> i found out that i actually had a system drive with bad sectors, as well
> as a flakey ram dim, so replaced both. did fresh format and install of
> X64. exact same problem. hard drive full-surface scan is fine... tried
> another format and install, same problem.... its sometimes fine for a
> few boots - then after a while it happens. usually a few boots after i
> install nForce4 X64 system drivers and graphics drivers. (but they have
> worked with this hardware before fine).
>
> i have DFI Lanparty SLI-DR Expert, AMD X24200+, 2x1GB Kingston DDR, XFX
> 7950GT w/heatpipe, 150GB raptor OS disk, 150GB sata 2nd disk, all temps
> cool....
>
> i've been trying to fix this for almost a week with the help of another
> ng and have drawn a blank. the only thing that hass actually changed
> since the problem is the case... that sounds completely absurd that a
> case could cause that.... but maybe the mobo was damaged or something...?
|
|
What quality & size power supply is in your case? And how
old is it?
I recently replaced my power supply because I wanted a
quieter fan and was since then a lot of little problems have
disappeared. Occasionally the system BIOS would suddenly be
reset, occasional random program failures, etc.
cgimofo wrote:
[Quoted Text] > i recently transplanted my rig into a new Silverstone TJ09
> case.... (heh its awesome), all went well except now every 4 out of 5
> boots results in a weird boot problem, when it gets to the black X64
> loading screen the hard drive will spin down and spin up, but basically
> its stuck there and never get to windows.
>
> i found out that i actually had a system drive with bad sectors, as well
> as a flakey ram dim, so replaced both. did fresh format and install of
> X64. exact same problem. hard drive full-surface scan is fine... tried
> another format and install, same problem.... its sometimes fine for a
> few boots - then after a while it happens. usually a few boots after i
> install nForce4 X64 system drivers and graphics drivers. (but they have
> worked with this hardware before fine).
>
> i have DFI Lanparty SLI-DR Expert, AMD X24200+, 2x1GB Kingston DDR, XFX
> 7950GT w/heatpipe, 150GB raptor OS disk, 150GB sata 2nd disk, all temps
> cool....
>
> i've been trying to fix this for almost a week with the help of another
> ng and have drawn a blank. the only thing that hass actually changed
> since the problem is the case... that sounds completely absurd that a
> case could cause that.... but maybe the mobo was damaged or something...?
|
|
Theo wrote:
[Quoted Text] > What quality & size power supply is in your case? And how old is it?
>
> I recently replaced my power supply because I wanted a quieter fan and
> was since then a lot of little problems have disappeared. Occasionally
> the system BIOS would suddenly be reset, occasional random program
> failures, etc.
i thought about PSU, but how is it possible that it happens in the exact
same software spot on multiple installs...? don't see how it can be psu
unless that load point causes a sudden massive power spike or something
lol. its a Seasonic S12 500W, 80% efficiency... about a year old.
|
|
Theo is absolutely right. The quality of the rest of the system in mind, I
dared not mention this. One other important thing that comes to mind now, is
the number of spacers and screws you used to secure the motherboard. The
most common causes to random errors are Temperature, Power and Vibration!!!
With a possibly weighty cooling solution, this becomes very important.
Tony. . .
"Theo" <theo[ at ]discussions.microsoft.com> wrote in message
news:O5RZAS2pHHA.596[ at ]TK2MSFTNGP06.phx.gbl...
[Quoted Text] > What quality & size power supply is in your case? And how
> old is it?
>
> I recently replaced my power supply because I wanted a
> quieter fan and was since then a lot of little problems have
> disappeared. Occasionally the system BIOS would suddenly be
> reset, occasional random program failures, etc.
>
>
> cgimofo wrote:
> > i recently transplanted my rig into a new Silverstone TJ09
> > case.... (heh its awesome), all went well except now every 4 out of 5
> > boots results in a weird boot problem, when it gets to the black X64
> > loading screen the hard drive will spin down and spin up, but basically
> > its stuck there and never get to windows.
> >
> > i found out that i actually had a system drive with bad sectors, as well
> > as a flakey ram dim, so replaced both. did fresh format and install of
> > X64. exact same problem. hard drive full-surface scan is fine... tried
> > another format and install, same problem.... its sometimes fine for a
> > few boots - then after a while it happens. usually a few boots after i
> > install nForce4 X64 system drivers and graphics drivers. (but they have
> > worked with this hardware before fine).
> >
> > i have DFI Lanparty SLI-DR Expert, AMD X24200+, 2x1GB Kingston DDR, XFX
> > 7950GT w/heatpipe, 150GB raptor OS disk, 150GB sata 2nd disk, all temps
> > cool....
> >
> > i've been trying to fix this for almost a week with the help of another
> > ng and have drawn a blank. the only thing that hass actually changed
> > since the problem is the case... that sounds completely absurd that a
> > case could cause that.... but maybe the mobo was damaged or
something...?
|
|
Tony Sperling wrote:
[Quoted Text] > This is not much to go by, isn't there anything in your 'Event Viewer'?
only errors i could find in event viewer - not sure if the time relates
to it so will try and reproduce it, but its hard to get back into
windows after it happens lol:
Dependent Assembly Microsoft.Windows.Common-Controls could not be found
and Last Error was The referenced assembly is not installed on your system.
Resolve Partial Assembly failed for Microsoft.Windows.Common-Controls.
Reference error message: The referenced assembly is not installed on
your system.
..
Generate Activation Context failed for C:\WINDOWS\system32\fdco1ins.dll.
Reference error message: The referenced assembly is not installed on
your system.
..
The application-specific permission settings do not grant Local
Activation permission for the COM Server application with CLSID
{BA126AD1-2166-11D1-B1D0-00805FC1270E}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This
security permission can be modified using the Component Services
administrative tool.
> You could try and download the IDE/SATA driver ( or the complete set of
> system drivers? ) from the manufacturer's site,
was already done and installed. was working ok with them for a bit..
|
|
found another entry in the log:
The Plug and Play operation cannot be completed because a device driver
is preventing the device from stopping. The name of the device driver is
listed as the vetoing service name below.
Vetoed device:
PCI\VEN_10DE&DEV_0295&SUBSYS_22191682&REV_A1\4&243D7BD0&0&0070
Vetoing device:
PCI\VEN_10DE&DEV_0295&SUBSYS_22191682&REV_A1\4&243d7bd0&0&0070
Vetoing service name: Driver\vga
Veto type 6: PNP_VetoDevice
When Windows attempts to install, upgrade, remove, or reconfigure a
device, it queries the driver responsible for that device to confirm
that the operation can be performed. If any of these drivers denies
permission (query-removal veto), then the computer must be restarted in
order to complete the operation.
User Action
Restart your computer.
?
|
|
I'd call that a clear pointer. Now, who can decifer these incantations?
Tony. . .
"cgimofo" <gimp[ at ]fake.com> wrote in message
news:f43i6s$pj7$2[ at ]lust.ihug.co.nz...
[Quoted Text] > found another entry in the log:
>
> The Plug and Play operation cannot be completed because a device driver
> is preventing the device from stopping. The name of the device driver is
> listed as the vetoing service name below.
>
> Vetoed device:
> PCI\VEN_10DE&DEV_0295&SUBSYS_22191682&REV_A1\4&243D7BD0&0&0070
> Vetoing device:
> PCI\VEN_10DE&DEV_0295&SUBSYS_22191682&REV_A1\4&243d7bd0&0&0070
> Vetoing service name: Driver\vga
> Veto type 6: PNP_VetoDevice
>
> When Windows attempts to install, upgrade, remove, or reconfigure a
> device, it queries the driver responsible for that device to confirm
> that the operation can be performed. If any of these drivers denies
> permission (query-removal veto), then the computer must be restarted in
> order to complete the operation.
>
> User Action
> Restart your computer.
>
>
>
> ?
|
|
That PSU should be quite all right, but if you go SLI at some point, 500W
might be on the lower threshold.
Tony. . .
"cgimofo" <gimp[ at ]fake.com> wrote in message
news:f43hr1$oii$1[ at ]lust.ihug.co.nz...
[Quoted Text] > Theo wrote:
> > What quality & size power supply is in your case? And how old is it?
> >
> > I recently replaced my power supply because I wanted a quieter fan and
> > was since then a lot of little problems have disappeared. Occasionally
> > the system BIOS would suddenly be reset, occasional random program
> > failures, etc.
>
>
> i thought about PSU, but how is it possible that it happens in the exact
> same software spot on multiple installs...? don't see how it can be psu
> unless that load point causes a sudden massive power spike or something
> lol. its a Seasonic S12 500W, 80% efficiency... about a year old.
|
|
VEN_10DE&DEV_0295 is a NVIDIA GeForce 7950 GT
You may have a defective video card or a corrupt driver or
your motherboard platform drivers may have a problem.
Tony Sperling wrote:
[Quoted Text] > I'd call that a clear pointer. Now, who can decifer these incantations?
>
>
> Tony. . .
>
>
> "cgimofo" <gimp[ at ]fake.com> wrote in message
> news:f43i6s$pj7$2[ at ]lust.ihug.co.nz...
>> found another entry in the log:
>>
>> The Plug and Play operation cannot be completed because a device driver
>> is preventing the device from stopping. The name of the device driver is
>> listed as the vetoing service name below.
>>
>> Vetoed device:
>> PCI\VEN_10DE&DEV_0295&SUBSYS_22191682&REV_A1\4&243D7BD0&0&0070
>> Vetoing device:
>> PCI\VEN_10DE&DEV_0295&SUBSYS_22191682&REV_A1\4&243d7bd0&0&0070
>> Vetoing service name: Driver\vga
>> Veto type 6: PNP_VetoDevice
>>
>> When Windows attempts to install, upgrade, remove, or reconfigure a
>> device, it queries the driver responsible for that device to confirm
>> that the operation can be performed. If any of these drivers denies
>> permission (query-removal veto), then the computer must be restarted in
>> order to complete the operation.
>>
>> User Action
>> Restart your computer.
>>
>>
>>
>> ?
>
>
|
|
|