I have had this problem frequently and its really got me . I used the Whocrashed program and followed what it said to do and it happened again. This is what it says:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\windows\Minidump
Crash dumps are enabled on your computer.
On Wed 2/27/2013 6:58:51 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022613-26972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0x2A8E9000, 0xFFFFF8801911E1C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 2/27/2013 6:58:51 AM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngAcquireSemaphore+0xD16)
Bugcheck code: 0x3B (0xC0000005, 0x2A8E9000, 0xFFFFF8801911E1C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 2/27/2013 6:03:34 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022613-24258-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0x2B606000, 0xFFFFF8801990FFC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 2/27/2013 5:48:43 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022613-30139-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0x2B449000, 0xFFFFF88019A44FC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 2/27/2013 5:35:22 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022613-28688-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0x97D55000, 0xFFFFF88019A59FC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 2/25/2013 5:44:21 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\022513-32963-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0xC397D000, 0xFFFFF8801A828FC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 2/24/2013 12:00:27 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022313-44475-01.dmp
This was probably caused by the following module: bcmwl63a.sys (bcmwl63a+0x5BFAE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007ABEFAE, 0xFFFFF8801B1C4798, 0xFFFFF8801B1C3FD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\windows\system32\drivers\bcmwl63a.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bcmwl63a.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
bcmwl63a.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
What can I do to fix this problem before I have it wiped out and Win7 installed?
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\windows\Minidump
Crash dumps are enabled on your computer.
On Wed 2/27/2013 6:58:51 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022613-26972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0x2A8E9000, 0xFFFFF8801911E1C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 2/27/2013 6:58:51 AM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngAcquireSemaphore+0xD16)
Bugcheck code: 0x3B (0xC0000005, 0x2A8E9000, 0xFFFFF8801911E1C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 2/27/2013 6:03:34 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022613-24258-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0x2B606000, 0xFFFFF8801990FFC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 2/27/2013 5:48:43 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022613-30139-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0x2B449000, 0xFFFFF88019A44FC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 2/27/2013 5:35:22 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022613-28688-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0x97D55000, 0xFFFFF88019A59FC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 2/25/2013 5:44:21 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\022513-32963-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0xC397D000, 0xFFFFF8801A828FC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 2/24/2013 12:00:27 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022313-44475-01.dmp
This was probably caused by the following module: bcmwl63a.sys (bcmwl63a+0x5BFAE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007ABEFAE, 0xFFFFF8801B1C4798, 0xFFFFF8801B1C3FD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\windows\system32\drivers\bcmwl63a.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bcmwl63a.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
bcmwl63a.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
What can I do to fix this problem before I have it wiped out and Win7 installed?