Am I the only person getting 058?

Installed Win7 last night (64-bit). Everything was going okay. Went to idle in my GH while I took a shower, came back right when my PC decided to BSOD (apparently Win7 tends to not like GW and this can be very erratic and unpredictable, yes?). Whatever...

Restart. Launch GW. Code 058 out the ass, everything else works. I've incorporated port forwards and exceptions for the GW.exe client but the problem persists. Disabled the default Windows firewall, problem persists. Shut off NOD32, problem persists.

I'm leaning more towards the idea it may because it's event time and that's when an absurd amount of people get unpredictable lag-outs, kicks, drops, and errors.

So please, give me some solace and tell me I'm not the only one experiencing this.

UPDATE:
After a bit more reading and specifically directing myself to the NCSoft website, it appears shutting down NOD32 wasn't good enough, and it actually required reconfiguring of the IMON to prevent it from scanning port 80, which the GW client uses to communicate. Fixed, working now, feel free to close!

I haven't had a problem with my Win7 Ultimate and GW crashing. Good thing you opened the port. I was about to suggest that.

I had faulty RAM and so i'd get BSOD's while playing any game for a long time, but once I got new sticks everything was fine and I haven't received a blue screen yet. Run memtest86+ or prime95 and see if they come up with errors.

I did so on the Windows firewall and my router firewall. When it didn't work, I closed NOD32, but apparently closing it isn't good enough because it leaves a footprint in the background and keeps working. But only on NCSoft support, did they mention issues with NOD32's IMON.

RAM is fine, the only BSODs I would ever get on Vista is when I unintentionally RED ENGINE GORED ENGINE GORED ENGINE GORED ENGINE GOed my graphics card drivers up in attempt to overclock. I didn't know what caused the BSOD I had until I came here and looked a few threads down, and other people have the same problem (Win7+GW, and keywords from my OP: erratic and unpredictable).

Either way...

Per request... Closed