BSOD thanks to win32k.sys - Any ideas?

stormrocker · 01 Aug 2013

Hi guys,

i am getting now the 10th BSOD after using my notebook for standard for writing emails (outlook 2013, reading PDFs with Adobe and writing messages with lync 2013.
I haven't installed any new software and i haven't change the hardware.
I already have run the Windows memory Diagnose Tool without finding any errors.

Could you help me with finding the reason for these annoying interruptions?

Thanks a lot
Stormrocker

stormrocker · 01 Aug 2013

I was too fast zipping the SF File...

x BlueRobot · 01 Aug 2013

Code:

BugCheck 50, {fffff900c3cae000, 1, fffff96000072364, 0}

Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!sfac_GetLongGlyphIDs+84 )

Code:

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

This bugcheck that a device driver has referenced a invalid memory address, and attempted to cause a page fault in a non paged pool region of memory.

Code:

0: kd> !thread
GetPointerFromAddress: unable to read from fffff800032b4000
THREAD fffffa80161f8b50  Cid 2054.21b4  Teb: 000000007efdb000 Win32Thread: fffff900c23555d0 RUNNING on processor 0
IRP List:
    Unable to read nt!_IRP @ fffffa80167d0b40
Not impersonating
GetUlongFromAddress: unable to read from fffff800031f3bcc
Owning Process            fffffa800cfeab30       Image:         <Unknown>
Attached Process          fffffa8013ea3b30       Image:         csrss.exe
fffff78000000000: Unable to get shared data
Wait Start TickCount      2801075      
Context Switch Count      325526         IdealProcessor: 0                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x0000000000b81ca0
Stack Init fffff88010c42190 Current fffff88010c41750
Base fffff88010c43000 Limit fffff88010c34000 Call fffff88010c421e0
Priority 10 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5

There seems to be some IRPs associated with this thread, which would indicate more of a driver related cause.

--------------------------------------------------------------------

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

Driver Verifier - Enable and Disable

Information

Additional Help - Using Driver Verifier to identify issues with Drivers

Remove:

Code:

Start Menu\Programs\DAEMON Tools Lite

Arc said:

Download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

Double click to open it.
Click this button only:
If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Daemon Tools uses a driver called sptd.sys, which is known to cause BSODs with Windows 7. It is recommend you remove this program, and use Windows own in-built features or ImgBurn.

Remove:

Code:

Start Menu\Programs\McAfee

McAfee is a well known cause for BSODs, please remove the program completely using the McAfee Removal Tool, and then install and run full scans with these free and proven alternatives which work best with the operating system due to compatibility and lightweight nature on system resources.

Install and perform full scans with:

Information

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:

Good and Free system security combination.

Reduce the number of programs at startup, to avoid any driver or program conflicts:

Only the basic drivers and AV program will need to be enabled at start up.