Vista Basic 64Bit 6GB RAM Crashes

Hi,

I'm new to windows vista having recently bought a new computer and am experiencing a range of different BSODs. They range from issues to do with CACHE_MANAGER to SYSTEM_SERVICE_EXCEPTION and normally take place when performing memory intensive activities (such as playing games or using music composition software). Doing a small amount of research into these messages around the forums seems to indicate that they are a memory error, although that neither helps or narrows down the problem . I have limited knowledge with computer diagnostics but am more then capable of following instructions.

I have also started to collect as much information about the problem as suggested on many threads, my most recent crash data sets are contained below:

DATE: 22/9/09
Time: 4:10

SYSTEM_SERVICE_EXCEPTION

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.2
Locale ID: 3081

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80001E8C860
BCP3: FFFFFA60099AA0F0
BCP4: 0000000000000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini092209-02.dmp
C:\Users\Lucien\AppData\Local\Temp\WER-39359-0.sysdata.xml
C:\Users\Lucien\AppData\Local\Temp\WERD70C.tmp.version.txt

Read our privacy statement:
Microsoft Online Crash Analysis

DATE: 24/9/09
Time: 1:10

SYSTEM_SERVICE_EXCEPTION

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.2
Locale ID: 3081

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C000001D
BCP2: FFFFF800020FC3EF
BCP3: FFFFFA60085B3A60
BCP4: 0000000000000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini092209-03.dmp
C:\Users\Lucien\AppData\Local\Temp\WER-41574-0.sysdata.xml
C:\Users\Lucien\AppData\Local\Temp\WER2B63.tmp.version.txt

Read our privacy statement:
Microsoft Online Crash Analysis

Any help solving this problem would be greatly appreciated as these BSOD problems occour every 30 mins on average when using an application as listed above. The computer is able to run vista and browse the internet with no issues for extended periods, only when applications that use more computing power are used does the BSOD problem occur. Also a software rather then hardware fix is much preferred as my experience with computers on a hardware level is limited.

Any help is much appreciated,

Lucien

Lucian

could you go into c:\windows\minidump, zip the dump file (*.dmp) and upload it to us using the attachment icon (shaped like a paperclip) in the reply form

thanks

ken

Sure, here it is:

View attachment 15956

It has 116 Items...

Okay maybe rather then run through every single problem(?) we just start with the most recent. It was a PAGE_FAULT_IN_NONPAGED_AREA and im attaching the dump. http://www.vistax64.com/attachment.php?attachmentid=16048&stc=1&d=1254051426 I ran the windows memory test but it didn't come up with any errors. I'll try the memtest86+ next and hopefully get some more results from that one.

Lucien

have you been having sidebar problems lately?

this last one was cuased by sidebar writing a hard fault to a non paged memory area. It took ntkrnlmp with it.

how much memory? have you run a mem diaxnosis?

Just to be sure you want to run a system file check SFC /scannow from an elevated command prompt to verify the system files

ken


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Mini092709-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18295.amd64fre.vistasp1_gdr.090721-0152
Machine Name:
Kernel base = 0xfffff800`01e15000 PsLoadedModuleList = 0xfffff800`01fdadb0
Debug session time: Sun Sep 27 07:24:56.513 2009 (GMT-4)
System Uptime: 0 days 6:56:00.612
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffffe4, 0, fffff80001e84860, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ExQueryPoolUsage+110 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffe4, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80001e84860, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000203e080
ffffffffffffffe4

