Try this and then Windows 7 ...​bluescreen.

I have downloaded and installed Windows 7 beta 7000 on my PC from Microsoft.com for a few days. Today,I got the bluescreen when doing this below.

Go to the "Windows Color and Appearance". and then Select the Active Title Bar in Item drop-list. Now, type the number 9999....(hold on the number key 9) in Size. You know what will be happenning.

Maybe it's bug of OS or not. Same thing happened in the earlier testing version of Windows 7.

I don't get a BSOD, which error code do you get?

Confirmed blue screen.
I'll bug it if you're not in the beta

PeterF said:

Confirmed blue screen.
I'll bug it if you're not in the beta

What driver is throwing a blue screen on that?

ManipUni said:

PeterF said:

*snip*

What driver is throwing a blue screen on that?

Fun stuff . Instant bugcheck in win32k.sys when typing 99, probably they're missing some sanity check somewhere in the gdi code.

ManipUni said:

PeterF said:

*snip*

What driver is throwing a blue screen on that?

Probably caused by : win32k.sys ( win32k+11e81b )

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600011e81b, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88009d72d60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

MODULE_NAME: win32k

FAULTING_MODULE: fffff8000284b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
win32k+11e81b
fffff960`0011e81b 83a324010000fe  and     dword ptr [rbx+124h],0FFFFFFFEh

WinDbg could not use the correct symbols, but as dexter confirms it does point towards win32k.sys.

It's bugged under https://connect.microsoft.com/windows7/feedback/ViewFeedback.aspx?FeedbackID=396927 in case someone wants to confirm the bug

PeterF said:

Confirmed blue screen.
I'll bug it if you're not in the beta

Is this while not running Aero? I'm running Aero and I'm not getting the bsod.

ZippyV said:

PeterF said:

*snip*

Is this while not running Aero? I'm running Aero and I'm not getting the bsod.

I repro'd it here too while running Aero.  Bugs like this really scare me, GDI really needs to be in user mode. 

ZippyV said:

PeterF said:

*snip*

Is this while not running Aero? I'm running Aero and I'm not getting the bsod.

Aero is running here.

Maybe it's you using a 32bit Windows 7 instead of the 64bit we're using?

PeterF said:

ZippyV said:

*snip*

Aero is running here.

Maybe it's you using a 32bit Windows 7 instead of the 64bit we're using?

Repro'd this on 32-bit here.

PeterF said:

ManipUni said:

*snip*

Probably caused by : win32k.sys ( win32k+11e81b )

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600011e81b, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88009d72d60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

MODULE_NAME: win32k

FAULTING_MODULE: fffff8000284b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
win32k+11e81b
fffff960`0011e81b 83a324010000fe  and     dword ptr [rbx+124h],0FFFFFFFEh

WinDbg could not use the correct symbols, but as dexter confirms it does point towards win32k.sys.

It's bugged under https://connect.microsoft.com/windows7/feedback/ViewFeedback.aspx?FeedbackID=396927 in case someone wants to confirm the bug

I think you marked the bug as private. You can change that by editing it.

ZippyV said:

PeterF said:

*snip*

I think you marked the bug as private. You can change that by editing it.

Done, made public.

BTW, do crashes occur only on nvidia display driver or also on intel/ati/etc

CreamFilling512 said:

ZippyV said:

*snip*

I repro'd it here too while running Aero.  Bugs like this really scare me, GDI really needs to be in user mode. 

Pretty sure that GDI was in user-mode for the original 3.5x design but was moved to kernel-mode for 4.0

If I recall, the reason was that, with the Win95 desktop, UI performance sucked big-time, but was made workable by the move.

I think that this is the white-paper document explaining the move

http://technet.microsoft.com/en-au/library/cc750820.aspx

Not sure if the same perf reasons are valid for modern equipment ??

CreamFilling512 said:

ZippyV said:

*snip*

I repro'd it here too while running Aero.  Bugs like this really scare me, GDI really needs to be in user mode. 

Even if GDI were in user mode (as it was in NT 3.51), a bug like this would still take down the system, as a crash in CSRSS (where GDI and USER were located, according to the whitepaper linked above) will take down the entire system.

elmer said:

CreamFilling512 said:

*snip*

Pretty sure that GDI was in user-mode for the original 3.5x design but was moved to kernel-mode for 4.0

If I recall, the reason was that, with the Win95 desktop, UI performance sucked big-time, but was made workable by the move.

I think that this is the white-paper document explaining the move

http://technet.microsoft.com/en-au/library/cc750820.aspx

Not sure if the same perf reasons are valid for modern equipment ??

Considering back then the standard was 4 MB of RAM and a 486, I'd say yes.

This is strange.