Error 132... [Resolved!]

[meepitco]

I know this topic has probably been posted 12128513957124871058141025t4-2513510 times. But, this is seriously screwing me up. I have the beta completely 100% downloaded, and, I am still getting this error.
I'm also using Direct9 (I THINK that's what it's called), and windowed mode.
These are my computer graphic, stuff things:
OPERATING SYSTEM:
Windows 2.6.1.7600
CPU TYPE:
Intel® Celeron® CPU 900 @ 2.20GHz
CPU SPEED:
2.21 GHz
SYSTEM MEMORY:
1.93 GB
VIDEO CARD MODEL:
Mobile Intel(R) 4 Series Express Chipset Family
VIDEO CARD MEMORY:
797 MB
VIDEO CARD DRIVER:
igdumdx32.dll
DESKTOP RESOLUTION:
1366x768
HARD DISK SIZE:
220.4 GB
HARD DISK FREE SPACE:
41.95 GB (19%)
DOWNLOAD SPEED:
475 (3.8 kbps)

I have no damn clue on if this is right, or not. I'm figuring it's my computer, since this is probably the worst damn computer known to man (2009 Compaq laptop, Presario CQ60)

If anyone could help me, that would be lovely.
Thank you, or my apologies ahead of time.
---------------
Update: I ended up finding out what was wrong, thank you all for the help.

[Kayb]

Don't stress too much, I'd say more than half of beta players are having this issue. Blizzard are aware of it and are working to fix it. Give it another day or so and it should be right.

[CrystalKitten]

it's just an issue with the beta client. I know there's a LOT of posts about it on the official beta forums. They were requesting more info, but apparently there's MANY error 132s, and they can have a large variety of causes, so you need to send them the exact error (from the log) and your system info.

What I do know, is that I got FAR fewer crashes if I was in less populated areas. If I was near other players, I would end up crashing every 5 minutes.

[meepitco]

Ahh, but, I cant even launch the start up screen (not loader, the actual game) without crashing :/

I'm glad, it's not my computer though..

[CrystalKitten]

Well, it could still be your computer. Apparently some graphics cards are no longer supported, that sort of thing. I'd suggest you head over to the official forums and read the blizzard posts on error 132. I saw one blue post that said sometimes, error 132 is a graphics card/driver issue.

[meepitco]

Well, I finally got this resolved. All I had to do was update my drivers, and done! I'm on the beta
Why I didn't think of that, is going to stick with me forever though ._.