BSOD occuring alot lately , 0x00000019 and 0x00000050 , read more

Sneakyguydavid · 14 Nov 2012

hello thank you for reading for reading this . im having a a lot of bsod's occur lately usually when im in a web browser.

I checked memtest+86 , ram is good .

I ran chkdsk /f and chkdsk /r .

I deleted avast to see if it was my antivirus , since I had both avast and anti malwarebytes (probally not the problem though)

I ran a antivirus check , found like 3 little things that didn't seem connected to the problem , delete them anyways .

and from what I can see , the BSOD's occur when im in Any web browser .

im on from my pc right now trying to push my luck , no BSOD's as of last boot up.

I linked the files of the raw crash files , I apologize as I don't have the debugging tools , my pc would crash before I can download them from the Microsoft website .

please help , and thank you.

(P.S.) I included my system spec on my profile if it is necessary .

Arc · 14 Nov 2012

Welcome aboard.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c39bc000, 1, fffff96000072374, 0}


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

Followup: MachineOwner
---------

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff900c01cd460, fffff900c01cd4b0, 2505000f}

Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff900c01cd460, The pool entry we were looking for within the page.
Arg3: fffff900c01cd4b0, The next pool entry.
Arg4: 000000002505000f, (reserved)

Debugging Details:
------------------


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800028b6100
GetUlongFromAddress: unable to read from fffff800028b61c0
 fffff900c01cd460 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800027b1cae to fffff80002686fc0

STACK_TEXT:  
fffff880`09ad1e98 fffff800`027b1cae : 00000000`00000019 00000000`00000020 fffff900`c01cd460 fffff900`c01cd4b0 : nt!KeBugCheckEx
fffff880`09ad1ea0 fffff960`000b9415 : fffff880`09ad2000 00000000`00000000 fffff880`64667454 00000000`01fe4a44 : nt!ExDeferredFreePool+0x12da
fffff880`09ad1f50 fffff960`000c1e2e : 00000000`01fe4a44 fffff880`09ad2000 00000000`00000000 00000000`01fe080b : win32k!EngFreeMem+0x21
fffff880`09ad1f80 fffff960`000b915b : fffff900`c013f9e0 00000000`00000001 00000000`00000001 00000000`00000000 : win32k!bLoadGlyphSet+0x146
fffff880`09ad1fb0 fffff960`000b92fa : fffff900`c013f9e0 fffff900`00000001 fffff900`c013f9e0 fffff960`0022b2e4 : win32k!bReloadGlyphSet+0x24b
fffff880`09ad2670 fffff960`000b9252 : 00000000`00000000 fffff900`c013f9e0 fffff900`00000001 fffff900`c1af2e94 : win32k!ttfdQueryFontTree+0x66
fffff880`09ad26c0 fffff960`00105f63 : fffff960`000b91f8 fffff900`c013fd20 00000000`00000001 00000000`00000000 : win32k!ttfdSemQueryFontTree+0x5a
fffff880`09ad2700 fffff960`00105e0f : fffff880`09ad2810 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!PDEVOBJ::QueryFontTree+0x63
fffff880`09ad2780 fffff960`000c0046 : fffff900`c0091000 00000000`00000000 00000000`00000002 00000000`00000000 : win32k!PFEOBJ::pfdg+0xa3
fffff880`09ad27e0 fffff960`0011a578 : fffff900`c1af2d80 fffff880`09ad2a70 fffff880`09ad2970 fffff880`09ad2a40 : win32k!RFONTOBJ::bRealizeFont+0x46
fffff880`09ad2900 fffff960`000bc010 : 00000000`10018000 fffff900`00000000 00000000`00000000 00000000`00000002 : win32k!RFONTOBJ::bInit+0x548
fffff880`09ad2a20 fffff960`000c6f93 : 00000000`00000000 fffff960`000c6f74 00000000`00000000 00000000`00000000 : win32k!GreGetTextMetricsW+0x4c
fffff880`09ad2a60 fffff800`02686253 : 00000000`00000044 00000000`076a03c0 00000000`7ef7a000 00000000`7ef7a000 : win32k!NtGdiGetTextMetricsW+0x1f
fffff880`09ad2ae0 00000000`750a2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`031fede8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x750a2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!EngFreeMem+21
fffff960`000b9415 4883c420        add     rsp,20h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  win32k!EngFreeMem+21

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5006fd0d

FAILURE_BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21

BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21

Followup: MachineOwner
---------

In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Also upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

Let us know the results, with the subsequent crash dumps, if any.

Sneakyguydavid · 14 Nov 2012

thanks so much I uploaded the MSINFO32.nfo to this reply and I enabled driver verifier to all drivers except Microsoft drivers like the thread said , after 24 hours of usage , ill upload all of my dumps .

Sneakyguydavid · 14 Nov 2012

my computer wont even boot anymore , it freezes at the welcome screen , if it gets past the welcome screen it still only shows my wallpaper and taskbar , no icons and it freezes , cant move mouse or anything .

Arc · 14 Nov 2012

Boot into safe mode. Disable driver verifier. Then boot normally again, uninstall Daemon Tools.

Reboot again, and give it some time. Is it crashing anymore? If not, wait for even more time. If crashes, enable verifier again. Follow the steps of the tutorial very minutely, making it sure that you are following the steps perfectly, and not selecting any of the microsoft's drivers.

BTW, You use MBAM pro? When you last updated the version (not virus definition) for the last time?

Sneakyguydavid · 14 Nov 2012

ok turning off verifier allowed my pc to built , uhmm i havnt updated malwarebytes in a while, the database updated like 2-3 days ago . oh i also uninstalled daemon tools , i didnt have the sptd installed though i heard that causes problems , since i didnt need it i didnt install it during installation

Sneakyguydavid · 14 Nov 2012

still crashing , and crashing still only happens while im browsing on the internet .

Arc · 14 Nov 2012

Enable verifier again ....
Follow it carefully

Driver Verifier - Enable and Disable

Then upload the crash dumps with verifier enabled.

Sneakyguydavid · 14 Nov 2012

ok i selected everything EXCEPT microsoft drivers , im gonna restart and tell you if it freezes at welcome screen again .

Sneakyguydavid · 14 Nov 2012

froze again , before i can even log on this time , i went to safe mode , disabled , and i took 2 pictures of all the options i can choose to verify .

right under the malwarebytes on picture 2 is where the microsoft drivers start.

(since i know not to verify microsoft drivers i didnt show them in the pictures , both pictures show all my options except like 1 or 2 realtek drivers which i did click to verify)