I am getting really desperate now and hopefully someone will be able to help me out. Basically I've spent whole day trying to get 4gigs of ram work with my windows vista ultimate on asus striker extreme motherboard (680i - bios 1305) without getting blue screens after a couple of minutes (or even seconds!) after entering into windows. Sometimes I can't even enter windows at all! I doubt it's a purely mobo issue since I'd run the very same 4 gigs (even OCed) on XP for about 3 months without any issues at all. Perhaps my motherboard has some major issues with vista ultimate? I use Q6600 if that makes any difference.
Stuff I've noticed:
1) RAM is certainly not faulty. All 4 components run perfectly on their own in any setups (1-3 at a time). I've also tested every single one of them using prime and memtest. They're flawless (corsair xms2 800mhz).
2) I've tried any voltages and any clocks/memory timings - defaults, OCed and even heavily underclocked. Nothing works.
3) I am currently using VIsta Ultimate SP1 which contains patch KB929777. A fairly well-known hotfix for vista 4gb ram crashes. You've guessed it - no results.
4) I even tried to take away some memory from the system through command prompt. Some users reported that this workaround takes the amount of ram below the unfortunate 4gb threshold and the system becomes stable. Unfortunately, it did not work for me (in fact it appeared as if the command itself did not alter the amount of ram present at all ><)
Here's some additional info:
a) I was using Win XP 32 bit for 3 months without a single BSOD even though I was running 4gb ram all the time (very often OCed might I add). Now I have Windows Vista 32 bit. Interestingly enough, it shows 4gb in windows. Before it crashes, that is.
Vista runs OK with anything less than 4gb. However, 3gb disable dual channel (even on the first pair according to cpu-z) and 2gb is not enough for me with the amount of stuff I run at the same time.c) I only have these 4 sticks. Mind you, I've just finished testing them all on memtest (6 hours), A+C slots on prime for 6 hours and then B+D slots using the other 2 modules. Once again, after 6 hours of full load on prime95 - no probs. Both memory and the slots are flawless!
It appears that WInDBG has some issues with opening the crash files but this is what I did recover. Perhaps you'll be able to draw some conclusions from it. Thanks in advance! (or perhaps you will be able to advise me to use some alternative means of opening this dump since this one does not look very comprehensible. I am a complete noob so please try to keep it straightforward
)Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini012509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
MODULE_NAME: nt
FAULTING_MODULE: 81c18000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a
BUGCHECK_STR: 0x1a_41287
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt+0x70b4e
807f0bec 81c52085 badb0d00 00000000 00000000 nt+0x5aae4
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt+0x3a085
807f0cd8 81c4dcda 00000000 84417740 00000000 nt+0x35ed1
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt+0x35cda
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt+0x1a86ad
00000000 00000000 00000000 00000000 00000000 nt+0x8f686
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+70b4e
81c88b4e 837c242800 cmp dword ptr [esp+28h],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+70b4e
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x81c18000 PsLoadedModuleList = 0x81d25930
Debug session time: Sun Jan 25 19:44:09.599 2009 (GMT+0)
System Uptime: 0 days 0:05:51.721
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 9c0000, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
***
Back to top
