Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

PFN List Corrupt and IRQL not less or equal bsods


  • Please log in to reply
7 replies to this topic

#1 squall_1981

squall_1981

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Location:Hurst, TX
  • Local time:09:36 AM

Posted 23 November 2008 - 12:01 AM

Well I had a power supply failure, and multiple parts in my computer have failed. I'm using my original hard drive and video card, but that's really about it. I replaced everything else. My computer is working again.....except daily I am having random bsods. Usually PFN List Corrupt, and IRQL not less or equal. Here is the error report on my last bsod. I suspect bad drivers, but can't nail down which one. I am suspecting my video card and hard drive as well at this point, but I reformatted the hard drive and am still getting bsods. I have tried 3 different ram pairs. Can anybody glean any information from the dump file? Any help is appreciated.



Microsoft ® Windows Debugger Version 6.10.0003.233 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`01c5c000 PsLoadedModuleList = 0xfffff800`01e21db0
Debug session time: Sat Nov 22 10:51:28.682 2008 (GMT-6)
System Uptime: 0 days 0:18:48.775
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols

Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, fffff98023e61001, 18ffe, fffff78000001000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1b02 )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: fffff98023e61001
Arg3: 0000000000018ffe
Arg4: fffff78000001000

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


BUGCHECK_STR: 0x1a_41284

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001cff512 to fffff80001cb1350

STACK_TEXT:
fffffa60`06a787a8 fffff800`01cff512 : 00000000`0000001a 00000000`00041284 fffff980`23e61001 00000000`00018ffe : nt!KeBugCheckEx
fffffa60`06a787b0 fffff800`01d10df2 : fffffa60`06a78978 fffff6fc`c011f308 fffffa60`06a78970 fffffa60`00a96f26 : nt! ?? ::FNODOBFM::`string'+0x1b02
fffffa60`06a787f0 fffff800`01f2df49 : 00000000`00000000 fffff880`0a5851f0 00000000`00000000 00000000`0001ab38 : nt! ?? ::FNODOBFM::`string'+0x19172
fffffa60`06a78ac0 fffff800`01cc379e : 00000000`00000000 fffffa60`019637f0 fffffa80`042afd88 00000000`00100000 : nt!CcUnmapVacb+0x59
fffffa60`06a78b00 fffff800`01cc9cd3 : 00000000`00000000 fffffa80`0b4bb940 00000000`00000000 00000000`00000000 : nt!CcUnmapVacbArray+0x2be
fffffa60`06a78b80 fffff800`01cca89b : fffffa80`0b498e30 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CcDeleteSharedCacheMap+0x123
fffffa60`06a78be0 fffff800`01ccafbb : fffffa60`01963700 00000000`00000000 fffff880`00000000 fffffa60`06a78d00 : nt!CcWriteBehind+0x5eb
fffffa60`06a78c70 fffff800`01cbe05a : fffffa80`042d41e0 fffff800`01e5a8a0 fffffa80`0b0ea570 fffffa80`00000001 : nt!CcWorkerThread+0x17b
fffffa60`06a78cf0 fffff800`01ed3ff3 : fffffa80`042d41e0 fffffffe`9a5f4400 fffffa80`08187040 00000000`00000080 : nt!ExpWorkerThread+0x11a
fffffa60`06a78d50 fffff800`01ceb546 : fffffa60`005ec180 fffffa80`08187040 fffffa80`081867b0 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`06a78d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+1b02
fffff800`01cff512 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1b02

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+1b02

BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+1b02

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

BC AdBot (Login to Remove)

 


#2 squall_1981

squall_1981
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Location:Hurst, TX
  • Local time:09:36 AM

Posted 23 November 2008 - 12:06 PM

New one today.


Microsoft ® Windows Debugger Version 6.10.0003.233 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`01c52000 PsLoadedModuleList = 0xfffff800`01e17db0
Debug session time: Sun Nov 23 10:27:15.808 2008 (GMT-6)
System Uptime: 0 days 0:00:49.526
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80db00d81b, 2, 0, fffff80001ccb32c}

