OpenGL "lost connection" error code 7

1. Please attach the full output of the development console tab.
2. Does MCL-131 describe your issue?

1. Will post full output asap.
2. MCL 131 is not similar at all
My last comment "Minecraft is unplayable" was technically hyperbole.
The game will crash after 2minutes, 10 minutes or 25 minutes of gameplay; my minecraft sessions almost always end with a crash making it too frustrating to play.

I had the default JVM arguments when this first happened with 1.6 (it has happened with older versions but I think 1.5.2 it didnt).
I changed to -Xincgc -Xms1G -Xmx3G and still had the same problem;
now I'm trying -Xincgc -Xms2G -Xmx2G
Maybe a static size will help. This is just a hunch that its java memory issues causing a delay in dealing with video drivers which then timeout.

Its really hard to diagnose since it can happen over and over every 2 or 3 mins, or not happen for half an hour or longer. It didnt happen just now for instance when I tried to get a console output.

I have same/similar crashes (1.6.1 and 1.6.2) occurring seemingly randomly 2 to 20 minutes after starting. I have tried everything I can think of to correct the problem: tried various video drivers (the most current and older ones as they worked with previous MC versions); updated java, tried both 32 and 64 bit versions; as the OpenGL error references a Windows time-out limit error I tried lowering all of the video intensive options in MC (again still got errors).

One thing I noticed, I am getting a lot of particle ghosting when mining (leaves, wood, stone or dirt), and I don't recall seeing this in the previous versions of MC. So I am wondering if in the new 1.6 version there are new/additional video stuff that is causing a greater strain on the video cards?

I am also often (but not always) getting the following launcher messages near the time of crash:
Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
Client> [SERVER] [WARNING] Can't keep up! Did the system time change, or is the server overloaded?

Specs:
Win 7 Home (6.1, amd64)
Java 1.7.0_25 (64 bit)
Nvidia GT 540M (320.49) [tried 310.70, 314.07. and 314.22]

Played for ~1 hour with no crash, then played for ~16 minutes and experienced the crash.
At the time of crash I was feeding animals, about 20 pigs, cows chickens and a few sheep in a 25x25 pen during day, no rain.
When minecraft crashed it also crashed my audioplayer (media monkey)

Second dev console.
I've had less crashes since changing to 2Gig min-max java memory but that might be just random chance.

This time the fps seemed to be taking some hits shortly before the crash.
It crashed almost immediately after unpausing the game.
I had firefox open in the background playing a youtube vid, firefox didnt have to quit, though it usually does even it was pretty much doing nothing on a static web page.

Getting this error in the console every two seconds: [18:58:54 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102

When quitting a world in 14w21b, the following is outputted to the console:
[19:18:27 INFO]: Client> [19:18:27] [Server thread/INFO]: Stopping server
[19:18:27 INFO]: Client> [19:18:27] [Server thread/INFO]: Saving players
[19:18:27 INFO]: Client> [19:18:27] [Server thread/INFO]: Saving worlds
[19:18:27 INFO]: Client> [19:18:27] [Server thread/INFO]: Saving chunks for level 'Whil E. Coyote'/Overworld
[19:18:27 INFO]: Client> [19:18:27] [Server thread/INFO]: Saving chunks for level 'Whil E. Coyote'/Nether
[19:18:27 INFO]: Client> [19:18:27] [Server thread/INFO]: Saving chunks for level 'Whil E. Coyote'/The End
[19:18:36 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:36 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:38 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:42 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:44 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:46 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:48 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:50 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:52 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:54 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:56 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:18:58 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:19:00 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:19:02 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:19:04 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[22:19:06 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[10:36:50 INFO]: Client> AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102

This also happens me after closing a singleplayer world. I also get an OpenGL error sometimes, and my Minecraft freezes. Could a mod reopen this?

AL lib (Audio) has nothing to do with OpenGL (Graphics).

True, but I'm also getting that AL lib error.