BleepingComputer.com: Repeated BSODs and Crashes

Hello, I have a Home Premium Vista 64 bit on my Lenovo Y550 laptop. I've had problems where my laptop will restart after showing the BSOD. This problem has been happening off and on for about two months and I've done everything to try and fix it including sending my laptop back to Lenovo and many system restores. Lenovo said there was nothing wrong with my laptop when there obviously was and after I received the laptop from them, it worked properly for about a month before the BSODs happened again. Also, recently, wlanext.exe has been failing and I get a message immediately after startup that the LAN Framework has stopped working so I'm wondering if perhaps the crashes are network-related as I exclusively use Wireless Internet. I've also noticed that often times the error codes and messages on the BSODs vary. This problem has been a huge pain and it seems the internet doesn't have the answer so I come to you guys hoping and praying for a solution. Here's my latest memory.dmp debugging report:


Microsoft ® Windows Debugger Version 6.11.0001.404 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 Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Machine Name:
Kernel base = 0xfffff800`01e4c000 PsLoadedModuleList = 0xfffff800`02010dd0
Debug session time: Wed Jan 20 10:48:46.412 2010 (GMT-5)
System Uptime: 0 days 1:28:58.233
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, {fffffa866173bfa8, 2, 1, fffff80001eb2f58}

Page b1680 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 : memory_corruption ( nt!MiRemoveAnyPage+178 )

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

1: 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: fffffa866173bfa8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80001eb2f58, address which referenced memory

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

Page b1680 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

WRITE_ADDRESS: fffffa866173bfa8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemoveAnyPage+178
fffff800`01eb2f58 4c094828 or qword ptr [rax+28h],r9

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: chrome.exe

TRAP_FRAME: fffffa60057b46e0 -- (.trap 0xfffffa60057b46e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa866173bf80 rbx=0000000000000000 rcx=0000000000000078
rdx=fffffa8003c00000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001eb2f58 rsp=fffffa60057b4870 rbp=0000000000000000
r8=0000058000000000 r9=000fffffffffffff r10=0000000000000000
r11=0000000000000028 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!MiRemoveAnyPage+0x178:
fffff800`01eb2f58 4c094828 or qword ptr [rax+28h],r9 ds:4720:bfa8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001ea61ee to fffff80001ea6450

STACK_TEXT:
fffffa60`057b4598 fffff800`01ea61ee : 00000000`0000000a fffffa86`6173bfa8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa60`057b45a0 fffff800`01ea50cb : 00000000`00000001 00000000`00000000 00000000`00001000 fffffa80`02052780 : nt!KiBugCheckDispatch+0x6e
fffffa60`057b46e0 fffff800`01eb2f58 : 00000000`00000020 00000000`00000000 00000000`00000080 fffff700`01080000 : nt!KiPageFault+0x20b
fffffa60`057b4870 fffff800`01ebdefb : 00000000`40000028 fffffa80`06173330 fffffa80`06173040 fffffa80`0344e350 : nt!MiRemoveAnyPage+0x178
fffffa60`057b48d0 fffff800`01ec05b2 : 00000000`00000001 00000000`027b4000 00000000`00000080 00000000`00000060 : nt!MiResolveDemandZeroFault+0x17b
fffffa60`057b4960 fffff800`01ebefd0 : fffff680`00013da0 00000000`00000020 fffff680`00013da0 fffffa80`06173330 : nt!MiResolveProtoPteFault+0x402
fffffa60`057b49e0 fffff800`01ebc9dd : 00000000`00000000 00000000`027b4000 fffffa80`06070060 fffffa80`00000000 : nt!MiDispatchFault+0x190
fffffa60`057b4b40 fffff800`01ea4fd9 : 00000000`00000001 fffffa60`057b4ca0 fffffa80`06173001 00000000`05ae750c : nt!MmAccessFault+0x32d
fffffa60`057b4c20 00000000`70e1ae40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119
00000000`0339f84c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x70e1ae40


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemoveAnyPage+178
fffff800`01eb2f58 4c094828 or qword ptr [rax+28h],r9

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiRemoveAnyPage+178

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a7801eb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiRemoveAnyPage+178

BUCKET_ID: X64_0xA_nt!MiRemoveAnyPage+178

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

Thanks.