FAULTING_IP:
nt!ExQueryPoolUsage+110
fffff800`01e84860 8379e400 cmp dword ptr [rcx-1Ch],0

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: sidebar.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffffa6008c8e7c0 -- (.trap 0xfffffa6008c8e7c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000c00 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa6008c8ea7c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001e84860 rsp=fffffa6008c8e950 rbp=fffffa6008c8eca0
r8=fffffa6008c8ea78 r9=fffff80001fa7a10 r10=fffffa60005edf60
r11=fffffa6008c8ea60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!ExQueryPoolUsage+0x110:
fffff800`01e84860 8379e400 cmp dword ptr [rcx-1Ch],0 ds:ffffffff`ffffffe4=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001e78671 to fffff80001e69650

STACK_TEXT:
fffffa60`08c8e6c8 fffff800`01e78671 : 00000000`00000050 ffffffff`ffffffe4 00000000`00000000 fffffa60`08c8e7c0 : nt!KeBugCheckEx
fffffa60`08c8e6d0 fffff800`01e681d9 : 00000000`00000000 00000000`00000001 fffff800`01f8eb00 00000000`00000000 : nt!MmAccessFault+0x1371
fffffa60`08c8e7c0 fffff800`01e84860 : 00000000`04d1d2c0 fffff800`020e02ec 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119
fffffa60`08c8e950 fffff800`020e02ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`04d1d2c0 : nt!ExQueryPoolUsage+0x110
fffffa60`08c8e960 fffff800`01e690f3 : fffffa80`09c1bac0 00000000`04d1d500 00000000`04d1f5a8 00000000`00000000 : nt!NtQuerySystemInformation+0x64c
fffffa60`08c8ec20 00000000`779a5dda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`04d1d1f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779a5dda


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExQueryPoolUsage+110
fffff800`01e84860 8379e400 cmp dword ptr [rcx-1Ch],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!ExQueryPoolUsage+110

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a65b149

FAILURE_BUCKET_ID: X64_0x50_nt!ExQueryPoolUsage+110

BUCKET_ID: X64_0x50_nt!ExQueryPoolUsage+110

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

I tried running the sfc /scannow command using this link to show me how (since I didn't previously know how):

SFC /SCANNOW Command - System File Checker - Windows 7 Forums

However when I did this the computer told me that

"You must be an administrator running a console session in order to use the sfc utility."

IL try to track down some information on this problem while awaiting your reply.

I also just had a MEMORY_MANAGEMENT BSOD when playing Resident Evil 5 should i post the crash dump up for that as well??

Lucien said:

I tried running the sfc /scannow command using this link to show me how (since I didn't previously know how):

SFC /SCANNOW Command - System File Checker - Windows 7 Forums

However when I did this the computer told me that

"You must be an administrator running a console session in order to use the sfc utility."

IL try to track down some information on this problem while awaiting your reply.

I also just had a MEMORY_MANAGEMENT BSOD when playing Resident Evil 5 should i post the crash dump up for that as well??

Click to expand...

'You must be an administrator' just means you need to right click the cmd icon and select 'Run as administrator' then type in sfc /scannow.

After the sfc /scannow finishes, type this into the command prompt to access the log:

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >>%userprofile%\desktop\sfcdetails.txt

That will save a text document with the results of the scan. Please upload that here.

Also, please upload your latest dump so I can debug for you

i would go with your first thought and test your ram , remove all but one stick and see if the problme persists then swap out the sticks one by one

6 gig is an odd ammount or DDR2 some motherboard controllers dont like it , try 4 gig , itll run in dual channel then too making it a little faster (as long as its in the correct slots

it also could be a voltage issue , could you list your mobo make model and the make and moel of your ram

with uch a wide range of dumps id suspect hardware , as you have already summised

edit just seen your system specs brb

ive just had a quick look , your ram runs at 1.8v which is standard so i see no possible issues there , maybe it could be upped by .1 of a volt (thats POINT1 not 1 ) if the issue persists as threee sticks may be sapping a bit too much juice

so you could try swapping it out as i mentioned and run memtest .. linky .. Memtest86 - Download Page (plenty of info of off google on how to run it) you may also have to use multipliers to slow your ram down a bit (in your bios) or it may just be a case of slackening up the timings a little (we can look into this if it turns out to be a ram issue) good luck