Tom's Hardware: Topic Help with Gigabyte's New F8 BIOS version for DQ6 Mobo
Tom's Hardware > Forum > Overclocking > Motherboards > Help with Gigabyte's New F8 BIOS version for DQ6 Mobo
Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions.
Sign up now! Its free!
Last message on previous page:
I'll be going over a Gigabyte GA-965P-DQ6 (Rev 1.0), with BIOS F8 installed in about 4 hours.
Clearing the BIOS (remove battery for 60 seconds while unplugged from mains power) is an important step. - Try this instead of shorting the CMOS CLEAR jumper.
I'll be raising the FSB to 333, from 266, and using a CPU voltage of 1.375 - To overclock a Intel Core 2 Duo E6600 from 2.40 GHz to 3.00 GHz - This is the same chip everyone else is mentioning problems with here.
You're all raising the CPU Voltage to 1.375 or higher right ?
Maybe try VDIMM and other voltage tweaks too, but only slight ones (unless your RAM needs 2.x Volts to work that is 
).
The F8 BIOS adds a Voltage 'Detection Probe' to the boot up sequence, which improves DRAM compatibility on the board (high end modules need more volts, as above).
Have you checked all BIOS settings using Ctrl+F1 at the main BIOS menu ?
PCI Express Frequency I plan to lock at between 97 and 101.
The RAM I use is G.Skill DDR2-800 (PC2-6400) that requires 2.1 Volts (+0.3 VDIMM) - and I run 4 x 1 GB sticks of it. (That is 8 banks of RAM to the system, the maximum number of banks the i965P supports as far as I am aware). This is a fairly 'maxed out' memory setup, esp considering it is not standard 1.8 Volt gear.
The only odd thing is that the Intel Chipset ID tool detects the northbridge as a Intel G965 on my GA-965P-DQ6 for some reason, but the south bridge is definitely a ICH8R - as I am setting up RAID-5 (4 x 320 GB Seagate Barracuda 10's - within the next 4 hours).
I'll post back when I have more info.
I'm only running a GeForce 7600 GT (Gigabyte branded one, Silent Pipe II cooling), but the 4 internal HDDs (and sometimes 1 - 2 eSATA HDDs) will be pulling somewhere around 125 - 150 watts at boot up - So I am sure my drain on PSU - during POST - will be more than a typical setup with just 2 HDDs and a GeForce 8800 GTX.
(Comparable enough for this little test anyway).
ED: Only 1 hour of backups to go, or 2-3 episodes of a decent animé series - 
| Quote : I'll be going over a Gigabyte GA-965P-DQ6 (Rev 1.0), with BIOS F8 installed in about 4 hours.
|
Here are my stable settings with any other BIOS version less than the F8 verison.
I'm back @ 3.40Ghz with the ver. F7.
A wise man once said to me:
"User the Force" & remember the DISCLAIMER!!!
DISCLAIMER: If someone reading this wishes to OC & test their system using these parameters below please do so at your own risk. The parameters are for my specific hardware. I'm not sure if it would work equally for a different system.
I took a chance with the help from the guys hanging out here & I'm still here writing about it on my OC'ed system. I'm only posting my findings to make it easy/easier for noobies like me on OCing. Your welcome.
The changes in my BIOS are in BOLD Blue & Red below:
[Gigabyte BIOS (M.I.T.) Menu Options word-for-word with the F7 BIOS update]
Robust Graphics Booster: [AUTO]
CPU Clock Ratio: (9x)
CPU Host Frequency (Mhz): [378]
PCI Express Frequency (Mhz) [100]
C.I.A.2: [Disabled]
System Memory Multiplier: [2.00]
Memory Frequency (Mhz) {this option is shaded out}: [726]
======================================
{Pressing Ctrl + F1 key Combo At Main BIOS Screen Enables DRAM Timings Below}
DRAM Timing Selectable: [AUTO]
CAS Latency Time: [grayed out]
DRAM RAS# To CAS# Delay: [grayed out]
DRAM RAS# Precharge: [grayed out]
Precharge Delay: [grayed out]
ACT to ACT Delay: [Auto]
Rank Write To READ Delay: [Auto]
Write To Precharge Delay: [Auto]
Refresh To ACT Delay: [0]
Read To Precharge Delay: [Auto]
Memory Performance Enhance: [Normal]
======================================
{blinking} ***** System Voltage NOT Optimized!! ***** {blinking}
======================================
System Voltage Control: [Manual]
DDR2 OverVoltage Control: [+0.025V]
PCI-E OverVoltage Control: [Normal]
{option appears after pressing Ctrl + F1 key combo}
(G)MCH OverVoltage Control: [Normal]
FSB OverVoltage Control: [+0.15V]
CPU OverVoltage Control: [1.42500V]
--------------------------------------------------
Like I said. All has been good with these settings until the new F8 came & it was all down hill from there...
I picked up my GA-965P-DQ6 (Rev 1.0) about 10 days ago here in Australia. Came with F8 already installed. Other than the occasional issue where about 1 x every 2 days rebooting XP seems to send the motherboard into an endless loop of booting for 5 seconds then turning off. I Have to unplug the power for a few minutes then it's ok. I'm having few problems overclocking (maybe not to the extent of some 
). I think I may have stopped the booting too - I hope so anyway :?: It seems to have stopped since I removed a self-powered USB hub I had connected.
Anyway I've got:
E6600 running @ 3.2G (7 x 457)
Zalman 9500 CPU Cooler
Corsair CM2X1024-6400C4 (1:1 @ 914 / 4-4-4-12)
GF 8800 GTS
4 x 250GB WD SATA1 ( 2 x 500GB raid 0) (from old setup)
2 x 300GB WD SATA1 in IDE mode on Gigabyte contoller (from old setup)
2 x BENQ 1640's on the IDE controller as well (from old setup)
Got a Thermaltake 750W power supply. Wasn't sure what to do at first as far as 4x4 connection (which this PSU has) & extra molex connection on MB - The manual was just plane confusing, so I ended up just connecting everything and hoping for the best.
Settings:
All CPU stuff like Eist, C1E, no execute, & virtualization I have disabled - left thermal monitor on to be safe.
Multiplier to 7. FSB to 457. Mem @ 1:1 (or 2 as MB says). PCIE @ auto
Mem Voltage + .325 (+.3 is stock for the RAM)
MCH + .25
FSB + .30
CPU 1.3375
Set Mem to 4-4-4-12 & left all other mem settings at auto other than setting one thing to 'fast'.
In health I have all the wakeup from whatever stuff disabled as well as HPET (whatever that is) and fan controls disabled.
Anyway, here's some screen shots to show what's going on
If the reboot thing keeps happening I'll give the F7 a go and see how it is.
Mick
Hi all,
Well, the reboot issue came about again with F8. What I found is that with the self powered USB hub in place it takes many attempts to get it started again e.g., turning off power and waiting a few minutes & veen after emoving battery for a few minutes; without the hub it starts after one time doing this. From what I can gather the HUB seems to keep supplying the MB with power when it's powered off and PSU plug removed - I noticed the LED on my webcam would stay on even with system off and PSU unplugged when I was having the problem, but other times when booting fine the LED would be off when powered down. So the HUB seems to be stopping the MB completely powering off at times - well that's my uneducated diagnosis anyway 
I've flashed back to F7 (first time for me using this). Strange thing is everyone raves about this bios - I can't get past booting @ 440FSB with this bios though with F8 I could boot at 460FSB (most of the time ).
First attempt booting with F7 = same problem (5 seconds on / off in continuous cycles). So I removed power and battery and then booted fine. Then a few times it kicked me to backup BIOS F8 on boot. So dropped FSB back to 440 on F7 and not a prob booting since. But hey, at least kicking me to the backup BIOS is an improvement - something F8 never did (BTW - MB delivered with backup F3)
The frustrating thing about this MB is that (with either BIOS) I can run 2 x prime9 no problems; prime2004 no problem; microsoft memory diagnostic extended tests no problems; memtest86 no problems. With F8 I've done each test for over 24 hrs straight. I've only had F7 in place for 12 hours & did windows mem diag for 7 hours while I slept & now have had prime2004 running for 4 hrs without any probs.
With F8 I've even deliberately left air con off and window open on hot days (Summer here in Aus ). This left an ambient room temp of over 34C (temp probe in case 48C) to rule out temp as an issue - I ran prime2004 for 8 hours with CPU reaching 79C still no errors; then next day same with windows mem diagnostic & no problems.
It definitely seems to be an issue with booting & how motherboard applies or interprets voltages at this time. Seems the only thing that makes sense as once past the boot stage you go torture the %^$^% 
out of the system without a problem.
BTW I briefly flirted with F9 before going back to F7. My advice - leave tis BIOS the %^$# alone, it's horribly unstable & resulted in my first blue screens since owning this MB, even with very mild overclocks.
The only certain things I can say are:
removing the USB self-powered HUB has helped me
Once past booting everything is fine.
Here's hoping they can finally get a BIOS together that addresses booting issues properly
See Ya
Mick :?
Haven't got time to look now about to go out. But I'm sure I found the link to it @ these forums. If not search around. Not sure if it's beta or leaked but it's real
| Quote : Hi all,
|
even the USB portion of your statement deserves it's own post in the hardware section, I think anyway, cuz it's getting away from the topic at hand, here we go...
I dunno what's going on, but just to tell ya that I have a self powering Targus USB 2.0 hub. No problems with it here with this mobo or any of the BIOS versions I've used. I also have a Logitech WebCam Orb & it stays on standby mode with the little red light on (no image or video capturing is done unless I activate some application that will use it), along with the USB hub even though my system is powered off. The Cam & the USB hub have always stayed on even with my previous systems & I've had them for a little over a year now. I think this is normal for my stuff since the mobo is still sending some sort of power so that I can turn my system on from the keyboard's space bar & since the hub is connected to the USB ports & so is my wireless keyboard's & hub.
| Quote :
|
I gues you're referring to F9. My experience with it is *&*(%*( horrible. Yes the boot issue is fixed but the system is so unstable it's a joke.
So Far for me with E6600 & Corsair DDR2 C6400C4 4-4-4-12. All CPU stuff like Eist, C1E, no execute, & virtualization I have disabled - left thermal monitor on to be safe.
Mem @ 1:1 (or 2 as MB says).
PCIE @ auto
Mem Voltage + .325 (+.3 is stock for the RAM)
MCH +.30
FSB + .30
CPU 1.3375
tried more varioations with F9 (nothing worked):
_____________________________________________________________
F7
7x450 FSB = 3.15G CPU & 900 Mem @ 4-4-4-12
2 x Prime 95 stable 8 hours; prime 2004 stable 8 hours; microsoft memory diagnositc all night no problems; memtest86+ 8 hours no problems. prime95 & prime2004 done while using comp as normal(e.g runnning virus scans, browsing net, using word & outlook, downloading with bitcomet). No errors any test had to stop due to time constraints.
System solid as a rock when running.
Cold boot problems = need to unplug power 30 secs then ok
Reboot from OS no problems
Can solve boot problems by setting voltages to Auto in BIOS. But CPU reads 1.55 - 1.65v in diagnostic utilities & runs too hot. Same utilities read 1.33 - 1.34 normally
_____________________________________________________________
F8
7x458 FSB = 3.2G CPU & 916 Mem @ 4-4-4-12
2 x Prime 95 stable; prime 2004; microsoft memory diagnositc; & memtest86+ all stable for abt 24 hrs. Once again using comp like normal while running prime tests.
System solid as a rock when running.
Even tried prime2004 for 6 hours with window open on hot day no aircon to see if heat an issue - ambient temp abt 34C & CPU sat between 68 and peaking at 79C at times & no probs at all
Cold boot problems = need to unplug power 30 then ok. sometimes have to do this many times with F8
Reboot from OS= sometimes powers right down & get cold boot problem. Usually takes clearing CMOS to get back running or at least many times with unplugging PSU
Once again, can solve boot problems by setting voltages to Auto in BIOS. But CPU reads 1.5 - 1.6v again
_____________________________________________________________
F9
7 x 458 FSB = 3.2G CPU & 916 Mem @ 4-4-4-12
2 x Prime 95 stable instant crash & Blue screen; prime 2004 blue screen within 1 ninute; microsoft memory diagnositc errors constantly ; memtest86+ 24 locks system
Sandra CPU & Mem Tests = crash & blue screen
virus scan = crash & blue screen
Rarely system up more than 5-10 minutes before blue screen
Cold boot = No Problem
Reboot from OS = No Problem
7x450 FSB = 3.15G CPU & 900 Mem @ 4-4-4-12
2 x Prime 95 stable instant crash & Blue screen; prime 2004 blue screen within 1 ninute; microsoft memory diagnositc errors constantly ; memtest86+ 24 constant errors
Sandra benchmarks = carsh & blue screen sometimes
virus scan = crash & blue screen within 10-15 minutes
System ok for light tasks
Cold boot = No Problem
Reboot from OS = No Problem
7x442 FSB = 3.1G CPU & 884 Mem @ 4-4-4-12
2 x Prime 95 errors within 20 minutes sometimes blue screen; prime 2004 lasts about 15 minutes sometimes blue screen; microsoft memory diagnositc errors constantly ; memtest86+ 24 constant errors
Sandra memory test = ok soemtimes; somtimes locksup sandra
virus scan = blue screen within 40-50 minutes
System ok for light tasks
Cold boot = No Problem
Reboot from OS = No Problem
7x428 FSB = 3.0G CPU & 856 Mem @ 4-4-4-12
2 x Prime 95 errors within 60 minutes; prime 2004 lasts about 30 minutes; microsoft memory diagnositc errors lots of errors on some tests ; memtest86+ 24 some tests produce streams of errors
Sandra memory test = ok
virus scan = sometimes crash & blue screen
Ok for most tasks with some crashes
Cold boot = No Problem
Reboot from OS = No Problem
Auto voltages = same results. Upping voltages = same results.
_____________________________________________________________
God knows what they've done with F9 there is a new setting which has values 1 or 2 for people running 1000+ RAM. Maybe this needs a disabled setting as well.
I really think the boot issue is related to how the motherboard supplies power or detects power levels when booting. With F7 & F8, even with successful boots, it seems to power on softly for 3-5 seconds and then kick in the power. I think the power levels are too low to RAM and/or CPU or are being detected as too low during this period. Maybe this is why auto setings seem to solve the problem.
With F9 - if I'm not imagining things by now :? - this low power period seems much shorter; full power to fans etc seems to kick in much quicker.
So F9 solves my boot issues and creates more problems 
Back to F7 with F8 as backup.
See Ya
Mick
it WORKED !
now we can confirm its the same Bios for both of us
| Quote : @mikey why don't u try 400x8 1:1? vcore 1.300 - 1.32500 (depend on your cpu week), default v.mch and v.fsb. And plz let me know the result.
|
Hi,
Yes 8x400 works fine for me with F7 & F8. I prefer 7x458 because it gives me extra memory bandwidth - I can run the memory 4-4-4-12 1:1 @ 458 and get over 7.5GB/s bandwidth with Sandra test but at 400x8 the best I can do is about 6.8GB/s.
Now for the good news I'm running F8 again after my disaster with F9. I noticed after I flashed back to F8 and cleared cmos by removing battery for a few minutes upon boot it went in reboot cycles agin. When I finally got it started again (discovered repeatedly hitting reset switch works too)most settings were at default but it still had my raid array set up properly and overclock settings:?:
Thought about this and think one of two things:
1) when flashing it reads some stuff from cmos and loads it to bios2) Accesses some info from the backup bios when cmos cleared (F7 in my case)So I removed battery for about 10 minutes to clear cmos and then flashed both main to F8 and backup to F7, both with "keep DMI Data" disabled. I then (at a guess) pressed "load default settings" and QFlash asked me what to call it so simply named it 'default'
Turned off machine and diconncted power and battery again. 10 minutes later booted machine and booted and then scared the hell out of me with a blank screen, then a few seconds later it popped up a box and asked me which settings to apply - my only choice was 'default' from before to I chose it. I was presented with an absolutely clean bios.
Set up all the important stuff no overclock and rebooted - all ok. Then powered down and put my FSB to 458 divider @ 7 (3.2G) memory at 1:1 settings 4-4-4-12 fast the rest auto. Set voltage to Auto. Crossed fingers and booted and it booted first time 8O
Only thing about auto voltage is it sets CPU way above what it needs. In ET5 showing RAM @ 2.2v & CPU @ 1.57-1.63v (way too high but I think it may overreport a little). I ran 2 x prime95 for a couple of hours and gradually reduced CPU voltage via ET5 found it stable down to value of about 1.4 then crashed. Then same with RAM and found it crashed the minute I lowered the RAM by anything.
Went into BIOS set RAM @ +.325 @ CPU one level above 1.375 (forget number now I'm at work). Set mem controller and FSB +.25.
Saved settings, crossed fingers, and pressed 'y'. The thing booted fine
CPU voltage reported in ET5 as 1.4 & CPU-Z as 1.36. Ran prime95 x2 for a few hours while I checked email, browsed, etc. Did a (very slow) virus scan with prime running. No problems. Installed a few pieces of sofware that required reboot no problems.
Left prime2004 running for 7 hours while I slept and no errors. Got up and powered down comp. Showered and got ready for work and went for the final test - the cold boot. Not a problem
Not 100% about this, but to me its seems to get a totally clean bios you may need to clear cmos before flashing, and flash both main and backup with your choice of versions with the 'remeber dmi' disabled. I think this ensures each bios is clean. As I said before the bios may possibly pick up cmos data when flashing or from backup on first boot - either way, even though you clear cmos after flash your bios isn't 100% clean. All I know is a fresh flash of F8 knew my OC settings and Raid setup first boot after clearing cmos, so it was somehow inbedded in there without me doing it. I imagine after many flashes and booting from backup and main you may end up with a very mixed up bios.
Anyway I'm now using F8 with CPU @ 3.2G(458x7) DDR @ 916/4-4-4-12, perfectly stable, with no more boot problems
I suppose a frustrating week getting this board stable:
Some observations The self-powered USB hub without doubt made my boot issues worse, so I was reminded to never assume something is compatibleAuto voltage settings in bios set CPU much higher than needed. Just thinking that default DDR is 1.8 mine was 2.25 & default CPU is 1.325 and mine showed up to 1.62. abt 20% for both - is it just a % applied across all voltages when set to auto?If possible it would be great to have individual 'auto' settings for voltage e.g., set cpu to 3.375 and leave the rest at auto. Maybe give us a way to monitor MCH and FSB voltages in flight so we get an an idea whats happening with them. Clearing CMOS after a flash doesn't mean you have a clean bios. Remember the old days flashing in dos with switches like /py /sn /cks /r - clear CMOS, DMI, PnP data and reboot. With everything so automated sometimes forget the importance of these things. With the dual BIOS it seems we have to clear CMOS first and then flash both main & backup, with save DMI info disabled, to be sure of a clean BIOS image; at least from my experience with F8 seeming to read my mind 8O
See Ya
Mick
BTW - it seems most people are finding F9 good. If a few more people say the same I may use the new flashing method with F9 and give it another chance. Then again if things stay how they are why stuff around unless the BIOS contains any worthwhile updates for onboard stuff
| Quote : @mikey why don't u try 400x8 1:1? vcore 1.300 - 1.32500 (depend on your cpu week), default v.mch and v.fsb. And plz let me know the result.
|
Hi,
Yes 8x400 works fine for me with F7 & F8. I prefer 7x458 because it gives me extra memory bandwidth - I can run the memory 4-4-4-12 1:1 @ 458 and get over 7.5GB/s bandwidth with Sandra test but at 400x8 the best I can do is about 6.8GB/s.
Now for the good news I'm running F8 again after my disaster with F9. I noticed after I flashed back to F8 and cleared cmos by removing battery for a few minutes upon boot it went in reboot cycles agin. When I finally got it started again (discovered repeatedly hitting reset switch works too)most settings were at default but it still had my raid array set up properly and overclock settings:?:
Thought about this and think one of two things:
1) when flashing it reads some stuff from cmos and loads it to bios2) Accesses some info from the backup bios when cmos cleared (F7 in my case)So I removed battery for about 10 minutes to clear cmos and then flashed both main to F8 and backup to F7, both with "keep DMI Data" disabled. I then (at a guess) pressed "load default settings" and QFlash asked me what to call it so simply named it 'default'
Turned off machine and diconncted power and battery again. 10 minutes later booted machine and booted and then scared the hell out of me with a blank screen, then a few seconds later it popped up a box and asked me which settings to apply - my only choice was 'default' from before to I chose it. I was presented with an absolutely clean bios.
Set up all the important stuff no overclock and rebooted - all ok. Then powered down and put my FSB to 458 divider @ 7 (3.2G) memory at 1:1 settings 4-4-4-12 fast the rest auto. Set voltage to Auto. Crossed fingers and booted and it booted first time 8O
Only thing about auto voltage is it sets CPU way above what it needs. In ET5 showing RAM @ 2.2v & CPU @ 1.57-1.63v (way too high but I think it may overreport a little). I ran 2 x prime95 for a couple of hours and gradually reduced CPU voltage via ET5 found it stable down to value of about 1.4 then crashed. Then same with RAM and found it crashed the minute I lowered the RAM by anything.
Went into BIOS set RAM @ +.325 @ CPU one level above 1.375 (forget number now I'm at work). Set mem controller and FSB +.25.
Saved settings, crossed fingers, and pressed 'y'. The thing booted fine
CPU voltage reported in ET5 as 1.4 & CPU-Z as 1.36. Ran prime95 x2 for a few hours while I checked email, browsed, etc. Did a (very slow) virus scan with prime running. No problems. Installed a few pieces of sofware that required reboot no problems.
Left prime2004 running for 7 hours while I slept and no errors. Got up and powered down comp. Showered and got ready for work and went for the final test - the cold boot. Not a problem
Not 100% about this, but to me its seems to get a totally clean bios you may need to clear cmos before flashing, and flash both main and backup with your choice of versions with the 'remeber dmi' disabled. I think this ensures each bios is clean. As I said before the bios may possibly pick up cmos data when flashing or from backup on first boot - either way, even though you clear cmos after flash your bios isn't 100% clean. All I know is a fresh flash of F8 knew my OC settings and Raid setup first boot after clearing cmos, so it was somehow inbedded in there without me doing it. I imagine after many flashes and booting from backup and main you may end up with a very mixed up bios.
Anyway I'm now using F8 with CPU @ 3.2G(458x7) DDR @ 916/4-4-4-12, perfectly stable, with no more boot problems
I suppose a frustrating week getting this board stable:
Some observations The self-powered USB hub without doubt made my boot issues worse, so I was reminded to never assume something is compatibleAuto voltage settings in bios set CPU much higher than needed. Just thinking that default DDR is 1.8 mine was 2.25 & default CPU is 1.325 and mine showed up to 1.62. abt 20% for both - is it just a % applied across all voltages when set to auto?If possible it would be great to have individual 'auto' settings for voltage e.g., set cpu to 3.375 and leave the rest at auto. Maybe give us a way to monitor MCH and FSB voltages in flight so we get an an idea whats happening with them. Clearing CMOS after a flash doesn't mean you have a clean bios. Remember the old days flashing in dos with switches like /py /sn /cks /r - clear CMOS, DMI, PnP data and reboot. With everything so automated sometimes forget the importance of these things. With the dual BIOS it seems we have to clear CMOS first and then flash both main & backup, with save DMI info disabled, to be sure of a clean BIOS image; at least from my experience with F8 seeming to read my mind 8O
See Ya
Mick
BTW - it seems most people are finding F9 good. If a few more people say the same I may use the new flashing method with F9 and give it another chance. Then again if things stay how they are why stuff around unless the BIOS contains any worthwhile updates for onboard stuff
You have a hardware problem.
| Quote : You have a hardware problem. |
Hi,
Just wondering what makes you think I have a hardware problem :?:
I'm running perfectly stable @ 3.2 G / 1.34v with memory 1:1 / 4-4-4-12. And it now boots fine
Is it because I can't OC the CPU by 30% undervolted to 1.300 like you claim to be able to do. Can you post some pics such as below with CPU OC to 3200 with voltage at 1.300.
The only hardware giving me any problems was the USB hub & at 916 I've reached the limits of what my 800 RAM will do with nice timings.
I really can't see where the hardware problem is 8O
If you have some ideas I'm interested to know.
Mick
Please mind
You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.
Sponsored links
Ad
Related Topics
- Prime95 version 24.14
- New System Need Help to decide.
- Cooling Help
- Roadblock with my Opty 165
- Help! e6600 bx2 question about memory and overclocking
- Can someone help me find?
- Gigabyte DS3 out of stock on NewEgg - Help
- Mobo suggestions for overclocking Pentium D 805
- 965? 975x? 680? Need a lil help
They won a badge
Join us in greeting them
- 01:00 agentgod won the Freshman badge
- 01:00 Malcer won the Uniformed badge
- 01:00 bbr256 won the Uniformed badge
- 01:00 samborambo47 won the Uniformed badge
- 01:00 clarastewart07 won the Uniformed badge
- 01:00 DrgnRebrn won the Uniformed badge
- 01:00 computer_veteran won the Freshman badge
- 01:00 groundhog won the Freshman badge
- 01:00 rasonjowe won the Freshman badge
- 01:00 overshocked won the Spy badge