You posted only one crash report, which makes almost impossible to make any diagnosis. In any case, it indicates "memory_corruption".

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Here ya go. I really appreciate it. Another thing, I've noticed that Daemon Tools Lite is a bad program to have installed on a computer and I had it but uninstalled it. I don't know if it was a clean full uninstall and if there are still remnant files still on my computer.

==================================================
Dump File : Mini012010-06.dmp
Crash Time : 1/20/2010 7:43:38 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffea00`1b816d0b
Parameter 2 : 00000000`00000001
Parameter 3 : fffffa60`00d4a010
Parameter 4 : 00000000`00000007
Caused By Driver : sptd.sys
Caused By Address : sptd.sys+50b5b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\Mini012010-06.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini012010-05.dmp
Crash Time : 1/20/2010 3:58:14 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffea00`17b4404b
Parameter 2 : 00000000`00000001
Parameter 3 : fffffa60`00d4b010
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\Mini012010-05.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini012010-03.dmp
Crash Time : 1/20/2010 1:42:39 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff960`8911e134
Parameter 2 : 00000000`00000008
Parameter 3 : fffff960`8911e134
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\Mini012010-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini012010-02.dmp
Crash Time : 1/20/2010 11:36:44 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff800`02ec0c30
Parameter 2 : 00000000`00000008
Parameter 3 : fffff800`02ec0c30
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\Mini012010-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini012010-01.dmp
Crash Time : 1/20/2010 10:49:50 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa86`6173bfa8
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`01eb2f58
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\Mini012010-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini011910-04.dmp
Crash Time : 1/19/2010 4:49:47 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffffa60`00fd7a5a
Parameter 3 : fffffa60`01d07fb8
Parameter 4 : fffffa60`01d07990
Caused By Driver : ecache.sys
Caused By Address : ecache.sys+19fd0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\Mini011910-04.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini011910-02.dmp
Crash Time : 1/19/2010 4:13:24 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`020e120c
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`000179f8
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\Mini011910-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini011910-01.dmp
Crash Time : 1/19/2010 4:09:03 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff900`008298e8
Parameter 2 : 00000000`00000000
Parameter 3 : fffff960`0011dae7
Parameter 4 : 00000000`00000000
Caused By Driver : acpi.sys
Caused By Address : acpi.sys+17812920
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\Mini011910-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini011810-01.dmp
Crash Time : 1/18/2010 10:01:48 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffffff`d23345da
Parameter 2 : 00000000`00000001
Parameter 3 : fffff800`02052b73
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\Mini011810-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

Yeah, judging from errors, RAM problem is very likely.

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

Sorry for my lack of knowledge, but how can I find out how many RAM modules my computer has? Based on context, I don't have any external RAM sticks, so I'm guessing I have one? I'm thinking I should go with the memtest but I'll wait for your reply on the RAM modules before I do anything. Really appreciate it Broni.

No reason for being sorry

If nobody changed anything in your laptop, according to this: http://www.crucial.com/store/listparts.asp...8All%20Types%29, you have just one 3, or 4GB RAM stick, so your only option would be to run memtest.

Okay I'll go ahead and run the test. Sadly, after I posted my last reply, my computer crashed again. But I'll run the test and post what happens.

You'll create bootable CD, so you don't have to worry about crashes at this point.

Don't have any blank CDs on me so I'm gonna have to wait to run the memtest. But can you elaborate on the bootable CD? So there won't need to be a fix or replacement done to the RAM module?

Quote

We don't know yet. That's why, you need to run memtest, to find out.

Quote

Just read my memtest manual. It explains everything. If you have any question about some particular step....I'll be around.

By "boot from it", do you mean to restart my computer while leaving the CD in the drive?

Exactly and at some point, you should see this:
Press any key to boot from CD

Broni, on Jan 20 2010, 10:11 PM, said:

Never got prompted with "Press any key to boot from CD". What should I do?

Oh, you made that CD already?

You'll need to enter laptop's BIOS then.
In case of Lenovo, you should press [F1] or [F2] on boot up.
Which one, I can't tell you because it depends on BIOS type.
You can simply try one F1 key, if it doesn't work, try F2 key.
If successful, you should see screen similar to this:



You have look around until you find "boot order".
It'll look similar to this:



Make sure, CD drive is listed first.
If it's not, change it.
Make sure to save settings on exit, by pressing F10 key.

running the memtest now but it's seemed to stop at pass 0% and test 44%. worst part is there are 21760 errors shown. so pretty safe to say this is a RAM problem right?