BSODS MEMORY_MGMT/pfn_list_corrupt help - Windows 7 x64

D

DamiThorStone

Member
Joined
Apr 5, 2015
Posts
8
Windows 7
x64
Windows 7
Not OEM, it's full retail
MOBO,RAM,VCARD, PSUPPLY, are less then 3mnths. HD is about a year, and the CPU is about 4yrs old.
Installed and reinstalled the os several times, last time was about 2months ago.
Processor: AMD Phenom(tm)II X4 965 Processor 3.40 GHz
NVIDIA GeForce GT 740
MSI 970
I don't remember the brand and its not easily accessible. The watt. is 650. If the brand is extremely needed I can find a way to get it.
It's a frankenstein, i put it together.
Desktop

I keep getting these bsod's when running a particular game. Any help would be amazing!
 

Attachments

No dumps in your output.

1. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

3. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
 
Random bsods during particular game

**This is essentially a re-post from a previous topic I opened. It contains updated information that was requested in that post.**

Hello all, still getting random bsods when playing a particular game or just after closing it. Any help would be awesome!

Windows 7
x64
Windows 7
Not OEM, it's full retail
MOBO,RAM,VCARD, PSUPPLY, are less then 3mnths. HD is about a year, and the CPU is about 4yrs old.
Installed and reinstalled the os several times, last time was about 2months ago.
Processor: AMD Phenom(tm)II X4 965 Processor 3.40 GHz
NVIDIA GeForce GT 740
MSI 970View attachment BSOD Report.zipView attachment SysnativeFileCollectionApp.zip
I don't remember the brand and its not easily accessible. The watt. is 650. If the brand is extremely needed I can find a way to get it.
It's a frankenstein, i put it together.
Desktop
 
Code: 
3: kd> .bugcheck
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0d173cf8 fffff880`0d173550 fffff880`014b46c7

Code: 
3: kd> .exr 0xfffff8800d173cf8
ExceptionAddress: fffff880014b46c7 (Ntfs!NtfsFindPrefixHashEntry+0x00000000000001fe)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000c0100001010
Attempt to read from address 00000c0100001010

Looking at the exception record regarding the crash, we can see the reason for the crash was an access violation that occurred in Ntfs!NtfsFindPrefixHashEntry+0x00000000000001fe.

Code: 
3: kd> .cxr 0xfffff8800d173550;r
rax=fffff8a00298d000 rbx=00000c0100001000 rcx=00000000000005d4
rdx=0000000000000003 rsi=fffff8a0002945b0 rdi=fffffa800df7c358
rip=fffff880014b46c7 rsp=fffff8800d173f30 rbp=0000000000000000
 r8=000000001a4942ea  r9=0000000000000000 r10=0000000000000010
r11=fffff8800d173f78 r12=fffff8800d174240 r13=fffff8800d1744d0
r14=00000000000002ea r15=00000000000042ea
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
Ntfs!NtfsFindPrefixHashEntry+0x1fe:
fffff880`014b46c7 44394310        cmp     dword ptr [rbx+10h],r8d ds:002b:00000c01`00001010=????????

Looking into the context record for the trapframe on the faulting instruction, we can see it was comparing r8d to the value stored at address rbx+10.

Code: 
3: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`0d172d28 fffff880`01410211 nt!KeBugCheckEx
01 fffff880`0d172d30 fffff880`01416b8b Ntfs! ?? ::FNODOBFM::`string'+0x299d
02 fffff880`0d172d70 fffff800`02ea7c4c Ntfs! ?? ::FNODOBFM::`string'+0xee8
03 fffff880`0d172da0 fffff800`02ea76cd nt!_C_specific_handler+0x8c
04 fffff880`0d172e10 fffff800`02ea64a5 nt!RtlpExecuteHandlerForException+0xd
05 fffff880`0d172e40 fffff800`02eb7431 nt!RtlDispatchException+0x415
06 fffff880`0d173520 fffff800`02e7b542 nt!KiDispatchException+0x135
07 fffff880`0d173bc0 fffff800`02e7a0ba nt!KiExceptionDispatch+0xc2
08 fffff880`0d173da0 fffff880`014b46c7 nt!KiPageFault+0x23a
09 fffff880`0d173f30 00000000`00000000 Ntfs!NtfsFindPrefixHashEntry+0x1fe

Leaving the trapframe and going back to the crash callstack, we can see nothing really aside from hitting a pagefault after the file system function. Just some exception dispatching.

Get rid of Bitdefender for MSE as I have a feeling it's playing a role in this.

BitDefender removal - How to uninstall Bitdefender

MSE - Microsoft Security Essentials - Microsoft Windows
 
Ok, I've un-installed bitdefender, rebooted, and then installed MSE. Right after the restart after the MSE dl i got another bsod. I've attached the report. Thanks again!
 

Attachments

Enable verifier.

Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (only on Windows 7 & 8/8.1)
- DDI compliance checking (only on Windows 8/8.1)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues.

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

- Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

Any other questions can most likely be answered by this article:

Using Driver Verifier to identify issues with Windows drivers for advanced users
 
I've kept DV enabled and haven't had a bsod yet. However, I did get this from Windows, not sure if they are related. The message was:

Problem: Video hardware errorFiles that help describe the problem:
WD-20150424-0150.dmp
sysdata.xml
WERInternalMetadata.xml

I've also attached the files associated with the error. Not sure if this is useful or related.
 

Attachments

Code: 
2: kd> .bugcheck
Bugcheck code 00000117
Arguments fffffa80`12b99010 fffff880`057e8480 00000000`00000000 00000000`00000000

Code: 
2: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`04de0630 fffff880`0611372b watchdog!WdDbgReportRecreate+0xa3
01 fffff880`04de0b50 fffff880`061143f0 dxgkrnl!TdrUpdateDbgReport+0xcb
02 fffff880`04de0ba0 fffff880`060e86b3 dxgkrnl!TdrCollectDbgInfoStage2+0x220
03 fffff880`04de0bd0 fffff880`06114f43 dxgkrnl!DXGADAPTER::Reset+0xef
04 fffff880`04de0c80 fffff880`061e503d dxgkrnl!TdrResetFromTimeout+0x23
05 fffff880`04de0d00 fffff800`03115aba dxgmms1!VidSchiWorkerThread+0x101
06 fffff880`04de0d40 fffff800`02e6d426 nt!PspSystemThreadStartup+0x5a
07 fffff880`04de0d80 00000000`00000000 nt!KiStartSystemThread+0x16

Starting from frame 07, we can see we're starting a system thread which is a video worker thread from the Direct X MMS. Directly after scheduling the video worker thread, we enter TDR (timeout detection recovery) to try and restore the display driver as it has crashed (your display driver is nVidia). You can see on frame 03 that the Direct X kernel calls DXGADAPTER::Reset to reset the display driver in an attempt to ultimately recovery it as I discussed, and it appears to have succeeded as we're afterwards collecting the debug info to write to a dump as opposed to failing and throwing a bug check.

Given an 0x117 occurred, this gives us a place to start. This tells us that either your display driver needs to be updated, or rolled back if at the latest version. If neither of those help, this implies your video card is faulty, most likely.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top