Jump to content

Dasizzle

Member
  • Posts

    32
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Dasizzle reacted to twovaliant2 in Acer Predator X34 34" Curved 3440x1440 75Hz Monitor w/ G-Sync available in August and for around £999!   
    Was looking at ultra wide monitors to buy in spring....saw this post, thought it was a joke. Then read it again...searched internet. Read post again. SIGH
     
    Well....I guess i don't need to look for a monitor now. :]
  2. Like
    Dasizzle reacted to Keudn in Samsung 840/840 EVO Firmware Upgrade - Release   
    YAY! I was starting to get worried as this was my first choice for my 1TB SSD I want, looks like I will be getting it after all!
  3. Like
    Dasizzle reacted to SeanBond in Samsung 840/840 EVO Firmware Upgrade - Release   
    Awesome, been waiting for this. I was starting to see performance degredation whenever I checked a ssd benchmark. I have only been hitting about 350 sequential reads over 555 when I first got my drive. 
  4. Like
    Dasizzle got a reaction from MountainDrew in Samsung 840/840 EVO Firmware Upgrade - Release   
    Samsung's 840 EVO update fixes slow reads with old data
    An early look at the EVO's Performance Restoration tool
    by Geoff Gasior — 6:28 PM on October 14, 2014
     
    Last month, Samsung confirmed that its 840 EVO SSD can suffer from slower read speeds with older data. The company promised to address the issue with updated firmware, and we've been experimenting with the fix.
    Before we get into the results of our testing, we should spend a moment on the problem itself. Here's how Samsung describes the issue:

    SSDs usually calibrate changes in the statuses of cells over time via the flash management software algorithm. Due to the error in the software algorithm, the 840 EVO performed read-retry processes aggressively, resulting in a drop in overall read performance. This only occurs if the data was kept in its initial cell without changing, and there are no symptoms of reduced read performance if the data was subsequently migrated from those cells or overwritten.
    Read-retry is used to compensate for changes in cell voltages, suggesting that voltage drift over time was a key factor here. The EVO's flash management routines evidently haven't been responding to voltage changes correctly.
    Fixing the problem is a two-part process managed by Samsung's appropriately named Performance Restoration tool. First, the utility flashes the SSD's firmware with the new EXT0CB6Q revision. Then, it reboots the system and completes the restoration process, which we're told involves "conditioning" the NAND. The entire process is non-destructive, so it shouldn't compromise any data on the drive. It also only needs to be run once. That said, the target drive must have at least 10% free capacity for the tool to work its magic.
    The data on the 840 EVOs we have in the lab isn't old enough to be affected by the flaw. Fortunately, our resident developer, Bruno "morphine" Ferreira, has been running an 840 EVO 500GB in his personal system for more than 10 months. Having already noticed slower performance with older files, he bravely volunteered to test Samsung's fix.
    The restoration process went off without a hitch, though it took over an hour to condition Bruno's drive. Read speeds seem to be much improved. Below is a screenshot from HD Tach, which tests read performance across the extent of the drive. Click the buttons below the image to switch between results from before and after the fix was applied.

    Those dips before the fix correspond to performance slowdowns with older data. They're nowhere to be found after the fix, where read speeds are much more consistent overall.
    Samsung recommended running HD Tach to evaluate the fix, but we also had Bruno try SSD Read Speed Tester, which was developed specifically in response to the EVO issue. The graphs below depict the range of file read speeds based on the age of the data. Again, use the buttons to switch between the before and after results.

    The differences here aren't as striking, but there's a definite improvement in read performance for older files. Some of the individual files load more than 2X faster after the fix, and one of them experienced a massive 6X speedup. Your mileage may vary, of course, but Samsung's fix seems to work as advertised.
    After applying the EVO update, Bruno also noticed snappier application load times. He says Windows now boots faster, too, particularly after it reaches the desktop and starts filling out the taskbar. We don't have hard data on how the fix impacts load times, but OS and application files are likely to be older, so they're good candidates for a speed boost.
    Apart from addressing read speeds with older files, the new EVO firmware is supposed to perform identically to the previous release. Bruno ran a couple of quick CrystalDiskMark benchmarks before and after applying the fix, and the scores are pretty much identical.

    Given how the bug manifests, we won't know if the EVO is truly fixed until at least a month from now, when freshly written data will be old enough to exhibit slower read performance. Samsung is confident that the problem has been addressed, though, and the company has updated its validation procedures to look for similar issues in future products. For what it's worth, Samsung says the problem is unique to the 840 EVO and not an artifact of that drive's TLC NAND. The older, TLC-based 840 Series is unaffected, and so is the upcoming 850 EVO, which will use the three-bit version of 3D V-NAND.
    If all goes well with final testing, the 840 EVO Performance Restoration tool will be released this week. There are still some associated caveats, like the updater not working with SSDs in RAID arrays or with older AMD SATA drivers, but those restrictions aren't too different than those that typically come along with new SSD firmware. We'll post a link to the update tool once it's available.
    Update — Samsung has released its Performance Restoration tool to the masses. The utility is available here, while the installation guide can be found here. Although the tool is Windows-only right now, a DOS-based version is coming before the end of the month. That release should allow Mac and Linux users to perform the update via thumb drive.
    Source: Tech Report
     
  5. Like
    Dasizzle got a reaction from Archangel1994 in Samsung 840/840 EVO Firmware Upgrade - Release   
    Samsung's 840 EVO update fixes slow reads with old data
    An early look at the EVO's Performance Restoration tool
    by Geoff Gasior — 6:28 PM on October 14, 2014
     
    Last month, Samsung confirmed that its 840 EVO SSD can suffer from slower read speeds with older data. The company promised to address the issue with updated firmware, and we've been experimenting with the fix.
    Before we get into the results of our testing, we should spend a moment on the problem itself. Here's how Samsung describes the issue:

    SSDs usually calibrate changes in the statuses of cells over time via the flash management software algorithm. Due to the error in the software algorithm, the 840 EVO performed read-retry processes aggressively, resulting in a drop in overall read performance. This only occurs if the data was kept in its initial cell without changing, and there are no symptoms of reduced read performance if the data was subsequently migrated from those cells or overwritten.
    Read-retry is used to compensate for changes in cell voltages, suggesting that voltage drift over time was a key factor here. The EVO's flash management routines evidently haven't been responding to voltage changes correctly.
    Fixing the problem is a two-part process managed by Samsung's appropriately named Performance Restoration tool. First, the utility flashes the SSD's firmware with the new EXT0CB6Q revision. Then, it reboots the system and completes the restoration process, which we're told involves "conditioning" the NAND. The entire process is non-destructive, so it shouldn't compromise any data on the drive. It also only needs to be run once. That said, the target drive must have at least 10% free capacity for the tool to work its magic.
    The data on the 840 EVOs we have in the lab isn't old enough to be affected by the flaw. Fortunately, our resident developer, Bruno "morphine" Ferreira, has been running an 840 EVO 500GB in his personal system for more than 10 months. Having already noticed slower performance with older files, he bravely volunteered to test Samsung's fix.
    The restoration process went off without a hitch, though it took over an hour to condition Bruno's drive. Read speeds seem to be much improved. Below is a screenshot from HD Tach, which tests read performance across the extent of the drive. Click the buttons below the image to switch between results from before and after the fix was applied.

    Those dips before the fix correspond to performance slowdowns with older data. They're nowhere to be found after the fix, where read speeds are much more consistent overall.
    Samsung recommended running HD Tach to evaluate the fix, but we also had Bruno try SSD Read Speed Tester, which was developed specifically in response to the EVO issue. The graphs below depict the range of file read speeds based on the age of the data. Again, use the buttons to switch between the before and after results.

    The differences here aren't as striking, but there's a definite improvement in read performance for older files. Some of the individual files load more than 2X faster after the fix, and one of them experienced a massive 6X speedup. Your mileage may vary, of course, but Samsung's fix seems to work as advertised.
    After applying the EVO update, Bruno also noticed snappier application load times. He says Windows now boots faster, too, particularly after it reaches the desktop and starts filling out the taskbar. We don't have hard data on how the fix impacts load times, but OS and application files are likely to be older, so they're good candidates for a speed boost.
    Apart from addressing read speeds with older files, the new EVO firmware is supposed to perform identically to the previous release. Bruno ran a couple of quick CrystalDiskMark benchmarks before and after applying the fix, and the scores are pretty much identical.

    Given how the bug manifests, we won't know if the EVO is truly fixed until at least a month from now, when freshly written data will be old enough to exhibit slower read performance. Samsung is confident that the problem has been addressed, though, and the company has updated its validation procedures to look for similar issues in future products. For what it's worth, Samsung says the problem is unique to the 840 EVO and not an artifact of that drive's TLC NAND. The older, TLC-based 840 Series is unaffected, and so is the upcoming 850 EVO, which will use the three-bit version of 3D V-NAND.
    If all goes well with final testing, the 840 EVO Performance Restoration tool will be released this week. There are still some associated caveats, like the updater not working with SSDs in RAID arrays or with older AMD SATA drivers, but those restrictions aren't too different than those that typically come along with new SSD firmware. We'll post a link to the update tool once it's available.
    Update — Samsung has released its Performance Restoration tool to the masses. The utility is available here, while the installation guide can be found here. Although the tool is Windows-only right now, a DOS-based version is coming before the end of the month. That release should allow Mac and Linux users to perform the update via thumb drive.
    Source: Tech Report
     
  6. Like
    Dasizzle reacted to Archangel1994 in Samsung 840/840 EVO Firmware Upgrade - Release   
    Good, now I can recommend the 840 EVO again without any issues whatsoever. Bookmarking this for now because the ones in store now will most likely not have this update
  7. Like
    Dasizzle got a reaction from SeanBond in Samsung 840/840 EVO Firmware Upgrade - Release   
    Samsung's 840 EVO update fixes slow reads with old data
    An early look at the EVO's Performance Restoration tool
    by Geoff Gasior — 6:28 PM on October 14, 2014
     
    Last month, Samsung confirmed that its 840 EVO SSD can suffer from slower read speeds with older data. The company promised to address the issue with updated firmware, and we've been experimenting with the fix.
    Before we get into the results of our testing, we should spend a moment on the problem itself. Here's how Samsung describes the issue:

    SSDs usually calibrate changes in the statuses of cells over time via the flash management software algorithm. Due to the error in the software algorithm, the 840 EVO performed read-retry processes aggressively, resulting in a drop in overall read performance. This only occurs if the data was kept in its initial cell without changing, and there are no symptoms of reduced read performance if the data was subsequently migrated from those cells or overwritten.
    Read-retry is used to compensate for changes in cell voltages, suggesting that voltage drift over time was a key factor here. The EVO's flash management routines evidently haven't been responding to voltage changes correctly.
    Fixing the problem is a two-part process managed by Samsung's appropriately named Performance Restoration tool. First, the utility flashes the SSD's firmware with the new EXT0CB6Q revision. Then, it reboots the system and completes the restoration process, which we're told involves "conditioning" the NAND. The entire process is non-destructive, so it shouldn't compromise any data on the drive. It also only needs to be run once. That said, the target drive must have at least 10% free capacity for the tool to work its magic.
    The data on the 840 EVOs we have in the lab isn't old enough to be affected by the flaw. Fortunately, our resident developer, Bruno "morphine" Ferreira, has been running an 840 EVO 500GB in his personal system for more than 10 months. Having already noticed slower performance with older files, he bravely volunteered to test Samsung's fix.
    The restoration process went off without a hitch, though it took over an hour to condition Bruno's drive. Read speeds seem to be much improved. Below is a screenshot from HD Tach, which tests read performance across the extent of the drive. Click the buttons below the image to switch between results from before and after the fix was applied.

    Those dips before the fix correspond to performance slowdowns with older data. They're nowhere to be found after the fix, where read speeds are much more consistent overall.
    Samsung recommended running HD Tach to evaluate the fix, but we also had Bruno try SSD Read Speed Tester, which was developed specifically in response to the EVO issue. The graphs below depict the range of file read speeds based on the age of the data. Again, use the buttons to switch between the before and after results.

    The differences here aren't as striking, but there's a definite improvement in read performance for older files. Some of the individual files load more than 2X faster after the fix, and one of them experienced a massive 6X speedup. Your mileage may vary, of course, but Samsung's fix seems to work as advertised.
    After applying the EVO update, Bruno also noticed snappier application load times. He says Windows now boots faster, too, particularly after it reaches the desktop and starts filling out the taskbar. We don't have hard data on how the fix impacts load times, but OS and application files are likely to be older, so they're good candidates for a speed boost.
    Apart from addressing read speeds with older files, the new EVO firmware is supposed to perform identically to the previous release. Bruno ran a couple of quick CrystalDiskMark benchmarks before and after applying the fix, and the scores are pretty much identical.

    Given how the bug manifests, we won't know if the EVO is truly fixed until at least a month from now, when freshly written data will be old enough to exhibit slower read performance. Samsung is confident that the problem has been addressed, though, and the company has updated its validation procedures to look for similar issues in future products. For what it's worth, Samsung says the problem is unique to the 840 EVO and not an artifact of that drive's TLC NAND. The older, TLC-based 840 Series is unaffected, and so is the upcoming 850 EVO, which will use the three-bit version of 3D V-NAND.
    If all goes well with final testing, the 840 EVO Performance Restoration tool will be released this week. There are still some associated caveats, like the updater not working with SSDs in RAID arrays or with older AMD SATA drivers, but those restrictions aren't too different than those that typically come along with new SSD firmware. We'll post a link to the update tool once it's available.
    Update — Samsung has released its Performance Restoration tool to the masses. The utility is available here, while the installation guide can be found here. Although the tool is Windows-only right now, a DOS-based version is coming before the end of the month. That release should allow Mac and Linux users to perform the update via thumb drive.
    Source: Tech Report
     
  8. Like
    Dasizzle got a reaction from neonfusion in 840 EVO Firmware read performance fix release to the public on October 15th !   
    Anyone with a 840 Evo getting this problem should be exited !

    More info about the problem here: http://www.anandtech.com/show/8550/samsung-acknowledges-the-ssd-840-evo-read-performance-bug-fix-is-on-the-way
     
    Source: http://www.anandtech.com/show/8570/firmware-update-to-fix-the-samsung-ssd-840-evo-read-performance-bug-coming-on-october-15th

  9. Like
    Dasizzle reacted to scaryjam823 in Giving my OPO one+one invites out d:   
    Well it's a good thing you told us here to raise your post count instead of ignoring the thread.
  10. Like
    Dasizzle got a reaction from Bensemus in Mod24(+24) AFTERMATH! My story. Post pictures of your desk or a story!   
    So it begins with me telling my boss "yo i cant come to work 19th of september".  That was fine. but i didn't quite calculated the time zone difference between Me in Denmark (UTC+1) And Game24 (PDT)... So i am practically 9  hours ahead! 
    Okay so i wake up at 08:00 AM 18th (PDT 11PM 17th) Driving to work. Done about 11 hours later. Then i went straight to supermarked to get aaaaaaalll the supplies i could possible need for 24 hours with no sleep!  Redbulls, icetea, soda, candy, frozen pizzas and so on. 
    09:00 PM 18th (PDT 06:00  AM 18) Home again! so i just had to do i few things and then take 5-6 hours sleep before the show. perfect! okay... those things took a little longer so 6 hours became to 3-4.. I where layin in my bed for 1½ hour trying to force my self to sleep just a tiny bit, but unfortunately i was just to damn excited!!   
     
    THE SHOW! First of all a  little confusing with the whole nvidia twitch thing not work as it should d: had especility problem with my 21:9 monitor. so ended up using LinusTech when it came online (Thanks Luke) !
    Yeah nothing much to say about  me stoning in front of a screen for more than 24 hours..  
    I think you guys did a amazing job, especially surprised by the way you and luke keep going with almost no scripting! As for the camera, sound guys and so called "controll center" nice job as well! 

    TWITCH and Twitter blitz ! awesome to get all the peoples insight! I tried and tried, tried some more and tried again to post both Worst computer memory, best allnighter, first allnighter how tired i was. but it where never seen d: bad luck BUT here is some 
     
    "#Mod24 Best Allnighter. this norwegian dude lost a bed to someone, and where contacting ppl on the web to be used as slave for 1 day! i accepted, hosted a lan, got free pizza and a nice footrest for 16 hours !AWESOME !"

    "#Mod24 Worst computer mistake... Changing Ram on my fathers computer when i was 7, burning the whole thing down.. he where a doctor.. so not smart. all data lost !"

    @LinusTech Im at my 35th hour soon. Btw i Live in Denmark (GMT1) I was so exited that i couldn't sleep, after 10 hours work. i sure make it to the 43Hours+ ! i cant miss the WANSHOW ! I love you guys, an what you do.

     
    The Linus twitch channel was just amazing! i have written to some of you guys for 24 hours straight, so amazing. we where 3 or 4 guys giving each other head ups and energy to make it through! TOGETHER WE ARE STRONG Shoutout to @benemus and @DeViLzzz! and good job !

    Wow.. the last few hours was so hard.. i haven't slept for 42 hours in that point of time, i where short of redbulls and had already crossed to daily dose for caffeine pills! My stomach where yelling in pain because all of the bad fast food and soda was burning through my stomach d:  

    I MAD IT TO THE WAN SHOW !!   NICE job everyone ! You can take a look at my other tread for the Pre mod24 preparations  http://linustechtips.com/main/topic/217671-post-your-preparations-for-game24-now/ 

    i have posted some pictures of the aftermath and other random stuff d: 






  11. Like
    Dasizzle got a reaction from DeViLzzz in Mod24(+24) AFTERMATH! My story. Post pictures of your desk or a story!   
    As linus said.  " we should make tshirt that say "I survived MOD24" 
    WE need special editions.. "I survived MOD 24+24
     
  12. Like
    Dasizzle got a reaction from alby800 in Mod24(+24) AFTERMATH! My story. Post pictures of your desk or a story!   
    3. Yes kinda normal. doing a lot of cloning  and experiments d: 
    4. YES i like theme ! as long you have a decent sound card that can power them! MUCH value for money!
    5 Im sorry ! Shout at me next time !
    6..   i dont know...
    7. I love membran! sorry, but that is just the way it is !
  13. Like
    Dasizzle reacted to Intervalence in Mod24(+24) AFTERMATH! My story. Post pictures of your desk or a story!   
    I thought everyone just used their expensive computer components as cup holder things? You know the titan black makes one hell of a coaster. 
  14. Like
    Dasizzle reacted to DeViLzzz in Mod24(+24) AFTERMATH! My story. Post pictures of your desk or a story!   
    Dasizzle thanks for sharing the photos and really ...

    I am just glad nobody has died from MOD24 ....

    That we know of.

    PS: OMG the energizer pills you have. LOL ... and Nutella well if you love it I heard it is going up in price huge cuz of some big weather event killing crops.
  15. Like
  16. Like
  17. Like
    Dasizzle got a reaction from DeViLzzz in Mod24(+24) AFTERMATH! My story. Post pictures of your desk or a story!   
    So it begins with me telling my boss "yo i cant come to work 19th of september".  That was fine. but i didn't quite calculated the time zone difference between Me in Denmark (UTC+1) And Game24 (PDT)... So i am practically 9  hours ahead! 
    Okay so i wake up at 08:00 AM 18th (PDT 11PM 17th) Driving to work. Done about 11 hours later. Then i went straight to supermarked to get aaaaaaalll the supplies i could possible need for 24 hours with no sleep!  Redbulls, icetea, soda, candy, frozen pizzas and so on. 
    09:00 PM 18th (PDT 06:00  AM 18) Home again! so i just had to do i few things and then take 5-6 hours sleep before the show. perfect! okay... those things took a little longer so 6 hours became to 3-4.. I where layin in my bed for 1½ hour trying to force my self to sleep just a tiny bit, but unfortunately i was just to damn excited!!   
     
    THE SHOW! First of all a  little confusing with the whole nvidia twitch thing not work as it should d: had especility problem with my 21:9 monitor. so ended up using LinusTech when it came online (Thanks Luke) !
    Yeah nothing much to say about  me stoning in front of a screen for more than 24 hours..  
    I think you guys did a amazing job, especially surprised by the way you and luke keep going with almost no scripting! As for the camera, sound guys and so called "controll center" nice job as well! 

    TWITCH and Twitter blitz ! awesome to get all the peoples insight! I tried and tried, tried some more and tried again to post both Worst computer memory, best allnighter, first allnighter how tired i was. but it where never seen d: bad luck BUT here is some 
     
    "#Mod24 Best Allnighter. this norwegian dude lost a bed to someone, and where contacting ppl on the web to be used as slave for 1 day! i accepted, hosted a lan, got free pizza and a nice footrest for 16 hours !AWESOME !"

    "#Mod24 Worst computer mistake... Changing Ram on my fathers computer when i was 7, burning the whole thing down.. he where a doctor.. so not smart. all data lost !"

    @LinusTech Im at my 35th hour soon. Btw i Live in Denmark (GMT1) I was so exited that i couldn't sleep, after 10 hours work. i sure make it to the 43Hours+ ! i cant miss the WANSHOW ! I love you guys, an what you do.

     
    The Linus twitch channel was just amazing! i have written to some of you guys for 24 hours straight, so amazing. we where 3 or 4 guys giving each other head ups and energy to make it through! TOGETHER WE ARE STRONG Shoutout to @benemus and @DeViLzzz! and good job !

    Wow.. the last few hours was so hard.. i haven't slept for 42 hours in that point of time, i where short of redbulls and had already crossed to daily dose for caffeine pills! My stomach where yelling in pain because all of the bad fast food and soda was burning through my stomach d:  

    I MAD IT TO THE WAN SHOW !!   NICE job everyone ! You can take a look at my other tread for the Pre mod24 preparations  http://linustechtips.com/main/topic/217671-post-your-preparations-for-game24-now/ 

    i have posted some pictures of the aftermath and other random stuff d: 






  18. Like
    Dasizzle got a reaction from alby800 in Mod24(+24) AFTERMATH! My story. Post pictures of your desk or a story!   
    So it begins with me telling my boss "yo i cant come to work 19th of september".  That was fine. but i didn't quite calculated the time zone difference between Me in Denmark (UTC+1) And Game24 (PDT)... So i am practically 9  hours ahead! 
    Okay so i wake up at 08:00 AM 18th (PDT 11PM 17th) Driving to work. Done about 11 hours later. Then i went straight to supermarked to get aaaaaaalll the supplies i could possible need for 24 hours with no sleep!  Redbulls, icetea, soda, candy, frozen pizzas and so on. 
    09:00 PM 18th (PDT 06:00  AM 18) Home again! so i just had to do i few things and then take 5-6 hours sleep before the show. perfect! okay... those things took a little longer so 6 hours became to 3-4.. I where layin in my bed for 1½ hour trying to force my self to sleep just a tiny bit, but unfortunately i was just to damn excited!!   
     
    THE SHOW! First of all a  little confusing with the whole nvidia twitch thing not work as it should d: had especility problem with my 21:9 monitor. so ended up using LinusTech when it came online (Thanks Luke) !
    Yeah nothing much to say about  me stoning in front of a screen for more than 24 hours..  
    I think you guys did a amazing job, especially surprised by the way you and luke keep going with almost no scripting! As for the camera, sound guys and so called "controll center" nice job as well! 

    TWITCH and Twitter blitz ! awesome to get all the peoples insight! I tried and tried, tried some more and tried again to post both Worst computer memory, best allnighter, first allnighter how tired i was. but it where never seen d: bad luck BUT here is some 
     
    "#Mod24 Best Allnighter. this norwegian dude lost a bed to someone, and where contacting ppl on the web to be used as slave for 1 day! i accepted, hosted a lan, got free pizza and a nice footrest for 16 hours !AWESOME !"

    "#Mod24 Worst computer mistake... Changing Ram on my fathers computer when i was 7, burning the whole thing down.. he where a doctor.. so not smart. all data lost !"

    @LinusTech Im at my 35th hour soon. Btw i Live in Denmark (GMT1) I was so exited that i couldn't sleep, after 10 hours work. i sure make it to the 43Hours+ ! i cant miss the WANSHOW ! I love you guys, an what you do.

     
    The Linus twitch channel was just amazing! i have written to some of you guys for 24 hours straight, so amazing. we where 3 or 4 guys giving each other head ups and energy to make it through! TOGETHER WE ARE STRONG Shoutout to @benemus and @DeViLzzz! and good job !

    Wow.. the last few hours was so hard.. i haven't slept for 42 hours in that point of time, i where short of redbulls and had already crossed to daily dose for caffeine pills! My stomach where yelling in pain because all of the bad fast food and soda was burning through my stomach d:  

    I MAD IT TO THE WAN SHOW !!   NICE job everyone ! You can take a look at my other tread for the Pre mod24 preparations  http://linustechtips.com/main/topic/217671-post-your-preparations-for-game24-now/ 

    i have posted some pictures of the aftermath and other random stuff d: 






  19. Like
    Dasizzle reacted to rutwik in Post your preparations for GAME24 Now!   
    I am here from the beginning
  20. Like
    Dasizzle reacted to c3p0 in Post your preparations for GAME24 Now!   
    I'm ready. I'm ready
     

     
    Shit won't load  <_<
  21. Like
    Dasizzle reacted to Swndlr in Post your preparations for GAME24 Now!   
    lotion and tissues, oh yes, lots of tissues.
  22. Like
    Dasizzle got a reaction from SpyRosL in Post your preparations for GAME24 Now!   
    I had to make room for the supplies so the  System Audio Comets when on holiday d: 

    You guys definitely did better than me. Im watching from Denmark, so the show start 03:00 AM here  

    DEDICATION hehe!



  23. Like
    Dasizzle got a reaction from Real_PhillBert in Post your preparations for GAME24 Now!   
    I had to make room for the supplies so the  System Audio Comets when on holiday d: 

    You guys definitely did better than me. Im watching from Denmark, so the show start 03:00 AM here  

    DEDICATION hehe!



  24. Like
    Dasizzle reacted to Trik'Stari in Post your preparations for GAME24 Now!   
  25. Like
    Dasizzle got a reaction from JoaoPRSousa in Post your preparations for GAME24 Now!   
    I had to make room for the supplies so the  System Audio Comets when on holiday d: 

    You guys definitely did better than me. Im watching from Denmark, so the show start 03:00 AM here  

    DEDICATION hehe!



×