Windows SUCKS!

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

cry_monster

Distinguished
May 25, 2010
92
0
18,630
WTF is BSoD event id 100? i have contacted MS support and they have no idea what it is either. i am getting this error abour 30 to 40 times a day and i am literaly seconds from tossing my computer out the window and getting a MAC. my specs are: Asus crosshair formula III MOBO, ASUS EAH5870/G/ 950core 1300mem, AMD 965 4.0ghz, 4gb 1333 talent RAM. i also get this at all stock speeds to. i have reinstalled all my drivers, the whole entire OS and cleaned all my componants, as well as replacing the RAM, and video card. can someone please fix it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


- System

- Provider

[ Name] Microsoft-Windows-Diagnostics-Performance
[ Guid] {CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}

EventID 100

Version 2

Level 1

Task 4002

Opcode 34

Keywords 0x8000000000010000

- TimeCreated

[ SystemTime] 2010-07-29T00:04:50.823824400Z

EventRecordID 1072

- Correlation

[ ActivityID] {00000100-0000-0001-90F0-DB29B12ECB01}

- Execution

[ ProcessID] 1608
[ ThreadID] 5740

Channel Microsoft-Windows-Diagnostics-Performance/Operational

Computer Zachary-PC

- Security

[ UserID] S-1-5-19


 
While this continues to be hilarious, when I look up BSOD and id 100, I get a bunch of results pointing that it's taking Windows too long to load...

Couldn't this be caused by a number of factors? Just saying...why is this specifically Windows? Have you tried the live CD or full install of Linux yet? This would seem to rule out the OS, or point to it more specifically? Have you done the rest of the troubleshooting - only 1 RAM module, etc?

If you aren't willing to try these things and just want to rant about how much you hate Windows, that's fine. If you are actually trying to fix it, you might have to try things, even if you don't think they will work - as a troubleshooter, you actually have to rule things out. If you don't, you'll never know what causes the problems, but will just have your guess.
 
@huron - how right you are. Too many people, when troubleshooting, make assumptions about what the fault is so never bother to test those things that they think can't be at fault (and so never find the cause). You have to apply a methodical approach and test everything. If you knew what the fault was to start with, why bother to test.

@Kewlx25 - the OP has already been asked what further messages there are in the log and several things to try have been suggested. So far he has provided no further info and there is no indication that he has tried any of the things suggested. It looks more and more as if this was just a bit of flamebait from a troll. Either that or he's just too embarrassed to admit that he's screwed his m/b, cpu, or RAM by pushing the overclocking too far.
 
just to end this, i fixed it. non of what you guys posted fixed anything. i went to the M$ store and they reinstalled a new copy of windows 7, (How nice of them) and the problem never occered again. the defect was in the windows disc itself, not my hardware.
 
This won’t change my mind that windows suck unfortunatly. It is still terrible software with tons of bugs. But apple and windows have their ups and downs. Apple has flawless software but at a price that is around 3x more than a PC, and PC has cheap ass broken software for affordable prices. not to mention I have taken MS to small claims court numerous times and winning every case, things like warranty issues, software issues, and there customer support. Unfortunately I have to use MS for my Artificial Intelligence programming, which apple sucks at. But other than that MS is the only flaw with my computer.
 


well at least its working and you didnt have to spend any money.. thats all that matters..
 


The Windows sucks related accusation is always fun and the most legitimate reason to sue M$. This is why they make drugs.


[flash=480,385]http://www.youtube.com/v/oERolxv2Zo8&hl=en_US&fs=1[/flash]
 


im wearing my tin foil hat RIGHT NOW...
 


you just dig yourself deeper every time you talk...

quit while you are ahead-ish
 

Yeah, right. I think your fantasies are beginning to take over. It's pretty clear that there is only one flaw with your computer and you have shown us exactly what it is.

But thanks for the laugh. This has been one of the funniest threads for a long time.
 
That is funny, ijack... I can't see MS wasting their time in small claims court. Besides, MS offers absolutely no warranty on Windows other than the media itself... and that's only if there is a defect out of the box. All other warranty issues are handled by the hardware manufacturers.

well i adjusted the voltage of my ram to standards of 1.501 if this doesnt work i will try 1.6, and if that doesnt work i will be conviced its not the ram. ram checks take to long and last time i did a check there were no problems with it. and besides this is my second set of ram with the same issue so i don think its a ram problem.

But you still didn't check the manufacturer's specs, did you? You just decided to try random voltages without actually checking whether or not they were the correct voltages. I'm not interested in "standard" voltage... I want to know what voltage the manufacturer says is best. The RAM I have, for instance, has a slightly higher spec voltage than what my motherboard provided by default... so I adjusted the voltage accordingly. If you can't be bothered to check such simple things, then the rest of us couldn't be bothered to help you.
 
last I checked, OSX has more bugs than Win7 and OSX only has to work with something closer to tens of hardware configs while Win7 has to work with THOUSANDS, and unlike Win7, Apple has it's fingers in on all hardware for that platform. Microsoft just sets a standard and when someone makes software/hardware that doesn't follow that standard, MS gets blamed.

MS could be better, but they're still pretty decent, well with Win7 anyway. Vista sucked.
 


at the same time M$ doesn't like to follow standards either, look at the open office document standard and how they don't even follow it in Office 2010