Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: PFN_LIST_CORRUPT BSOD, Driver Verifier BSOD

17 Jun 2014   #11
Onision

Windows 7 Home Premium 64bit
 
 

Just got another bsod today, the message was different from the other ones though.


My System SpecsSystem Spec
.
18 Jun 2014   #12
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

What do you have connected to the USB ports?
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\ONISION-PC-Tue_06_17_2014_205310_39\061714-17940-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0345a000 PsLoadedModuleList = 0xfffff800`0369d890
Debug session time: Wed Jun 18 09:48:09.152 2014 (UTC + 6:00)
System Uptime: 0 days 1:45:08.964
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff88005fbae75, 20e3d2121, fffff80000b9c490, a}

Probably caused by : hidusb.sys ( hidusb!HumReadReport+13f )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff88005fbae75, Virtual address for the attempted write.
Arg2: 000000020e3d2121, PTE contents.
Arg3: fffff80000b9c490, (reserved)
Arg4: 000000000000000a, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000b9c490 -- (.trap 0xfffff80000b9c490)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88005fc7110 rbx=0000000000000000 rcx=fffffa800e977b58
rdx=fffffa800d7a4b40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005fbaeef rsp=fffff80000b9c620 rbp=0000000000000000
 r8=fffff88005fbae32  r9=0000000000000009 r10=fffff8000364b820
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbccgp!UsbcForwardIrp+0xf:
fffff880`05fbaeef 41fe4043        inc     byte ptr [r8+43h] ds:fffff880`05fbae75=00
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000354c14b to fffff800034cfbc0

STACK_TEXT:  
fffff800`00b9c328 fffff800`0354c14b : 00000000`000000be fffff880`05fbae75 00000002`0e3d2121 fffff800`00b9c490 : nt!KeBugCheckEx
fffff800`00b9c330 fffff800`034cdcee : fffff800`0364000b fffff800`00b9c4e8 00000000`00000008 fffffa80`0e998b58 : nt! ?? ::FNODOBFM::`string'+0x4333b
fffff800`00b9c490 fffff880`05fbaeef : 00000000`00000000 fffffa80`0e977c58 00000000`00000002 fffffa80`0e977b58 : nt!KiPageFault+0x16e
fffff800`00b9c620 fffff880`05fb76d6 : fffffa80`0e998b58 fffff880`05fbae32 00000000`00000324 fffffa80`0ea31800 : usbccgp!UsbcForwardIrp+0xf
fffff800`00b9c650 fffff880`05fb797e : fffffa80`0e977b58 fffffa80`0ea31800 fffffa80`0ea31800 fffffa80`0e998b58 : usbccgp!DispatchPdoUrb+0xfa
fffff800`00b9c690 fffff880`05fb572e : 00000000`0000000f fffffa80`0e998b50 fffffa80`0e998b58 fffffa80`0ea31800 : usbccgp!DispatchPdoInternalDeviceControl+0x17a
fffff800`00b9c6c0 fffff880`05ff448f : fffffa80`0e998a00 fffffa80`0ea31801 00000000`00000000 00000000`000007ff : usbccgp!USBC_Dispatch+0x2de
fffff800`00b9c740 fffff880`05ff3f5b : fffffa80`0ea31ba0 fffffa80`0e97dc01 fffff800`00b9c800 fffffa80`0e97db30 : hidusb!HumReadReport+0x13f
fffff800`00b9c790 fffff880`05e04555 : fffffa80`0e9a9701 fffffa80`0e9a97c0 fffffa80`0ea31800 00000000`00000009 : hidusb!HumInternalIoctl+0x137
fffff800`00b9c800 fffff880`05e04d75 : fffffa80`0e9a97c0 fffffa80`0e97dca0 00000000`00000000 00000000`00000009 : HIDCLASS!HidpSubmitInterruptRead+0xdd
fffff800`00b9c860 fffff800`034d35d1 : fffffa80`0ea31ba3 00000000`00000000 fffffa80`0e97db01 fffffa80`0ea31800 : HIDCLASS!HidpInterruptReadComplete+0x37d
fffff800`00b9c8f0 fffff880`056e0631 : fffffa80`0cd9f050 fffffa80`0ece7c00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00b9c9e0 fffff880`056e0b0f : fffffa80`0faf8c02 fffffa80`0ea31800 00000000`ffffffff fffffa80`0cd9feb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`00b9cac0 fffff880`056de66f : fffffa80`0cd9feb0 fffffa80`0cd9f1a0 fffffa80`0cda0050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00b9cb20 fffff880`056cff89 : fffffa80`0cd9f050 00000000`00000000 fffffa80`0cd9fe02 fffffa80`0cd9feb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00b9cb60 fffff800`034da30c : fffff800`0364ae80 fffffa80`0cd9feb0 fffffa80`0cd9fec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9cb90 fffff800`034c78ca : fffff800`0364ae80 fffff800`03658cc0 00000000`00000000 fffff880`056cfdb0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
hidusb!HumReadReport+13f
fffff880`05ff448f 488b4c2460      mov     rcx,qword ptr [rsp+60h]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  hidusb!HumReadReport+13f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hidusb

IMAGE_NAME:  hidusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

FAILURE_BUCKET_ID:  X64_0xBE_hidusb!HumReadReport+13f

BUCKET_ID:  X64_0xBE_hidusb!HumReadReport+13f

Followup: MachineOwner
---------
My System SpecsSystem Spec
18 Jun 2014   #13
Onision

Windows 7 Home Premium 64bit
 
 

Just the wireless receiver for my mouse and keyboard, they connect to the same receiver. I dug further and realized the driver upgrader program did not truly get rid of the old drivers and upgrade them so i manually updated my usb 3.0 drivers an hour ago. Ill report back if another BSOD happens
My System SpecsSystem Spec
.

18 Jun 2014   #14
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Alright thanks
My System SpecsSystem Spec
18 Jun 2014   #15
Onision

Windows 7 Home Premium 64bit
 
 

Well that didnt fix it New logs
My System SpecsSystem Spec
18 Jun 2014   #16
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\ONISION-PC-Wed_06_18_2014_180026_68\061814-24757-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03454000 PsLoadedModuleList = 0xfffff800`03697890
Debug session time: Thu Jun 19 06:57:12.812 2014 (UTC + 6:00)
System Uptime: 0 days 0:25:17.014
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 1d0e91, 0, 1ccc11}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001d0e91, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000001ccc11, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003558a4c to fffff800034c9bc0