*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Page 6e648 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Probably caused by : aswMonFlt.sys ( aswMonFlt+6f33 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa80db00d81b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001ccb32c, address which referenced memory

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

Page 6e648 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

READ_ADDRESS: fffffa80db00d81b

CURRENT_IRQL: 2

FAULTING_IP:
nt!MmCheckCachedPageState+6ec
fffff800`01ccb32c 41f6471b40 test byte ptr [r15+1Bh],40h

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: ashServ.exe

TRAP_FRAME: fffffa600d0c22c0 -- (.trap 0xfffffa600d0c22c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=0000000fffffffff
rdx=fffff80001c52000 rsi=fffffa800a914530 rdi=fffff80001cdf6f7
rip=fffff80001ccb32c rsp=fffffa600d0c2450 rbp=fffff8800895fcf8
r8=fffffa60019d27f0 r9=0000000000000000 r10=0000000000000002
r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MmCheckCachedPageState+0x6ec:
fffff800`01ccb32c 41f6471b40 test byte ptr [r15+1Bh],40h ds:0400:001b=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001ca70ee to fffff80001ca7350

STACK_TEXT:
fffffa60`0d0c2178 fffff800`01ca70ee : 00000000`0000000a fffffa80`db00d81b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0d0c2180 fffff800`01ca5fcb : 00000000`00000000 fffff800`01cd50c3 fffffa60`0d0c2300 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`0d0c22c0 fffff800`01ccb32c : fffffa80`0a914530 00000000`0001e000 fffff780`00001000 fffff880`0895dcf0 : nt!KiPageFault+0x20b
fffffa60`0d0c2450 fffff800`01f1a06d : fffffa80`000094ae 00000000`00001000 00000000`00000000 fffff6fc`40044af8 : nt!MmCheckCachedPageState+0x6ec
fffffa60`0d0c24e0 fffffa60`010c0136 : fffffa80`0a94a710 00000000`00000001 00000000`0007fc00 00000000`00080000 : nt!CcFastCopyRead+0x20d
fffffa60`0d0c25c0 fffffa60`00a8f248 : 00000000`00000080 fffffa60`0d0c2620 00000000`00000001 00000000`00000001 : Ntfs!NtfsCopyReadA+0x1e6
fffffa60`0d0c27b0 fffffa60`00a921d5 : fffffa60`0d0c28b8 00000000`00000000 fffffa80`0a94a703 fffffa60`00000000 : fltmgr!FltpPerformFastIoCall+0x88
fffffa60`0d0c2810 fffffa60`00a9e6f0 : 00000000`00000000 fffffa80`0a94a710 00000000`00000000 00000000`00000000 : fltmgr!FltpPassThroughFastIo+0xb5
fffffa60`0d0c2860 fffffa60`06775f33 : fffffa80`0a940430 fffffa80`0000f18b fffffa80`09c68510 fffffa80`00000000 : fltmgr!FltReadFile+0x260
fffffa60`0d0c2940 fffffa60`06776272 : 00000000`00000000 fffffa60`10800000 fffffa60`0d0c2a80 00000000`00000000 : aswMonFlt+0x6f33
fffffa60`0d0c2a10 fffff800`01f343dc : 00000000`00000001 00000000`057a0000 00000000`00000000 00000000`00001000 : aswMonFlt+0x7272
fffffa60`0d0c2a70 fffff800`01f111bf : fffffa80`0d3e4780 fffffa60`0d0c2c01 fffffa80`0d3e4780 fffffa60`0d0c2ca0 : nt!IopSynchronousServiceTail+0x13c
fffffa60`0d0c2ad0 fffff800`01ca6df3 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x5fd
fffffa60`0d0c2bb0 00000000`75733917 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02d3f0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75733917


STACK_COMMAND: kb

FOLLOWUP_IP:
aswMonFlt+6f33
fffffa60`06775f33 8bf8 mov edi,eax

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: aswMonFlt+6f33

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: aswMonFlt

IMAGE_NAME: aswMonFlt.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4923033f

FAILURE_BUCKET_ID: X64_0xA_aswMonFlt+6f33

BUCKET_ID: X64_0xA_aswMonFlt+6f33

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa80db00d81b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001ccb32c, address which referenced memory

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

Page 6e648 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

READ_ADDRESS: fffffa80db00d81b

CURRENT_IRQL: 2

FAULTING_IP:
nt!MmCheckCachedPageState+6ec
fffff800`01ccb32c 41f6471b40 test byte ptr [r15+1Bh],40h

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: ashServ.exe

TRAP_FRAME: fffffa600d0c22c0 -- (.trap 0xfffffa600d0c22c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=0000000fffffffff
rdx=fffff80001c52000 rsi=fffffa800a914530 rdi=fffff80001cdf6f7
rip=fffff80001ccb32c rsp=fffffa600d0c2450 rbp=fffff8800895fcf8
r8=fffffa60019d27f0 r9=0000000000000000 r10=0000000000000002
r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MmCheckCachedPageState+0x6ec:
fffff800`01ccb32c 41f6471b40 test byte ptr [r15+1Bh],40h ds:0400:001b=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001ca70ee to fffff80001ca7350

STACK_TEXT:
fffffa60`0d0c2178 fffff800`01ca70ee : 00000000`0000000a fffffa80`db00d81b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0d0c2180 fffff800`01ca5fcb : 00000000`00000000 fffff800`01cd50c3 fffffa60`0d0c2300 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`0d0c22c0 fffff800`01ccb32c : fffffa80`0a914530 00000000`0001e000 fffff780`00001000 fffff880`0895dcf0 : nt!KiPageFault+0x20b
fffffa60`0d0c2450 fffff800`01f1a06d : fffffa80`000094ae 00000000`00001000 00000000`00000000 fffff6fc`40044af8 : nt!MmCheckCachedPageState+0x6ec
fffffa60`0d0c24e0 fffffa60`010c0136 : fffffa80`0a94a710 00000000`00000001 00000000`0007fc00 00000000`00080000 : nt!CcFastCopyRead+0x20d
fffffa60`0d0c25c0 fffffa60`00a8f248 : 00000000`00000080 fffffa60`0d0c2620 00000000`00000001 00000000`00000001 : Ntfs!NtfsCopyReadA+0x1e6
fffffa60`0d0c27b0 fffffa60`00a921d5 : fffffa60`0d0c28b8 00000000`00000000 fffffa80`0a94a703 fffffa60`00000000 : fltmgr!FltpPerformFastIoCall+0x88
fffffa60`0d0c2810 fffffa60`00a9e6f0 : 00000000`00000000 fffffa80`0a94a710 00000000`00000000 00000000`00000000 : fltmgr!FltpPassThroughFastIo+0xb5
fffffa60`0d0c2860 fffffa60`06775f33 : fffffa80`0a940430 fffffa80`0000f18b fffffa80`09c68510 fffffa80`00000000 : fltmgr!FltReadFile+0x260
fffffa60`0d0c2940 fffffa60`06776272 : 00000000`00000000 fffffa60`10800000 fffffa60`0d0c2a80 00000000`00000000 : aswMonFlt+0x6f33
fffffa60`0d0c2a10 fffff800`01f343dc : 00000000`00000001 00000000`057a0000 00000000`00000000 00000000`00001000 : aswMonFlt+0x7272
fffffa60`0d0c2a70 fffff800`01f111bf : fffffa80`0d3e4780 fffffa60`0d0c2c01 fffffa80`0d3e4780 fffffa60`0d0c2ca0 : nt!IopSynchronousServiceTail+0x13c
fffffa60`0d0c2ad0 fffff800`01ca6df3 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x5fd
fffffa60`0d0c2bb0 00000000`75733917 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02d3f0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75733917


STACK_COMMAND: kb

FOLLOWUP_IP:
aswMonFlt+6f33
fffffa60`06775f33 8bf8 mov edi,eax

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: aswMonFlt+6f33

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: aswMonFlt

IMAGE_NAME: aswMonFlt.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4923033f

FAILURE_BUCKET_ID: X64_0xA_aswMonFlt+6f33

BUCKET_ID: X64_0xA_aswMonFlt+6f33

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

#3 squall_1981

squall_1981
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Location:Hurst, TX
  • Local time:09:36 AM

Posted 24 November 2008 - 03:33 PM

New one today....I've never seen this one before.


Microsoft ® Windows Debugger Version 6.10.0003.233 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`01c5e000 PsLoadedModuleList = 0xfffff800`01e23db0
Debug session time: Sun Nov 23 22:13:38.114 2008 (GMT-6)
System Uptime: 0 days 1:34:57.861
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000113bcc, fffffa600e0affb0, 0}

PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for details
Probably caused by : win32k.sys ( win32k!PFEOBJ::vFreepfdg+e8 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000113bcc, Address of the exception record for the exception that caused the bugcheck
Arg3: fffffa600e0affb0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
win32k!PFEOBJ::vFreepfdg+e8
fffff960`00113bcc 0fba60300f bt dword ptr [rax+30h],0Fh

CONTEXT: fffffa600e0affb0 -- (.cxr 0xfffffa600e0affb0)
rax=c9ab87ac0000017c rbx=0000000000000000 rcx=fffff900c1c29010
rdx=0000000000000000 rsi=fffff900c1c6f920 rdi=fffffa600e0b0890
rip=fffff96000113bcc rsp=fffffa600e0b0810 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000001 r10=fffff900c1c29010
r11=fffffa600e0b08b0 r12=0000000000000000 r13=fffff900c0709030
r14=000000000000171f r15=0000000000000001
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
win32k!PFEOBJ::vFreepfdg+0xe8:
fffff960`00113bcc 0fba60300f bt dword ptr [rax+30h],0Fh ds:002b:c9ab87ac`000001ac=????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: ehshell.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff960002c106a to fffff96000113bcc

STACK_TEXT:
fffffa60`0e0b0810 fffff960`002c106a : 00000000`00000000 00000000`00000000 00000000`00000000 fffff960`001508c5 : win32k!PFEOBJ::vFreepfdg+0xe8
fffffa60`0e0b0840 fffff960`002cb81b : fffff900`c1c29010 00000000`00000001 fffffa60`0e0b0920 00000000`00000000 : win32k!RFONTOBJ::vDeleteRFONT+0x32
fffffa60`0e0b0890 fffff960`002cb492 : 00000000`00000000 fffff900`c1f75540 fffff900`c26a2ca0 fffff900`c3418010 : win32k!vRestartKillRFONTList+0xab
fffffa60`0e0b08e0 fffff960`0017dcba : fffff900`c2443930 00000000`00000000 00000000`00000000 fffff900`0000001e : win32k!PFTOBJ::bUnloadWorkhorse+0x196
fffffa60`0e0b0960 fffff960`0017e5c9 : fffff900`c2443910 00000000`00000000 00000000`00000001 00000000`00000001 : win32k!vCleanupPrivateFonts+0x72
fffffa60`0e0b09a0 fffff960`00176364 : 00000000`00000000 00000000`c0000000 fffff900`c3416910 fffffa60`019d2180 : win32k!NtGdiCloseProcess+0x479
fffffa60`0e0b0a00 fffff960`00175313 : 00000000`00000000 fffff900`c3416910 00000000`00000000 00000000`c000004b : win32k!GdiProcessCallout+0x1f4
fffffa60`0e0b0a80 fffff800`01f5984b : fffffa80`097c2060 00000000`00000000 00000000`00000000 fffffa80`04de83b0 : win32k!W32pProcessCallout+0x6f
fffffa60`0e0b0ab0 fffff800`01f59dd5 : 00000000`c000004b fffffa80`04de8301 00000000`00000000 000007fe`f15c0000 : nt!PspExitThread+0x467
fffffa60`0e0b0b70 fffff800`01f11ef2 : 00000000`00000000 00000000`0000000c 00000000`00000001 fffff880`0000000c : nt!PspTerminateThreadByPointer+0x4d
fffffa60`0e0b0bc0 fffff800`01cb2df3 : fffffa80`0a868130 fffffa80`04de83b0 fffffa60`0e0b0ca0 00000000`00000001 : nt!NtTerminateProcess+0xfa
fffffa60`0e0b0c20 00000000`77025d3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0014ede8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77025d3a


FOLLOWUP_IP:
win32k!PFEOBJ::vFreepfdg+e8
fffff960`00113bcc 0fba60300f bt dword ptr [rax+30h],0Fh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!PFEOBJ::vFreepfdg+e8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1bca9

STACK_COMMAND: .cxr 0xfffffa600e0affb0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8

BUCKET_ID: X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8

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

#4 RandomUser

RandomUser

  • Members
  • 518 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:36 AM

Posted 24 November 2008 - 11:56 PM

Unless I'm mistaken, you're running Vista in 64 bit mode? Can you confirm this?

Second, Are you running Avast Antivirus? If so and this is Vista 64 bit allowing Terminal Server (remote desktop) connections,
that's a good start for diagnosing the problem.

Also, Can you post all of your hardware, down to the Modem and video cards, and the Model of Ram installed on the pc?

This is going to be a bit involved to figure out what's happening.

#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:36 AM

Posted 25 November 2008 - 01:19 PM

The first error (STOP 0x1a) is a memory management error, but the debugger is stating it's a driver fault.
The next error (STOP 0x0a) is an memory access error, most commonly caused by a driver. This one blames Avast - so uninstall Avast and install a freshly downloaded copy.
The next error (STOP 0x3b) is a system service exception, but there's many different reasons for it.

The power supply failure (and the other component failures) may be related. This could then mean that there may be damage to the remaining equipment.

Try a hard drive diagnostic available from the manufacturer of your hard drive. Try a memory diagnostic - since you've tried 3 sets of RAM it may reveal errors anyway (which would then probably be due to motherboard failure). Try a video card stress test to test the video card (or swap it for another one temporarily).

Since malware can be a factor in these issues - I'd suggest some free, online scans to verify that you're clean: http://www.bleepingcomputer.com/blogs/usas...?showentry=1252
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#6 RandomUser

RandomUser

  • Members
  • 518 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:36 AM

Posted 25 November 2008 - 06:09 PM

This is only a guess, but when the Hard drive was moved to another computer, Was Windows Re-installed or was the original configuration on the Failing PC used? That could be a pointer.

Further more, Can you confirm that the Ram combinations that you've used are supported by your motherboard? IE DDR 2, DDR 3 and
what speeds are they? Also, What Cas Latencies do they have?

Some Motherboards don't like Ram with certain Cas Latenies or overclocking.

I suspect if the Video card was damaged, that display issues would be happening and there might be noticeable Burning on the Video Card.

I would do as the other one says, and run the Hard Drive test, but I might also Try to boot from a Live CD.

http://en.wikipedia.org/wiki/LiveCD

This could eliminate the Hard drive as a problem or help you be more detailed in finding a resolution.

Edited by RandomUser, 25 November 2008 - 07:01 PM.


#7 squall_1981

squall_1981
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Location:Hurst, TX
  • Local time:09:36 AM

Posted 26 November 2008 - 06:45 PM

I am using a motherboard I got through RMA...ie identical hardware. I think I may have solved the problem. I've had no bluescreens for a 2-3 days now. I took out my tv tuner card. What I've found is that Vista 64 bit along with 4gb of ram does not mix well with many tv tuner cards. But it seemed to run ok on my previous motherboard.....but only for a month because that's how long I've had it. Anyway I've been error free for a few days except for a minor error that came up saying that prefetch had stopped working. I'll live with that I guess, and I haven't seen that one for 2 days. Thanks for the help. I was already virus free. Memtest86 never came up with errors. CPU benchmarks were normal. Video card seems to be running fine....except when I mess with Rivatuner I did notice some artifacts, but none without.

#8 RandomUser

RandomUser

  • Members
  • 518 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:36 AM

Posted 26 November 2008 - 07:40 PM

You may want to update the BIOS and the software/drivers for the TV Tuner card, and this may allow you to run the runer card without issues.


You left out that you had a tuner card installed. But if the computer is working now, all the better




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users