Solved In and out of game freezes, crashes, restarts and occasional BSOD.

[Feonir]

Pretty much as the title describes. Of late the system has been prone to random resets, freezing up entirely. (No HDD activity etc.) And it seldom goes to BSOD it just freeze screens and I have to manually powerdown.

To help diagnostic I am not going to lie, I did a stupid thing, and reinstalled Daemon tools I had an image file I had to get at. Its since been removed and I even did a system restore to a point before it was put back in. But the problems have persisted.

I also cannot at current update my video card drivers to current install as theres a few old as shit apps I have to run on a day by day that dont seem to want to run under the newest drivers.

ImageShack® - Online Photo and Video Hosting
Is basically what it looked like. Froze at this point in playing Stalker SoC. Cellphone camera quality not withstanding.

A couple of the BSOD's i've received are:

PFN List Corrupt
Bad Pool Header
Memory Management

As a pre-emptive strike I ran Memtest 86 for 6 passes and it came back with 0 errors as well.

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Feonir\Windows_NT6_BSOD_jcgriff2\042112-28485-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03059000 PsLoadedModuleList = 0xfffff800`0329d650
Debug session time: Sat Apr 21 10:12:42.138 2012 (UTC - 6:00)
System Uptime: 0 days 14:19:44.777
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {2, 1fa6cb, 22ffff, 2000}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )

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

0: 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: 0000000000000002, A list entry was corrupt
Arg2: 00000000001fa6cb, entry in list being removed
Arg3: 000000000022ffff, highest physical page number
Arg4: 0000000000002000, reference count of entry being removed

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


BUGCHECK_STR:  0x4E_2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800030e639d to fffff800030d5c80

STACK_TEXT:  
fffff880`09187778 fffff800`030e639d : 00000000`0000004e 00000000`00000002 00000000`001fa6cb 00000000`0022ffff : nt!KeBugCheckEx
fffff880`09187780 fffff800`030b6a74 : 00000000`00000000 fffffa80`09f15df0 fffff8a0`0a5f9c00 fffff8a0`0a5f9b10 : nt!MiUnlinkPageFromLockedList+0x8d
fffff880`09187800 fffff800`033b0a81 : fffffa80`09f15df0 fffff6fc`4001f2d0 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x244
fffff880`091878b0 fffff800`033b0bc0 : ffffffff`ffffffff 00000000`00000001 fffff8a0`0e8e5010 00000000`00000006 : nt!MiSwitchBaseAddress+0x61
fffff880`091878e0 fffff800`033d179f : 00000000`00000004 00000000`00000080 00000000`01000000 00000000`01000000 : nt!MiRelocateImageAgain+0x100
fffff880`09187930 fffff800`033b0306 : fffff880`09187b80 fffff880`09187ca0 00000000`00000000 fffff880`09187b78 : nt!MmCreateSection+0x2df
fffff880`09187b30 fffff800`030d4f13 : fffffa80`07aeb060 00000000`006ef058 fffff880`09187bc8 00000000`006ef228 : nt!NtCreateSection+0x171
fffff880`09187bb0 00000000`779717ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`006ef038 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779717ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+8d
fffff800`030e639d cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+8d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8d

BUCKET_ID:  X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8d

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

Points to memory. May be worth running Memtest86+ for seven passes overnight when you have a chance again. It does not always find errors the first time. You may also have a driver conflict or Windows corruption.

• If you are overclocking any hardware, please stop.
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 208910
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

Can you upload your msinfo32.nfo file again? Yours was corrupted. To get the file: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

 

[Feonir]

Thanks for the quick reply and when I get home from work I will try that stuff out. Currently I'm on 12 hour shifts so I will be able to let the Memtest run for an extended duration tomorrow and see if any errors are found on higher passes ran. The Memtest I used was the iso burnt to cd and ran on bootup. Is there a different one I should be using?

As of right now the system is fine, usually, when sitting idle on the desktop but any attempt to run a full screen game or even a particularly intensive flash game seems to make my pc have a brain melting aneurysm. Will try out the above and as soon as I am home fish out a non-corrupt file. Though it is looking like this install of windows is nearing its lifespan with the constantly reoccuring problems. Which is doubly an issue since the thing was an OEM install and i've no recovery media, sans repair disc I made with the OS, so formatting for now is out of the question.

 

[Feonir]

As requested, the msinfo32. Hopefully with 100% less corruption and a tangy lime taste.

Ninja Edit: Tried the SFC /SCANNOW Command and it made my PC explode into a Memory Management BSOD within 35 seconds of running the command.

 

[writhziden]

Looks like your system info is incompatible with my system or you have major corruption occurring. Instead of saving, try exporting (Start Menu -> Type msinfo32 into the Search programs and files box -> File -> Export -> msinfo32.txt). You can upload the .txt file here.

That is not a good sign that you had a blue screen crash running SFC /SCANNOW. See what Memtest86+ reveals.

 

[Feonir]

Will run an extended memtest today while at work. And here is the .txt version of the msinfo32 file.

Had to zip it as the uncompressed .txt file was 2.13 megs which is over the forum limit on such files.

 

[James7679]

Yeah, you definitely need to run memtest. The amount of program errors was in the hundreds. Post back the results of Memtest.

 

[Feonir]

Yeah I went to run the memtest this morning before work and on pass 0 pretty much instantaneously (5-20 mins it took me to shower and come back) it found a heap of errors and stopped running. So I believe that brings me to the step where I have to remove all but one of the chips and run individual scans.

So that will be a project once I get home from work tonight in about twelve hours.

 

[James7679]

It shouldn't take you that long. Try each stick until you find one without errors. Just to be positive that there is not a slot error, try the stick(s) that show as good, in the different slots. Toss the offending sticks and replace as necessary.

EDIT: Once you think you have found the good remaining stick(s), then do an extensive run to verify.

 

[Feonir]

In testing individual sticks how many passes should I let it run before it's deemed as an acceptable stick and move onto the next? Do I do 7 passes with every stick in the first slot then swap slots and sticks as needed?

Ninja Edit: Nevermind, I re-read the instructions. 7 passes per stick.

 

[James7679]

Sorry for the delay in reply. Offending memory should present within a few passes. So, run each stick for a few passes in each slot. Whatever you are left with is what you should do a full run with.

 

[Feonir]

After banishing 2 2gig ram chips to the depths, which is a cross between the garbage compactor from starwars and a rubbermaid container, the system has ran without a hitch all morning under various stressful loads. I.E Mass Effect 3 and other entertaining testing platforms.

I also ran the SFC - SCANNOW dealy a few times (3 with a restart between each) each of which came back negative with no abnormalities found I think it is a safe bet to declare this one solved. Will give it a day of testing before I mark it as solved and then from there routienely sacrifice some sort of maiden to some sort of demi-god that the last remaining chip remains stable.

Or failing that i'll smash a game boy color open and see what I can cobble together from it's guts. Once again you people were miracle workers, so my deep personal thanks to James7679 and Writhziden which is officially the second hardest name to type correctly without looking at a reference higher up in the thread.

 

[James7679]

Glad to hear Feonir. Good luck and let us know how things go.

 

[writhziden]

Glad to see James and I were able to help you find a solution. Keep us updated as you proceed, as James said.

 

[Feonir]

Welp been more then a few days now. Everything is quite stable and running fine so this one is a solved. Thanks again for all the help.

 

[writhziden]

Great news. You're very welcome for our help.