BSOD - System Service Exception

Joined
Jul 26, 2012
Messages
1
Reaction score
0
When I start my computer and before my log on screen shows this blue screen appears and restarts my computer. I have no idea as to what is happening. Help me!!

Windows 7 Professional SP1
Processor: AMD Athlon(tm) 7750 Dual-Core Processor 2.70 GHz
(RAM): 6 GB
System type 64-bit OS
 

Attachments

Last edited:

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,134
Reaction score
252
Welcome to the W7 Forum.

I hope that we can help to resolve your problem.

Looking at the crash dump it is probably a out of date video driver.

Are you able to login to your computer at all?

If not start the computer in safe mode and remove the video drivers. Reboot.
The screen may be ugly because it will be VGA but at least it shouldn't crash. Then download your drivers.


FOLLOWUP_IP:
win32k!InternalGetRealClientRect+f
fffff960`000be5e7 0fb74142 movzx eax,word ptr [rcx+42h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!InternalGetRealClientRect+f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4fb1b20d

STACK_COMMAND: .cxr 0xfffff8800388cd70 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!InternalGetRealClientRect+f

BUCKET_ID: X64_0x3B_win32k!InternalGetRealClientRect+f

Followup: MachineOwner
If you have any questions, please don't hesitate to ask.

Hope this helps.
 
Joined
Jun 4, 2012
Messages
109
Reaction score
7
To shintaro
Why graphics cards and drivers cause so much BSODs in windows.
 

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,134
Reaction score
252
There are just so many things that can go wrong.
History.
Way back in Win NT 4.0 they, (Microsoft), decided to move the GDI (Graphic Device Interface) in to the Kernel space (Ring 0) for performance reasons. When the GDI wasn't in the Kernel space it wouldn't crash the complete system. So you might lose the display but the server would keep running. And you could reboot the server at a more convenient time via other means.

Now, however, because the GDI is in the kernel, if the developer messes up in writing the KMD (Kernel Mode Driver) it brings the whole system down. BTW writing a solid it no trival task. It takes years of work to get it right.

Some examples:
A User has video driver Ver. 1 on their computer, but the game developers tested their game with the new video driver Ver. 2, which has some fix(s) in it. So when the user play's the game, Bingo! crash!

Also a (imaginary in this example) fix might only relate to users with 2 Gb of RAM or more. So the majority of users will never have a problem, BUT, as time goes by, technology changes and the user adds RAM. So now the game access RAM above the 2Gb range, Bingo! crash. The user is left sctratching their head, thinking, I just added RAM and now my super cool game crashes? It should be running better?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top