STACK_TEXT:  
fffff880`0a85ae18 fffff800`03558a4c : 00000000`0000004e 00000000`00000099 00000000`001d0e91 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a85ae20 fffff800`03475ed2 : 00000000`00000000 fffff680`0000fb10 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0a85ae60 fffff800`034997c3 : fffffa80`0ce1e060 fffff700`000012e9 0000007f`fffffff8 fffff8a0`007731b0 : nt! ?? ::FNODOBFM::`string'+0x3242a
fffff880`0a85aef0 fffff800`0349a892 : fffffa80`0ce1e060 fffffa80`00000001 fffff8a0`00000bfa fffff880`000009f5 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0a85b7a0 fffff800`0379f05a : fffff8a0`0ecf4060 fffff880`0a85bae0 00000000`00000000 fffffa80`0c493b50 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0a85b7f0 fffff800`03783b7d : 00000000`c0000005 fffff880`0a85ba01 000007ff`fffaa000 fffffa80`0ceb2640 : nt!PspExitThread+0x56a
fffff880`0a85b8f0 fffff800`034bc6fa : 00000000`00000001 fffff880`0a85ba68 00000000`00000001 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`0a85b920 fffff800`034bca40 : 00000000`770245e8 fffff880`0a85b9a0 fffff800`03783af0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0a85b9a0 fffff800`034c8ef7 : fffffa80`0c493b50 00000000`770245c0 00000000`000000c0 00000000`0029baa0 : nt!KiInitiateUserApc+0x70
fffff880`0a85bae0 00000000`76f72bba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0251fa58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f72bba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`03558a4c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------
Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.
My System SpecsSystem Spec
18 Jun 2014   #17
Onision

Windows 7 Home Premium 64bit
 
 

Do you know why speccy says my ram is 936mhz? It also said 936 mhz while i was testing these rams in memtest86+, The bios is set to run then at their manufactured speed which is 1866mhz. I did test these ram sticks in slots 1 and 3 at the same time for 17 1/2 hours with 13 passes and 0 errors
My System SpecsSystem Spec
18 Jun 2014   #18
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Do you get BSOD in safe mode?
My System SpecsSystem Spec
18 Jun 2014   #19
Onision

Windows 7 Home Premium 64bit
 
 

LOL nevermind found out you had to times it by 2. So do you think overnight i should put both ram sticks in slots 2 and 4 this time?
My System SpecsSystem Spec
18 Jun 2014   #20
Onision

Windows 7 Home Premium 64bit
 
 

I never ran this computer in safe mode before
My System SpecsSystem Spec
Reply

 PFN_LIST_CORRUPT BSOD, Driver Verifier BSOD




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Fairly Often. Driver Verifier Enabled = BSOD on Boot Every Time
I have a relatively new computer that I've built and I've been getting BSOD's for a while. At first I thought it was because the pagefile was disabled, but that was just why they weren't getting logged to MiniDump. Then I got it enabled again and now I'm getting a lot of BSODs. It's been 0x3b...
BSOD Help and Support
Multiple BSOD. Driver Verifier Driver caught a driver corrupting
I have had BSOD for a while and being super busy I did not have time to look at it and get it fixed. Well Being a computer guy I assumed I could fix it myself. But with tons of research and trying to use every guide I can find I decided to try here(probably should have came here first). Today I...
BSOD Help and Support
BSOD-PC Freezes randomly-Driver Verifier BSOD's at User Log-On
Hello, As the thread shows im having lots and lots of little(and big) crashes. Im attaching the SF log and any help will be appreciated Many thanks, Dimitris
BSOD Help and Support
Random BSOD, ran driver verifier now got 0x000000c9 BSOD
Hi All Have been following a number of threads to identify my issue. I can only assume that a driver is at fault as when i run verifier i have to start in safe mode. Attached is my mini dump, can anyone help me identify where the issue is? Thanks a lot Lordmwa EDIT - Added the full lot...
BSOD Help and Support
BSOD's in driver verifier, BSOD's on C:/ disk check (os hdd) & more.
Recently my computer has started seriously acting up by first disabling all directx and d3d functionality it took a full driver uninstall and reinstall to make that functional again but my computer is still having bsod issue's I don't understand where this came from it happened out of nowhere my...
BSOD Help and Support
Driver verifier BSOD
System will randomly lockup. It is very sporadic and I have tested vga, ram, and cpu using prime95, memtest as well as memtest86, furmark used for vga. 7hrs and 7 full runs of memtest 86, 0 errors. I feel hardware is solid. Upon enabling driver verifier the system bluescreens before even...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 23:22.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App