BSOD "dumping phisycal memory to disk" 4GB RAM issue ?!

[BizkitBoy]

Hello, everyone. I'm new here and the only reason I was forced to access this forum is because of the multiple and continuous BSOD's i keep receiving. I upgraded my system and also upgraded to Windows 7 Ultimate (x64) from XP SP3 (x86). I did a clean install: formatted my 20GB partition and installed Win 7 (with both sticks of RAM installed). Installed available updates for Windows + all my necessary software. So far, so good. I don`t remember exactly when (the next day, I guess) I started receiving BSOD's. I tried multiple settings in BIOS: tried everything on Auto, tried increasing RAM voltage, tried setting the default XMP profile for my RAM... same results, same BSOD's: dumping phisycal memory to disk.

Tried a different approach: did another fresh install... same BSOD's. Then tried installing ONLY Windows updates (the important ones)... same BSOD's. So that rules out driver issues.

I have 0503 BIOS version and when I tried to update to the latest 0504 from AsusTek official website, I received an error: boot (something) doesn`t match, or something like that. Anyway, they state out what is fixed in the 0504 version and I don`t think that fix might help me.

Also, I used MemTest86+ v4.00 on each of my RAM sticks (separately) and everything is ok, my RAM is not the issue here.

I will attach the minidump files. Already looked over them with WhoCrashed and everytime ntoskrnl.exe is to blame.

Right now I have only one memory stick installed, so I come with the logical question... is Windows 7 (x64) not optimized for 4GB RAM?

P.S. I know these issues have been discussed before, but I wanted to point out my exact problem in a new thread. Sorry for the huge post, just wanted to make everything clear.

Thank you in advance.

 

[torrentg]

Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

"0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred."

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


Loading Dump File [E:\Temp\Rar$DI07.984\110509-23540-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02815000 PsLoadedModuleList = 0xfffff800`02a52e50
Debug session time: Thu Nov  5 02:18:00.780 2009 (GMT-5)
System Uptime: 0 days 0:12:11.262
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8000289415f, fffff8800317ea78, fffff8800317e2d0}

