🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

5 total messages Started by Emily_Waters Thu, 12 Mar 2009 14:07
Reader 9 causes BSOD on Windows XP Pro
#599
Author: Emily_Waters
Date: Thu, 12 Mar 2009 14:07
11 lines
1140 bytes
We have a few systems here that are having real problems with Adobe Reader 9. When the users attempt to open a .pdf file, they get a BSOD, and the system reboots. Once the system comes back up, they are able to open the offending file with no problems.

Here are details of our systems:
Dell Optiplex 755
Windows XP Pro SP3
2GB Ram
32 Bit OS

I have found this occurs most often when opening pdf's that were created with earlier versions.

I'm sure I have left out some vital piece of information, so if you need clarification on something, please ask. Any suggestions would be greatly appreciated!
Re: Reader 9 causes BSOD on Windows XP Pro
#602
Author: Michael Kazlow
Date: Thu, 12 Mar 2009 15:12
4 lines
752 bytes
The BSOD is caused by driver problems. Try updating the drivers to your 
hardware.

Mike
Re: Reader 9 causes BSOD on Windows XP Pro
#629
Author: Pat_Willener
Date: Fri, 13 Mar 2009 03:50
8 lines
796 bytes

      I'm sure I have left out some vital piece of information...




Yes, what is the error code on the BSOD, and if possible the module name that caused the BSOD; that would give us some clues what's wrong.
Re: Reader 9 causes BSOD on Windows XP Pro
#637
Author: Emily_Waters
Date: Fri, 13 Mar 2009 13:57
74 lines
3147 bytes
I ran a dumpchk, and the output is below. I will freely admit that the data presented is beyond my understanding. Does this information provide you with the data you need to assist? Thank you!

C:\Program Files\Support Tools>dumpchk -3 c:\Mini031109-01.dmp
Loading dump file c:\Mini031109-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0ad40500
PfnDataBase 81086000
PsLoadedModuleList 8055d720
PsActiveProcessHead 805638b8
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 1000007e
BugCheckParameter1 c0000005
BugCheckParameter2 bfc34800
BugCheckParameter3 adac250c
BugCheckParameter4 adac2208
PaeEnabled 00000001
KdDebuggerDataBlock 8054d2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000300
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000a90
DriverListOffset 000036a0
DriverCount 00000085
StringPoolOffset 00005e20
StringPoolSize 00001270
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack adac2570
DebuggerDataOffset 00003410
DebuggerDataSize 00000290
DataBlocksOffset 00007090
DataBlocksCount 00000006

Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Mar 11 15:50:41 2009
System Uptime: 0 days 2:18:26
start end module name
804d7000 806e4000 nt Checksum: 001FBC56 Timestamp: Thu
33:13 2008 (48A3FBD9)

Unloaded modules:
aa3a9000 aa3d4000 kmixer.sys Timestamp: unavailable (00000000)
aa3a9000 aa3d4000 kmixer.sys Timestamp: unavailable (00000000)
aab0b000 aab36000 kmixer.sys Timestamp: unavailable (00000000)
bafaa000 bafab000 drmkaud.sys Timestamp: unavailable (00000000)
baa48000 baa55000 DMusic.sys Timestamp: unavailable (00000000)
aab36000 aab59000 aec.sys Timestamp: unavailable (00000000)
ab33a000 ab348000 swmidi.sys Timestamp: unavailable (00000000)
bae4c000 bae4e000 splitter.sys Timestamp: unavailable (00000000)
add8a000 add9f000 naveng.sys Timestamp: unavailable (00000000)
add9f000 ade74000 navex15.sys Timestamp: unavailable (00000000)
bab08000 bab15000 i8042prt.SYS Timestamp: unavailable (00000000)
bac08000 bac0d000 Cdaudio.SYS Timestamp: unavailable (00000000)
ba5a1000 ba5a4000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check
Re: Reader 9 causes BSOD on Windows XP Pro
#573
Author: Pat_Willener
Date: Mon, 16 Mar 2009 05:32
1 lines
809 bytes
No, that doesn't tell me anything. You should post the data from the BSOD, or if this is not available, the Watchdog event log from C:\Windows\Logfiles\Watchdog.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads