BSOD on Shutdown, App run, etc.

[Darren B]

Hello,

First timer here at the forums. I'm hoping someone with a lot more knowledge than me can help me out. Been getting consistent BSOD issues lately on my Alienware PC. I have Visa home premium 32 bit edition. My computer is about 5 yrs old and I use it to mostly to game, starcraft, wow, etc. I have recently started using it again after a long break (2years) and I'm starting to have these issues. I most recently get the Process_has_locked_pages error when Shutting down my PC. This has happened the last 6 times without fail. Also, when I try to run the blizzard loader, I also get this error. Not everytime, but enough to where I've come here for help. I'm not the best computer literate person around, but I can follow directions. If someone can spot something I may need to look at, please assist! I've attached the files needed. Feel free to talk to me in simple terms as well, I won't be offended! Thanks in advance for any help, I just want to be able to play my games again!

Darren

 

[richc46]

Welcome
Your results are clear. You have memory problems. Take memory test.
Run for 8 passes.
Then test each stick in a good slot for 6 passes.
If you have dual channel, the results may be incorrect, if shows pass.
Guide to using Memtest86+ - Geeks to Go Forums

 

[Darren B]

Thanks for quick response! I'll do this next week when I can get back to the computer! Thanks again!

 

[Darren B]

I have 4 x 1gb cards in my 680i SLI board. Should I put two in and run the test? Or can I even run with just one!? may take a few days to run a couple 8hr tests...but I want to make sure I do it right. Which ever is the right way, I'm assuming I look for the test with the most errors? and try to eliminate the possibility of a bad slot and figure which stick is bad and replace, Thanks!

 

[richc46]

We have to do this right, because if memory is the cause and you convince me that you passed, we will never find the cause.
For 8 passes, just run the computer as normal,
You must run each stick, so you need to run a scan for each stick.
If you fail, we need to know is it the ram or the Motherboard. If one stick is bad you must replace all. Do not mix and match. We have one member that disagrees with that, but do it the sure way.

 

[Darren B]

Alright, one more question of verification before I do this...sorry, just don't want to mess up the test and want to clarify something..keep in mind i have never ran a memory test before. So you say run computer for 8 passes as normal. Do you define normal as all 4 sticks in the machine? So I run the test for 8 passes with all 4 sticks and look for errors. Then I run the test for 8 passes with only one individual stick in the machine...and i do this for each stick? And after all that, will the test tell me if its a memory or motherboard issue? And if i find an error with one stick I must replace all? Sorry for all the questions, just want to understand it

 

[richc46]

Please do not be afraid to ask questions if you do not understand or feel uncomfortable, that is why we are here.

First just use the computer as you usually do, enjoy and have fun. If you use it a bit more than usual thats better.
If you fail, the test is over, but you will have to find out if its the ram or Mother Board.
If you pass, you must open the computer and take all the ram stick out, but one. Then run the computer for 6 passes. Do the same for each stick.
If you find the bad stick, then you must replace all. You should not mix and match.

 

[Darren B]

How do I use the computer as usual while the test is going on? Don't i have to start it from a boot cd...that is what I got from the directions....I figured it tested it while I wasn't using it...guess that's where I"m confused. I have the .iso on a CD...

 

[richc46]

LOL
You are correct, I was thinking about the driver verifier test, which another test for drivers.
This may help, too.
MemTest Manual

 

[Darren B]

Ok, I'll run the test 4 times...one with each of the 4 sticks. If I find a bad one, your advice is to replace them all....If I don't, then its the motherboard...ok will let you know what I find in my 4, 8 hr tests (seems time consuming! I shouldn't have a problem running these while I sleep right? Overheating anything?)

 

[richc46]

Never had that problem, but if the computer has problems already there is no way to predict the future.

 

[Darren B]

Ok, I got a question! So I've ran the test 3 times so far and will be running my last stick tonight. All these sticks I have stuck in the first slot on my card....if this test I run tonight comes up just like the others and passes...what does that mean? Does it mean my MotherBoard is bad? If so, I haven't seen many DDR2 boards out there...I'm looking at getting a new board and new cpu and new ram huh? What are your thoughts if this test I do tonight passes and all 4 1gb sticks came back as pass? THanks!

 

[richc46]

I dont understand, if you pass all tests.
With all sticks in
and then
test each stick
Your memory is oK and not the cause of the BSODs we have to move to the next text.

 

[Darren B]

So I should do a mem test will all 4 sticks in as well? ok..well like i said, I have one more test of just the single stick...then i'll test all 4 at once...then I"m not sure what to do after that. Will let u know the results of these last 2 tests

 

[richc46]

Yes, test all sticks for 8 passes
and then test each stick separately for 6 passes each.

 

[Darren B]

I have done all tests...tests of each stick by itself, and of all 4 sticks together...without any errors. Hope there is a next step!?

 

[richc46]

Every single one of your reports indicate memory problems. Usually the reports are not so definitive. You have memory problems. Do you have dual channel memory, sometimes the reuslts of the test are inaccurate in those situations.
You tested all the sticks for 8 passes?
Then you took each stick and tested it alone for 6 passes?
Not very common, but I was able to find a situation where memtest gave false negative
http://www.sevenforums.com/crashes-debugging/72815-bad-ram-passes-memtest.html
From our affiliated Seven Forums

Your results were consistent

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_Seven Forums (1).zip\Seven Forums\Mini081612-03.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18607.x86fre.vistasp2_gdr.120402-0336
Machine Name:
Kernel base = 0x81e3d000 PsLoadedModuleList = 0x81f54c70
Debug session time: Thu Aug 16 21:11:51.842 2012 (GMT-4)
System Uptime: 0 days 0:03:38.814
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 76, {0, 84a70020, 9, 0}
Probably caused by : memory_corruption ( nt!MmDeleteProcessAddressSpace+52 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PROCESS_HAS_LOCKED_PAGES (76)
Caused by a driver not cleaning up correctly after an I/O.
Arguments:
Arg1: 00000000, Locked memory pages found in process being terminated.
Arg2: 84a70020, Process address.
Arg3: 00000009, Humber of locked pages.
Arg4: 00000000, Pointer to driver stacks (if enabled) or 0 if not.
 Issue a !search over all of physical memory for the current process pointer.
 This will yield at least one MDL which points to it.  Then do another !search
 for each MDL found, this will yield the IRP(s) that point to it, revealing
 which driver is leaking the pages.
 Otherwise, set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
 Management\TrackLockedPages to a DWORD 1 value and reboot.  Then the system
 will save stack traces so the guilty driver can be easily identified.
 When you enable this flag, if the driver commits the error again you will
 see a different bugcheck - DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) -
 which can identify the offending driver(s).
Debugging Details:
------------------
 
PROCESS_NAME:  Launcher.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
CUSTOMER_CRASH_COUNT:  3
BUGCHECK_STR:  0x76
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 81ecfa18 to 81f0aabf
STACK_TEXT:  
9c4cebac 81ecfa18 00000076 00000000 84a70020 nt!KeBugCheckEx+0x1e
9c4cec04 8202edb5 84a70020 00000000 00000000 nt!MmDeleteProcessAddressSpace+0x52
9c4cec3c 8206b44f 84a70020 81e1126c 84a70008 nt!PspProcessDelete+0x158
9c4cec58 81e81df0 84a70020 00000000 155a9eec nt!ObpRemoveObjectRoutine+0x13d
9c4cec80 81ef5e5c 00000002 9c4cece8 82081516 nt!ObfDereferenceObject+0xa1
9c4cec8c 82081516 00000000 c000009a 81f3c080 nt!MmFreeAccessPfnBuffer+0x27
9c4cece8 820811f4 00000000 891aec48 00000000 nt!PfpFlushBuffers+0x291
9c4ced7c 82012fe2 81f3c080 997bbcc1 00000000 nt!PfTLoggingWorker+0xaa
9c4cedc0 81e7bf0e 82081144 81f3c080 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MmDeleteProcessAddressSpace+52
81ecfa18 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!MmDeleteProcessAddressSpace+52
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4f79a9be
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  0x76_Launcher.exe_nt!MmDeleteProcessAddressSpace+52
BUCKET_ID:  0x76_Launcher.exe_nt!MmDeleteProcessAddressSpace+52
Followup: MachineOwner
---------

I really feel that it is the memory. Lets make a test. Take two stick and use the computer and see if there is a problem. If not, add a stick and continue the procedure. We will get to the bottom of this.

 

[Darren B]

I appreciate your patience with me and your desire to solve my issue! I'll run my computer with 2 sticks for a few days and see if there is an issue. Like I said before, usually my issue is on shutdown....should I keep my computer on? I usually shut down my computer every night and that could be a problem? I did have something interesting happen yesterday. I was booting up Warcraft online (there is currently a new patch being added to the game so this Background updater runs)...The error came up stating that Blizzard.net updater had stopped working and windows was going to check on the solution to the problem...well instead of closing that dialog box that popped up..I minimized it to the background. I continued to be able to play the game...after about an hour or 2, I quit the game...and returned to the dialog box. As soon as I closed that dialog box, I got the BSOD. Not sure how relevant that is..but just some info. I'll try running with only 2 sticks of Ram and see how that works. I apologize, but I'm not sure if my ram is Dual channel or not (not that literate with it). HOw can I tell? I know its DDR2 RAM .

 

[richc46]

Speccy will tell you everything that you need to know
Speccy - System Information - Free Download
If it happens during shut down, you may want to shut down just a little bit more often. We are trying to see how it operates with two sticks.
Dont worry about the time that this takes. With BSODs, its a little facts and a lot of hunches.
Darren, since the problem happens at shutdown and the reports indicate memory, we may have to administer some other tests to see if there is another problem at shutdown that cause the memory to malfunction.

 

[Darren B]

May be a silly question, but I just don't know. I think when I use 2 sticks of memory, they need to be in alternating slots...so I have a stick in the first slot and in the 3rd, Correct?