Probably caused by : ntkrnlmp.exe ( nt!KxStartSystemThread+16 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000289415f, The address that the exception occurred at
Arg3: fffff8800317ea78, Exception Record Address
Arg4: fffff8800317e2d0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExpWorkerThread+10f
fffff800`0289415f ffd3            call    rbx

EXCEPTION_RECORD:  fffff8800317ea78 -- (.exr 0xfffff8800317ea78)
ExceptionAddress: fffff8000289415f (nt!ExpWorkerThread+0x000000000000010f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800317e2d0 -- (.cxr 0xfffff8800317e2d0)
rax=0000000000000001 rbx=ff00f88004182510 rcx=fffffa8005701410
rdx=0000026500000000 rsi=fffffa80039f9b60 rdi=fffffa8005701410
rip=fffff8000289415f rsp=fffff8800317ecb0 rbp=fffff80002a2a5a0
 r8=0000000000000000  r9=000000000035b3dd r10=000000000000d6f7
r11=fffffa8005701c10 r12=fffffa8005701c10 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExpWorkerThread+0x10f:
fffff800`0289415f ffd3            call    rbx {ff00f880`04182510}
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002abd0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!KxStartSystemThread+16
fffff800`02865486 48c7c10e000000  mov     rcx,0Eh

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002b2a166 to fffff8000289415f

STACK_TEXT:  
fffff880`0317ecb0 fffff800`02b2a166 : 00000000`000189c0 fffffa80`039f9b60 00000000`00000080 fffffa80`039ce040 : nt!ExpWorkerThread+0x10f
fffff880`0317ed40 fffff800`02865486 : fffff880`02f63180 fffffa80`039f9b60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0317ed80 00000000`00000000 : fffff880`0317f000 fffff880`03179000 fffff880`0317e9f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KxStartSystemThread+16

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff8800317e2d0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!KxStartSystemThread+16

BUCKET_ID:  X64_0x7E_nt!KxStartSystemThread+16

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

You can start trying to alleviate problems by following the suggestions in the above link.

Make sure you are using latest video driver too.

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


Loading Dump File [E:\Temp\Rar$DI42.690\110509-18626-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02867000 PsLoadedModuleList = 0xfffff800`02aa4e50
Debug session time: Wed Nov  4 17:26:58.415 2009 (GMT-5)
System Uptime: 0 days 0:06:30.898
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800029564e5, fffff88007a70ed0, 0}

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

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800029564e5, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007a70ed0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt! ?? ::FNODOBFM::`string'+40819
fffff800`029564e5 498b1c24        mov     rbx,qword ptr [r12]

CONTEXT:  fffff88007a70ed0 -- (.cxr 0xfffff88007a70ed0)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80053ee218
rdx=0000000000000000 rsi=fffffa80053ee1d0 rdi=0000000000000000
rip=fffff800029564e5 rsp=fffff88007a718b0 rbp=fffff8a002985d00
 r8=fffff8a002741200  r9=00000000000000bc r10=00000000000000bc
r11=fffff88007a71978 r12=00ff000000000000 r13=fffffa8003db3060
r14=fffffa8003db3100 r15=fffff8a002985d40
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt! ?? ::FNODOBFM::`string'+0x40819:
fffff800`029564e5 498b1c24        mov     rbx,qword ptr [r12] ds:002b:00ff0000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  pcalua.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800029564e5

STACK_TEXT:  
fffff880`07a718b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40819


FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+40819
fffff800`029564e5 498b1c24        mov     rbx,qword ptr [r12]

SYMBOL_STACK_INDEX:  0

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff88007a70ed0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!_??_::FNODOBFM::_string_+40819

BUCKET_ID:  X64_0x3B_nt!_??_::FNODOBFM::_string_+40819

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

 

[BizkitBoy]

My video drivers are up-to-date.

Regarding the link, out of all the posible reasons, here`s how I stand:

Make sure you have enough disk space. - I do. 20GB of partition are enough
If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. - not the case for me, since I experienced the BSOD after fresh install and with no drivers and no software installed
Try changing video adapters. - tried, but without success
Check with your hardware vendor for any BIOS updates. - as I explained in my first post, i have 0503 BIOS version and the latest one is 0504 with this fix: "Fix system don't show new cpu warning when start up and shut down with two video cards". I don`t think a BIOS update helps at all. Besides, I tried it and it doesn`t work
Disable BIOS memory options such as caching or shadowing. - this is the only thing I haven`t managed to check because I simply can`t find it in my BIOS settings... any ideas where to look for it in an Asus motherboard BIOS?

 

[torrentg]

Try the bios update. No idea of settings. Best hopes to troubleshoot further is running latest bios.

 

[BizkitBoy]

First of all, thank you torrentg and H2SO4 for your replies (torrentg here and H2SO4 at this thread). I did try a BIOS update even before you guys suggested that I do, but without luck. I figured it`s somewhat "safer" to do this directly from BIOS, with the EZ Utility Asus has integrated directly into the BIOS. Like I posted above, I received an error "boot entry does not match" or something like that. I`ve got 2 more options... 1. redownload the .ROM file from Asus's website and try again, or 2. try installing the BIOS update using Asus Update Tool from Windows (if it works). If these don`t work... then the guys at Asus are complete morons. I`ve posted *a thread on their forums* 2 days ago and no one even cares to answer... I guess they don`t care about technical issues their customers have. This was my first Asus motherboard and I think it will be my last... I should have sticked to Intel motherboards because I`m not really the overclocking type of guy. Live and learn, I guess :huh:

 

[BizkitBoy]

And I`m back... wish I weren`t Don`t know why, but I redownloaded the BIOS update from Asus's website and this time I was able to update to the latest BIOS by using the EZ Flash 2 utility which is directly integrated in the BIOS. Put back my other 2GB memory stick and guess what? BSOD after 10-15min... so updating the BIOS didn`t do the trick for me...

I will attach the minidump file in hope it might give you guys any clue to what I should do next. I, for one, am totally out of ideas... except trying the x86 version.

 

[H2SO4]

And I`m back... wish I weren`t Don`t know why, but I redownloaded the BIOS update from Asus's website and this time I was able to update to the latest BIOS by using the EZ Flash 2 utility which is directly integrated in the BIOS. Put back my other 2GB memory stick and guess what? BSOD after 10-15min... so updating the BIOS didn`t do the trick for me...

I will attach the minidump file in hope it might give you guys any clue to what I should do next. I, for one, am totally out of ideas... except trying the x86 version.

This is a bizarre crash that is quite suggestive of some sort of hardware issue, though it doesn't immediately point at the RAM.

Are you quite sure this machine is not overclocked? Does relaxing the clock rates to something extremely conservative (just as a test) make any difference?

 

[BizkitBoy]

This machine is definetly not overclocked. The only thing that I noticed in BIOS is that because the RAM runs at 1600MHz, the FSB has also been automatically raised to 1600MHz, but from what I know, it`s normal. I don`t suppose it has anything to do with the fact that my CPU is a Q6600 which normaly has FSB 1066MHz.

For the past 2 hours I`ve been trying so many BIOS RAM latency options, that my eye-balls are popping out of my head It simply refuses to run at 1333MHz 9-9-9-24 which is the JEDEC #4 standard... even when I set manually these options, the system automatically reverts to a ~900MHz with that latency. I managed to make it run at 1066MHz 8-8-8-22, the JEDEC #3 standard.

I don`t know what to belive anymore... is the RAM idioticaly optimized for 1600MHz 8-8-8-24?

 

[torrentg]

Bump the voltage on the ram (Vdimm) to 1.65v.

Kingston Technology Company - HyperX DDR3 -

If the Q6600 is intended to run at 1066 MHz and your fsb is 1600 MHz, there is major overclocking going on (~ 50%!!!). 1600-1066=534 | 534/1066 = .500938086 (Good call H2SO4!)

http://ark.intel.com/Product.aspx?id=29765

Use CPU-Z to help sort things out and adjust bios accordingly.

 

[BizkitBoy]

Already tried setting the RAM manually to 1600MHz with 8-8-8-24 and 1.65V. I get the same BSOD's. Bumped the voltage higher to 1.76V... same result. And above 1.8V, Win7 refuses to boot. I get BSOD immediatly after Win7 logo.

I`ve been using CPU-Z to see exactly how everything is adjusted. I`ll keep trying, but I have a feeling that I need to stick to 1066MHz CL8 for RAM for a stable system... which leads me to say that I`ve made a very stupid decision going for DDR3 with LGA775.

Thanks for all the help, guys. I really appreciate it!

P.S. Question: if I should upgrade to a more powerfull processor from the Q9xxx family which has FSB 1333MHz... any chance of making the BSOD's go away and run my RAM at their standard 1600MHz CL8 1.65V? I`m asking because you guys have a lot more experience than I do. Just want to know if a more powerfull CPU would make a difference.
Thanks!

 

[BizkitBoy]

I`ve found someone who can sell me a Q9550 (stepping E0) which has FSB 1333Mhz. Do you belive I will be able to easily clock it`s FSB to 1600Mhz and have a stable system? I`d really appreciate an answer because today I am supposed to make the transaction and I don`t want to be throwing money again.

 

[H2SO4]

I`ve found someone who can sell me a Q9550 (stepping E0) which has FSB 1333Mhz. Do you belive I will be able to easily clock it`s FSB to 1600Mhz and have a stable system? I`d really appreciate an answer because today I am supposed to make the transaction and I don`t want to be throwing money again.

I cannot answer your question but I'd caution you against spending money on the assumption that any given OCed combination will be "stable". For what it's worth, I'd personally be inclined to either work out the problems in the hardware I've already bought, or return it for a refund and then worry about what else to buy.

 

[BizkitBoy]

Just wanted to let you guys know that the BSOD had nothing to do with Win7. It was an overclocking issue that made the system unstable and made Win7 crash. I thought that if the motherboard was (theoretically) made to get the FSB up to 1600, then I`d have no problem setting that FSB so I could run my RAM at 1600Mhz as well. I was wrong. The motherboard (Asus P5E3 Pro) is just too god damn stupid to make that jump possible. I did get that Q9550 I was talking about and still couldn`t make the system stable at FSB 1600. Returned it and decided to stick with my Q6600 which I was able to get to FSB 1333 so I could at least run my RAM at 1333Mhz (rather than 1066Mhz). It`s stable now. I ran Prime95 for 1h 30min and all was well. I know I`m supposed to run it for 24h or maybe a bit less, but the CPU reached 66* (degrees) and I decided to stop it... I considered it endured enough

So there you have it. Bottom line, a hardware overclocking issue that made the OS unstable and crash with BSOD.

Thank you guys for all the help and advices. To be honest, I don`t think I would`ve reached this conclusion if it weren`t for you. It`s because of you I started to dig deeper into the issue and with some help from a somebody I met that knows a hell lot more about overclocking, I was able to reach this final conclusion. This forum is indeed awesome and very helpful!