HELP! PLEASE! My computer keeps crashing and....

I don't know why or what to do!

Here is what happens:

Blue screen comes up with a message saying my PC has ran into a problem and needs to restart. At the bottom it goes on to say if I want to research the problem I can search "System_Service_Exception".

When it reboots I am not connected to the internet. I have to go down to the network icon or whatever in my system tray, right click that, and click on troubleshoot problems. It fixes the problem (as far as being connected the internet goes after restart) saying it was problem with the wireless adapter or access point. That may have computer working for a matter of minutes or hours, but eventually it does the same crap again. Any suggestions?

I just got the darn thing for Christmas, am running Bitdefender and don't do any web browsing other than Ebay, sports and mainstream news sites on this computer. I've run Spybot S&D and got no negative results.

Seems you have two issues:

Blue screen, trouble.

Restart problems.

It will be of little consolation probably but the "ran into trouble" is a frequent occurrence with me too. Just happened again this morning. Often when I am browsing and changing websites.

I too had the problematic and temperamental restart issues after a couple of months on my new computer. Then after a whole flock of updates and some other "cleanup" it straightened up and works fine now with lightning speed.

Culling through the "probably's":

Computers get loaded up with all sorts of stuff from all sorts of brigands and bandits. Hackers, ID thief's, data miners, viruses and on and on.

Win 8 it flighty and temperamental. It has lots of defects not yet fixed. There is rumored a big fix coming.

Win 8 has several trouble shooting and fix features. These could be run. But be a little bit careful with refresh and restore. Some will wipe out your data and some will not.

You can also run the feature that sets your computer back to the pre-trouble era. That usually takes care of the problem.

wetibbe said:

Seems you have two issues:

Blue screen, trouble.

Restart problems.

It will be of little consolation probably but the "ran into trouble" is a frequent occurrence with me too. Just happened again this morning. Often when I am browsing and changing websites.

I too had the problematic and temperamental restart issues after a couple of months on my new computer. Then after a whole flock of updates and some other "cleanup" it straightened up and works fine now with lightning speed.

Culling through the "probably's":

Computers get loaded up with all sorts of stuff from all sorts of brigands and bandits. Hackers, ID thief's, data miners, viruses and on and on.

Win 8 it flighty and temperamental. It has lots of defects not yet fixed. There is rumored a big fix coming.

Win 8 has several trouble shooting and fix features. These could be run. But be a little bit careful with refresh and restore. Some will wipe out your data and some will not.

You can also run the feature that sets your computer back to the pre-trouble era. That usually takes care of the problem.

Click to expand...

Now that I think about it, it does seem to happen while browsing when I change websites. Thanks for all the info; maybe this "big fix" will come along pretty soon.

Anyone think reinstalling or updating the network adapter would help at all? And if so, how do you do that in W8?

To be clear:

Is your computer a laptop or desktop ?

Is it new and under warranty ?

Do you actually have a network with more than 1 computer ?

New laptops and most desktops that are fairly new come with a network card already installed.

To run a "network" a router is required.

In my case I set up a multi computer network and bought Netgear G54/N150 wireless USB Micro Adapters and set up a Netgear WNDR 3400 wireless router. The USB adapter is a plug in with an LED light emitting diode, a little blue light and a set switch. It comes with a mini CD that sets it up. And instructions.

If your network card came factory installed in order to learn what it is you can go to Directx and run an analysis of your system. Once you identify your card you can either call your computers tech support or the network adapters makers tech support for any updates or drivers.

Run DirectX Diagnostic Tool

Here's a free program that can help identify blue screen causes. Click on downloads/free downloads and find the free version of "Who Crashed".
Resplendence Software - WhoCrashed, automatic crash dump analyzer
Jim

otisdog said:

Here's a free program that can help identify blue screen causes. Click on downloads/free downloads and find the free version of "Who Crashed".
Resplendence Software - WhoCrashed, automatic crash dump analyzer
Jim

Click to expand...

Okay, ran the analysis and here is my report. I'm not really computer literate enough to know what it says, but I think it seems to suggest what "wetibbe" suggested by it occurring when switching between websites. I think. Anyone care to translate?


[FONT=Segoe UI, Arial]On Fri 3/1/2013 12:22:21 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\030113-19328-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0x402F000, 0xFFFFF880192D7FC0, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 3/1/2013 12:22:21 PM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k!EngAcquireSemaphore+0xD16)
Bugcheck code: 0x3B (0xC0000005, 0x402F000, 0xFFFFF880192D7FC0, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 3/1/2013 11:25:35 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\030113-19110-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7A040)
Bugcheck code: 0x3B (0xC0000005, 0x5519F000, 0xFFFFF8801829FFC0, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]

---

Conclusion

---

[/FONT]
[FONT=Segoe UI, Arial]3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
[/FONT]

And wettibe and otisdog, thank you for your help!

I'm not good enough to translate but I'm sure one of these other guys can.
Jim

Brian:

The way it all works is that there is a very elaborate, sophisticated, aspect of a computer that has a transition area composed of large numbers of very intricate hardware and in the software there are numerous ways, means, methods, of doing things to make the software command the hardware.


When a problem like yours crops up it can be a corrupted file or a system conflict or both. Each letter or number on the keyboard is an assembly of binary bits which are "switches" that essentially and basically open and close yielding a 1 or a 0.. 8 bits make a byte. When data is transported it moves in packets of units of bytes. Back in the old days it was 16 bits. Then 32. Recently it became 64 bits, like a high way with 2 lanes, then 4 then 8 lanes. 4 lanes of traffic on an 8 lane highway works. 8 lanes of traffic on a 4 lane highways doesn't.

Windows 8 is pretty hostile, and semi compatible, to other older websites, software, and devices. Frequently things just don't work until there are updates to bring the older, or 3rd party, systems into conformity with new windows. The kernel is the transition zone where it happens.

You may have some measure of success here:

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION (Windows Debuggers)