- Joined
- Dec 18, 2005
- Messages
- 8,253 (1.16/day)
| System Name | money pit.. |
|---|---|
| Processor | Intel 9900K 4.8 at 1.152 core voltage minus 0.120 offset |
| Motherboard | Asus rog Strix Z370-F Gaming |
| Cooling | Dark Rock TF air cooler.. Stock vga air coolers with case side fans to help cooling.. |
| Memory | 32 gb corsair vengeance 3200 |
| Video Card(s) | Palit Gaming Pro OC 2080TI |
| Storage | 150 nvme boot drive partition.. 1T Sandisk sata.. 1T Transend sata.. 1T 970 evo nvme m 2.. |
| Display(s) | 27" Asus PG279Q ROG Swift 165Hrz Nvidia G-Sync, IPS.. 2560x1440.. |
| Case | Gigabyte mid-tower.. cheap and nothing special.. |
| Audio Device(s) | onboard sounds with stereo amp.. |
| Power Supply | EVGA 850 watt.. |
| Mouse | Logitech G700s |
| Keyboard | Logitech K270 |
| Software | Win 10 pro.. |
| Benchmark Scores | Firestike 29500.. timepsy 14000.. |
had this system for about three months now.. at first it seemed to work perfectly.. over the last few weeks its been having problems with the odd program.. game crashes and odd happenings..
about five weeks ago i installed a new creative audigy 4 sound card.. i never made the soundcard connection at first but it plays its part..
my most noticable problem has been large rar and par2 sets failing to either verify or unrar.. 3 gig type sets.. smaller ones have been okay..
the system runs all 3dmarks and passes every strees test u thow at it.. memory tests have been run all night and nothing shows up as being wrong.. ???
all googling says memory errors cause fail to verify errors in quickpar but i cant find any damn thing wrong with mine..
any ways to cut a long story short it turns out i am getting data corruption during disk writes.. not a lot and i had to devise my own test thing to even find it..
i took a 3 gig rar and par set.. found a little command line based rar/par fixer bunged the lot in a folder and started copying it about from place to place..
start off with good verified set of rras and pars copy em and run the little verify tool and errors show up in the copied rars..
at first every copy made shows more errors.. new xp installs.. in fact hours of altering everything thing on the bloody planet cannot get rid of these copy errors..
except.. removing the already turned off but still plugged in creative sound card.. !!!
problem fixed thought i.. hmmm.. but no it wasnt that easy.. it turned out without the card plugged in any copy made to the same ide channel produced an error free perfect copy.. but a copy made to a different ide or serial channel still produced errors.. not so many but still errors..
none of this would show up in normal usage and before the introduction of the creative card largely went unoticed cos most of my rar/par work was done on the same drive and would have been error free.. but anything copied over to another ide channel would have been producing copy errors..???.. my pagefile on another drive would have been something suffering from the odd data bit in the wrong place for example.. my registry would have been okay.. the creative changed all this and pretty quickly things started to go wrong.. he he he
what seems to be the "FIX".. i can now copy this big bunch of rars/pars wherever i like without any errors showing up.. ???
altering a mysteriouse bios setting called Vlink mode selection.. this governs the bus (Vlink) speed/bandwidth between the north and south bridge mobo chips.. changing from the default mode 4 to mode 3 has cured the problem..
trog
ps.. hmmm.. just sat there minding its own business.. up pops a blue machine is being shut down dumping physical memory screen and the machine resets itself.. he he..
about five weeks ago i installed a new creative audigy 4 sound card.. i never made the soundcard connection at first but it plays its part..
my most noticable problem has been large rar and par2 sets failing to either verify or unrar.. 3 gig type sets.. smaller ones have been okay..
the system runs all 3dmarks and passes every strees test u thow at it.. memory tests have been run all night and nothing shows up as being wrong.. ???
all googling says memory errors cause fail to verify errors in quickpar but i cant find any damn thing wrong with mine..
any ways to cut a long story short it turns out i am getting data corruption during disk writes.. not a lot and i had to devise my own test thing to even find it..
i took a 3 gig rar and par set.. found a little command line based rar/par fixer bunged the lot in a folder and started copying it about from place to place..
start off with good verified set of rras and pars copy em and run the little verify tool and errors show up in the copied rars..
at first every copy made shows more errors.. new xp installs.. in fact hours of altering everything thing on the bloody planet cannot get rid of these copy errors..
except.. removing the already turned off but still plugged in creative sound card.. !!!
problem fixed thought i.. hmmm.. but no it wasnt that easy.. it turned out without the card plugged in any copy made to the same ide channel produced an error free perfect copy.. but a copy made to a different ide or serial channel still produced errors.. not so many but still errors..
none of this would show up in normal usage and before the introduction of the creative card largely went unoticed cos most of my rar/par work was done on the same drive and would have been error free.. but anything copied over to another ide channel would have been producing copy errors..???.. my pagefile on another drive would have been something suffering from the odd data bit in the wrong place for example.. my registry would have been okay.. the creative changed all this and pretty quickly things started to go wrong.. he he he
what seems to be the "FIX".. i can now copy this big bunch of rars/pars wherever i like without any errors showing up.. ???
altering a mysteriouse bios setting called Vlink mode selection.. this governs the bus (Vlink) speed/bandwidth between the north and south bridge mobo chips.. changing from the default mode 4 to mode 3 has cured the problem..
trog
ps.. hmmm.. just sat there minding its own business.. up pops a blue machine is being shut down dumping physical memory screen and the machine resets itself.. he he..
Last edited: