Hello JacquieDV,
I'll see what I can do to help, hopefully we won't be seeing much of each other in the near future as we should have solved your problem.
Lets begin.
Code:
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: fc8e68c8, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: a0938cae, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Invalid system memory was referenced, so we know why the crashed happened but what caused it?
Lets look at the callstack.
Code:
e9e90a90 83878ad4 00000000 fc8e68c8 00000000 nt!MmAccessFault+0x157
e9e90a90 a0938cae 00000000 fc8e68c8 00000000 nt!KiTrap0E+0xdc
e9e90b28 a0938bd5 fcb74848 e9e90b7c e9e90b44 win32k!ttfdCloseFontContext+0x16
e9e90b38 a0938bfb fb297cf0 e9e90b60 a0938c74 win32k!ttfdDestroyFont+0x16
e9e90b44 a0938c74 fb297cf0 fc879cf0 e9e90bb8 win32k!ttfdSemDestroyFont+0x18
e9e90b60 a0938998 fb297cf0 fc879cf0 fc82dcf0 win32k!PDEVOBJ::DestroyFont+0x65
e9e90b84 a08fac21 00000000 00000000 00000001 win32k!RFONTOBJ::vDeleteRFONT+0x33
e9e90bbc a08fada2 e9e90be0 00000000 fe4579d8 win32k!vRestartKillRFONTList+0x7b
e9e90bf0 a08afcd7 00000003 fe4579d8 00000000 win32k!PFTOBJ::bUnloadWorkhorse+0x115
e9e90c1c a08af8d9 fc8dbb98 00000000 00000000 win32k!vCleanupPrivateFonts+0x4d
e9e90c34 a08ac06e fc8dbb98 00000000 00000000 win32k!NtGdiCloseProcess+0x16c
e9e90c54 a08abbad fc8dbb98 00000000 8a7651b0 win32k!GdiProcessCallout+0x145
e9e90c70 83a2a5ee 8ab18510 00000000 f05a4f6c win32k!W32pProcessCallout+0x5d
e9e90cdc 839ddf83 00000000 b41379b0 b4137a01 nt!PspExitThread+0x4a0
e9e90cf4 83898142 864556d8 e9e90d20 e9e90d2c nt!PsExitSpecialApc+0x22
e9e90d4c 83875a32 00000001 00000000 e9e90d64 nt!KiDeliverApc+0x1dc
e9e90d4c 77555d14 00000001 00000000 e9e90d64 nt!KiServiceExit+0x56
WARNING: Frame IP not in any known module. Following frames may be wrong.
04d2fce4 00000000 00000000 00000000 00000000 0x77555d14
Win32k.sys is running a lot of routines related to the graphics device interface and deleting fonts, we then reference memory which wasn't present so we generate a page fault, the memory didn't exist so we crash.
So lets look at the other crashes.
Code:
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fdd74d08, memory referenced
Arg2: 00000000, value 0 = read operation, 1 = write operation
Arg3: 816b7691, if non-zero, the address which referenced memory.
Arg4: 00000000, (reserved)
A driver referenced memory which was already freed, as stated this isn't allowed and cannot be dismissed so we bugcheck.
Code:
1: kd> dc fdd74d08
fdd74d08 ???????? ???????? ???????? ???????? ????????????????
fdd74d18 ???????? ???????? ???????? ???????? ????????????????
fdd74d28 ???????? ???????? ???????? ???????? ????????????????
fdd74d38 ???????? ???????? ???????? ???????? ????????????????
fdd74d48 ???????? ???????? ???????? ???????? ????????????????
fdd74d58 ???????? ???????? ???????? ???????? ????????????????
fdd74d68 ???????? ???????? ???????? ???????? ????????????????
fdd74d78 ???????? ???????? ???????? ???????? ????????????????
We can see that the memory was indeed freed as there is nothing in the page because it was scrubbed clean waiting for another driver to allocate the memory.
Do note that there is a difference between simply accessing freed memory and allocating memory, memory needs to be allocated before being accessed.
Code:
dbd80a58 8389aad4 00000000 fdd74d08 00000000 nt!MmAccessFault+0x157
dbd80a58 816b7691 00000000 fdd74d08 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
dbd80ae0 5ab7f1df 8160bf33 dbd80b7c fcdcd838 ATMFD+0x7691
dbd80b14 816b40ae 5ab7f18f 8160bf33 dbd80b7c 0x5ab7f1df
dbd80b44 81588c74 fcdcd838 fb111a60 dbd80bb8 ATMFD+0x40ae
dbd80b60 81588998 fcdcd838 fb111a60 fb15fa60 win32k!PDEVOBJ::DestroyFont+0x65
dbd80b84 8154ac21 00000000 00000000 00000001 win32k!RFONTOBJ::vDeleteRFONT+0x33
dbd80bbc 8154ada2 dbd80be0 00000000 fd33acd0 win32k!vRestartKillRFONTList+0x7b
dbd80bf0 814ffcd7 0000000c fd33acd0 00000000 win32k!PFTOBJ::bUnloadWorkhorse+0x115
dbd80c1c 814ff8d9 fb27f8a8 00000000 00000000 win32k!vCleanupPrivateFonts+0x4d
dbd80c34 814fc06e fb27f8a8 00000000 00000000 win32k!NtGdiCloseProcess+0x16c
dbd80c54 814fbbad fb27f8a8 00000000 82c77728 win32k!GdiProcessCallout+0x145
dbd80c70 83a4c5ee 8b4dfb20 00000000 e3308985 win32k!W32pProcessCallout+0x5d
dbd80cdc 839fff83 00000000 91a47270 91a47201 nt!PspExitThread+0x4a0
dbd80cf4 838ba142 89ed2348 dbd80d20 dbd80d2c nt!PsExitSpecialApc+0x22
dbd80d4c 83897a32 00000001 00000000 dbd80d64 nt!KiDeliverApc+0x1dc
dbd80d4c 77055d14 00000001 00000000 dbd80d64 nt!KiServiceExit+0x56
04edf6e4 00000000 00000000 00000000 00000000 0x77055d14
I'm starting to notice a consistency, aren't you?
This is good as consistency is a lot easier then any inconsistencies as we can narrow it down.
You have two more bugchecks which are both Kernel mode exceptions that weren't handled, they have the same callstacks.
Here are my suggestions.
1. If you're having these crashes when using Adobe PDF documents then this hotfix should solve the issue.
Adobe PDF Font Hotfix
2. Your font cache might be corrupt, delete FNTCACHE.dat located in this directory and restart your computer.
Code:
C:\Windows\System32\FNTCACHE.DAT
3. Win32k.sys is responsible for creating the link between the Graphics Device Interface and the device driver as well as fonts and other display functions, therefore your display driver may be causing or contributing to these problems.
Code:
0: kd> lmvm atikmdag
start end module name
92003000 9272f000 atikmdag (deferred)
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Wed Oct 25 02:53:03 2006 (453EC37F)
CheckSum: 00205904
ImageSize: 0072C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your AMD display driver is nearly
8 years old!
I've never seen a display driver that old, it wouldn't suprise me one bit if that is causing these problems.
Download and install the latest driver
here for your
ATI Radeon X1300PRO GPU.
4. Your BIOs dates back to 2007 which is very old, I recommend you update it. You will need to use a flash drive and put the BIOS update on it, boot into the BIOS and select something along the lines of 'Flash BIOS' or 'Update BIOS'.
DO NOT interrupt the BIOS update, don't turn off the computer or say hello to your new giant motherboard paperweight as it will become useless.
Any issues post back and let me know.
