BSoD Problems

The fact that Memtest shows errors indicates that you have a RAM problem. That problem can be one or more bad sticks of RAM, RAM sticks incompatible with each other, RAM incompatible with the motherboard, a bad RAM slot, or a bad memory controller. Remove all of your RAM sticks except the one in the first slot. Run Memtest on that stick. If it passes, remove it, mark it as good and test another stick in the same slot. Repeat until you have tested all of your sticks. If you find a bad stick, mark it as bad. Run your computer with just one RAM stick and see how it does.

Next take a known good stick and test each of your RAM slots with this stick. I know this is time consuming and tedious. If you find a bad slot, you will know not to use that slot. Post back with your results.

I did look at your dump and it is memory management error. It does not indicate any specific cause.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0300e000 PsLoadedModuleList = 0xfffff800`0324be50
Debug session time: Wed Dec 29 08:39:04.657 2010 (GMT-5)
System Uptime: 0 days 2:32:45.202
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800361a970, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa800361a970
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  hpqtra08.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030f1f9e to fffff8000307e740

STACK_TEXT:  
fffff880`0824b968 fffff800`030f1f9e : 00000000`0000001a 00000000`00041790 fffffa80`0361a970 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0824b970 fffff800`030c00da : 00000000`00000000 00000000`04970fff fffffa80`00000000 fffffa80`04596870 : nt! ?? ::FNODOBFM::`string'+0x33906
fffff880`0824bb30 fffff800`0307d993 : ffffffff`ffffffff 00000000`0008e310 00000000`0008e308 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`0824bc20 00000000`76fcff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fcff3a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33906
fffff800`030f1f9e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33906

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906

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

0: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2527
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 37 Stepping 5
ProcessorNameString = REG_SZ Intel(R) Core(TM) i5 CPU       M 460  @ 2.53GHz
Update Signature = REG_BINARY 0,0,0,0,2,0,0,0
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 200000000

evilwart said:

I tried the Driver Verifier again yesterday and it's working this time so I'm gonna let that run for 36 hours over the next couple of days and see if that can point to a bad driver.

Be sure to upload any Verifier enabled dumps. If the dumps point to Windows system files, you can stop Verifier.

In regards to the RAM, is the removal of RAM sticks an easy process? If it's a simple enough process, I'll give it a go after the Driver Verifier. I just don't want to mess up my laptop.

I am not familiar with your laptop. Many laptops have a door on the bottom that gives access to the memory without having to take the laptop apart. If your computer is still under warranty, you don't want to take it apart. And, if it is, I would let Acer deal with the RAM problem.

Also, I've just checked Acer's website and my laptop's BIOS isn't the latest version. Could that be what is causing the BSoDs?

I don't lightly recommend flashing the BIOS. If not done correctly, it can turn you computer into a useless paper weight. There is a definite risk involved, albeit not a great risk. Generally, I recommend flashing the BIOS when the BIOS update addresses a specific problem that the computer is experiencing or when the manufacturer recommend the BIOS upgrade. Since I do not know what the latest addresses or corrects, I can't give you an answer. There are some BIOS updates that correct memory problems. Without all of the facts, I recommend that you solve the RAM problem first.

Thanks for your help so far.

You are very welcome.

You are certainly welcome for the help. No BSOD's using Verifier is a good sign. It means Verifier found no faulty drivers. Good job of running it.

If there is a seal on the door that opens to the RAM, you definitely do not want to break it. If there is no seal, accessing the RAM probably does not invalidate the warranty. That said, as inconvenient as it may be, since the computer under warranty, I would let Acer handle it. I think you have made a good decision. Acer will also flash the BIOS if that is necessary. Please post back and update us after Acer looks at the RAM and tell us what they have done.