BSOD
I am running W7x64 SP1 and recently downloaded IE9.
This seemed to work well until, using an add-in from Nuance (PDF Create), I tried to create a PDF from a web page. I almost immediately got a BSOD.
I had not tried this on previous versions of IE and I'm loathe to repeate it. Is there anyway of troubleshooting this so as to know for sure what the problem is?
The *.dmp file generated is at
http://cid-8edb73c8a1a37a69.skydrive.live.com/redir.aspx?resid=8EDB73C8A1A37A69!158 and I didn't see references to PDF Create, although I surely could have missed that. There are some known issues with IE9 and Protected Mode and PDF Create,
and I could disable that, but since a BSOD was not mentioned on the Nuance web site, I'd like to see if there's some evidence that this particular add-in was the problem.
Because of a note in the dump file, I did run memtestx86 V4 and had no errors after about 6 hours, which was slightly less than 2 full passes on my 8GB RAM.
Thanks for any help.
Ron
April 9th, 2011 4:20pm
*******************************************************************************
*
*
* Bugcheck Analysis *
*
*
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c6000070, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600010a71f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: win32k
FAULTING_MODULE: fffff80002a49000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2415ea
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffff900c6000070
FAULTING_IP:
win32k+7a71f
fffff960`0010a71f 0fba61700b bt dword ptr [rcx+70h],0Bh
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002a73ca0 to fffff80002ac9640
STACK_TEXT:
fffff880`0810a838 fffff800`02a73ca0 : 00000000`00000050 fffff900`c6000070 00000000`00000000 fffff880`0810a9a0 : nt+0x80640
fffff880`0810a840 00000000`00000050 : fffff900`c6000070 00000000`00000000 fffff880`0810a9a0 00000000`00000002 : nt+0x2aca0
fffff880`0810a848 fffff900`c6000070 : 00000000`00000000 fffff880`0810a9a0 00000000`00000002 fffff900`c6000000 : 0x50
fffff880`0810a850 00000000`00000000 : fffff880`0810a9a0 00000000`00000002 fffff900`c6000000 fffff880`0810aaa8 : 0xfffff900`c6000070
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
win32k+7a71f
fffff960`0010a71f 0fba61700b bt dword ptr [rcx+70h],0Bh
SYMBOL_NAME: win32k+7a71f
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
-----------------------------------------------------------------
The BSOD was caused by win32k.sys.
I recommand that you re-install your Windows.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
April 9th, 2011 5:09pm
On Sat, 9 Apr 2011 21:02:10 +0000, Mr X wrote:
>----------------------------------------------------------------- The BSOD was caused by win32k.sys. I recommand that you re-install your Windows.
I note that your printout of my Dump file is slightly different than what I get. And I wonder about the Process Name and other items outputted by my copy of Windbg, including the comment that it could not
read faulting driver name; and the Process Name of iexplore
=============================
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ron\Desktop\040911-23859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a49000 PsLoadedModuleList = 0xfffff800`02c8ee90
Debug session time: Sat Apr 9 07:21:14.323 2011 (UTC - 4:00)
System Uptime: 1 days 8:52:12.901
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*
*
* Bugcheck Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff900c6000070, 0, fffff9600010a71f, 2}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!GreRestoreDC+23f )
Followup: MachineOwner
---------
1: kd>
1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis *
*
*
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c6000070, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600010a71f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfa0e8
fffff900c6000070
FAULTING_IP:
win32k!GreRestoreDC+23f
fffff960`0010a71f 0fba61700b bt dword ptr [rcx+70h],0Bh
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: iexplore.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800810a9a0 -- (.trap 0xfffff8800810a9a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c21fd2e0 rbx=0000000000000000 rcx=fffff900c6000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600010a71f rsp=fffff8800810ab30 rbp=fffff8800810aca0
r8=0000000000000000 r9=000000000000001f r10=0000000000000000
r11=fffff900c21fd690 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
win32k!GreRestoreDC+0x23f:
fffff960`0010a71f 0fba61700b bt dword ptr [rcx+70h],0Bh ds:ab24:fffff900`c6000070=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a73ca0 to fffff80002ac9640
STACK_TEXT:
fffff880`0810a838 fffff800`02a73ca0 : 00000000`00000050 fffff900`c6000070 00000000`00000000 fffff880`0810a9a0 : nt!KeBugCheckEx
fffff880`0810a840 fffff800`02ac776e : 00000000`00000000 fffff900`c6000070 00000000`0000cc00 fffff900`c00ed010 : nt! ?? ::FNODOBFM::`string'+0x448c6
fffff880`0810a9a0 fffff960`0010a71f : fffff900`c00ed010 fffff900`c21fd2e0 ffffffff`88211447 fffffa80`0ee55060 : nt!KiPageFault+0x16e
fffff880`0810ab30 fffff800`02ac88d3 : ffffffff`e90119ee 00000000`00000001 00000000`00000001 00000000`88211447 : win32k!GreRestoreDC+0x23f
fffff880`0810ac20 00000000`74f62e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0dafea58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74f62e09
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!GreRestoreDC+23f
fffff960`0010a71f 0fba61700b bt dword ptr [rcx+70h],0Bh
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!GreRestoreDC+23f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2415ea
FAILURE_BUCKET_ID: X64_0x50_win32k!GreRestoreDC+23f
BUCKET_ID: X64_0x50_win32k!GreRestoreDC+23f
Followup: MachineOwner
---------
==========================================
Ron
April 9th, 2011 7:29pm
Hi Ron,
From your dump file, I notice
Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA.
This indicates that invalid system memory has been referenced. Also, the crash is caused by
win32k.sys.
I suggesting running
memory diagnose
and check disk for hard drive.
To check disk, please open an elevated CMD windows and run Chkdsk /f /r
In addition, you can run memtest86+ to check the memory.
http://www.techsupportforum.com/2863029-post5.html
Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
If there is no error both in RAM and hard drive, please boot into
Safe Mode to check if the BSOD occurs again. If not, please update all device drivers and BIOS to the latest version and then boot with
Clean Boot to narrow down the issue.
If the issue occurs in Safe Mode again, you need to contact the manufacture to examine the hardware issue.
Regards,
Niki
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
April 15th, 2011 6:03am
On Fri, 15 Apr 2011 10:01:47 +0000, Niki Han wrote:
>
>
>Hi Ron,
>
>From your dump file, I notice Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA.
>This indicates that invalid system memory has been referenced. Also, the crash is caused by win32k.sys.
>\I suggesting running memory diagnose and check disk for hard drive.
>
>To check disk, please open an elevated CMD windows and run Chkdsk /f /r
>In addition, you can run memtest86+ to check the memory.
>
>If there is no error both in RAM and hard drive, please boot into Safe Mode to check if the BSOD occurs again. If not, please update all device drivers and BIOS to the latest version and then boot with Clean Boot to narrow down the issue.
>
>If the issue occurs in Safe Mode again, you need to contact the manufacture to examine the hardware issue.
>
>Niki
>Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Thank you for those suggestions. I had already run memtest86+ V4.0 after seeing the memory error. No errors were found.
I have not run the disk check but I will do that.
The BSOD has not recurred; I suspect a poorly behaved add-in that I tried in IE9 but, since it existed prior to IE9 could well have some incompatibilities. It is PDF Converter Pro 6 from Nuance, and it sometimes does not play nicely. But I
am loathe to try it again as these sudden shutdowns can play havoc sometimes (and I don't really need the feature I tried). Perhaps if I can set up a virtual machine, I can try it out there.
Thanks for looking at this for me.
And I am accessing this via a news reader and have no way of marking a post as an answer.
Ron
April 15th, 2011 6:58am
Ron,
I have version 7 of Nuance PDF Converter Pro installed on two Windows 7 X64 SP1 machines and observed that under IE 9 the web-browser plug-in for creating PDFs from the toolbar generated an immediate BSOD on both. Reverting back to IE 8 solved the issue
on both, as well.
I've found a few indications from others reporting that they are experiencing similar issues with this.
The error I observed in both cases was an APC_INDEX_MISMATCH.
-afh3
Free Windows Admin Tool Kit Click here and download it now
April 15th, 2011 1:04pm
On Fri, 15 Apr 2011 17:02:50 +0000, afh3 wrote:
>
>
>Ron,
>
>I have version 7 of Nuance PDF Converter Pro installed on two Windows 7 X64 SP1 machines and observed that under IE 9 the web-browser plug-in for creating PDFs from the toolbar generated an immediate BSOD on both. Reverting back to IE 8 solved the
issue on both, as well.
>
>I've found a few indications from others reporting that they are experiencing similar issues with this.
>
>The error I observed in both cases was an APC_INDEX_MISMATCH.
>
>-afh3
Thank you for that information. If I upgrade from 6 to 7, I will know not to expect that plug-in to work :-(
Ron
April 15th, 2011 4:57pm
On Fri, 15 Apr 2011 17:02:50 +0000, afh3 wrote:
>
>
>Ron,
>
>I have version 7 of Nuance PDF Converter Pro installed on two Windows 7 X64 SP1 machines and observed that under IE 9 the web-browser plug-in for creating PDFs from the toolbar generated an immediate BSOD on both. Reverting back to IE 8 solved the
issue on both, as well.
>
>I've found a few indications from others reporting that they are experiencing similar issues with this.
>
>The error I observed in both cases was an APC_INDEX_MISMATCH.
>
>-afh3
afh3,
I have noted a problem in PDF Pro V6 that I wonder if you could see if it is present in V7.
In V6, there is a problem if one tries to open a PDF Portfolio and also has newer versions of Adobe Flash. This problem is corrected (according to Nuance) by substituting an update PlusCore.dll file in the appropriate folder. That works.
BUT, once I've done that, if I open a regular PDF file, and try to move a page around by selecting it from the Pages Thumbnails, and dragging it, the program crashes. (If I put back the original PlusCore.dll file, the pages drag OK, but I can't open
the portfolio).
Since I can no longer get free support from Nuance, I'm not sure what to do.
Ron
Free Windows Admin Tool Kit Click here and download it now
April 19th, 2011 8:35am
Ron,
I am able to create and open PDF Portfolios with PDF Converter Professional 7.0, with Adobe Flash version 10.2.159.1 installed.
Reordering pages in PDF documents works properly as well. I've made no changes to any dll files relevant to any Adobe products.
Hope that helps.
Now, if they would just fix the browser integration so that it worked in Internet Explorer 9...
-afh3
April 26th, 2011 12:19am
On Tue, 26 Apr 2011 04:17:24 +0000, afh3 wrote:
>
>
>Ron,
>
>I am able to create and open PDF Portfolios with PDF Converter Professional 7.0, with Adobe Flash version 10.2.159.1 installed.
>
>Reordering pages in PDF documents works properly as well. I've made no changes to any dll files relevant to any Adobe products.
>
>Hope that helps.
>
>Now, if they would just fix the browser integration so that it worked in Internet Explorer 9...
>
>-afh3
Well, that information is useful. Thank you.
Hopefully, one of these days I'll be able to upgrade my Enterprise version. I have V6 but They don't seem to want to sell V7 it to individuals (unless you buy at least five seats), and I need the redaction capability that is not in the non-Enterprise
version.
So far as the "integration" is concerned, I wouldn't hold my breath. Maybe in V8, after IE 11 comes out :-(. I've never used that feature though, always just printing to the PDF Printer that PDF Pro installs.
Ron
Free Windows Admin Tool Kit Click here and download it now
April 26th, 2011 6:27am