Too many BSODS :(

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by manojr, Mar 13, 2011.

  1. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    Hi there,
    I have recently installed Win 7 Pro.
    I am having too many BSODs. I have reinstalled couple of times.
    I have also performed memtest86 and had 2 passes ( took about an hour, so i ignored that )
    Windows 7 says all the drivers are upto date but no luck !

    What am i missing? Do i need to replace anything

    Here I have attached the files

    Please help.

    regards,
    Manoj R
     

    Attached Files:

    #1 manojr, Mar 13, 2011
    Last edited: Mar 13, 2011
  2. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Hello and Welcome to windows7forums. : )

    Ram is set slightly wrong - 630Mhz while it's rated 667Mhz 5-5-5-15 1.8v.





    Crash Dumps:

    Code:
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\031311-15756-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.x86fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0x8283e000 PsLoadedModuleList = 0x82986810
    Debug session time: Sun Mar 13 14:43:18.377 2011 (UTC - 5:00)
    System Uptime: 0 days 0:06:00.313
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {c0000005, 828ae655, 91ee3b6c, 0}
    
    Probably caused by : ntkrpamp.exe ( nt!_SEH_epilog4+0 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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: c0000005, The exception code that was not handled
    Arg2: 828ae655, The address that the exception occurred at
    Arg3: 91ee3b6c, Trap Frame
    Arg4: 00000000
    
    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!_SEH_epilog4+0
    828ae655 8b4df0          mov     ecx,dword ptr [ebp-10h]
    
    TRAP_FRAME:  91ee3b6c -- (.trap 0xffffffff91ee3b6c)
    ErrCode = 00000002
    eax=00000102 ebx=00000000 ecx=82a70bca edx=00000000 esi=00000001 edi=00000001
    eip=828ae655 esp=91ee3be0 ebp=91ee3d18 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!_SEH_epilog4:
    828ae655 8b4df0          mov     ecx,dword ptr [ebp-10h] ss:0010:91ee3d08=ffffffff
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 8288143a to 828ae655
    
    STACK_TEXT:  
    91ee3d18 8288143a 00000001 0019f764 00000001 nt!_SEH_epilog4
    91ee3d18 77d86344 00000001 0019f764 00000001 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0019f7b0 00000000 00000000 00000000 00000000 0x77d86344
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!_SEH_epilog4+0
    828ae655 8b4df0          mov     ecx,dword ptr [ebp-10h]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!_SEH_epilog4+0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrpamp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4cc78ed4
    
    FAILURE_BUCKET_ID:  0x8E_nt!_SEH_epilog4+0
    
    BUCKET_ID:  0x8E_nt!_SEH_epilog4+0
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\031311-15896-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Mini Kernel Dump does not have process information
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    
    "nt" was not found in the image list.
    Debugger will attempt to load "nt" at given base 00000000.
    
    Please provide the full image name, including the extension (i.e. kernel32.dll)
    for more reliable results.Base address and size overrides can be given as
    .reload <image.ext>=<base>,<size>.
    Unable to load image nt, Win32 error 0n2
    Unable to add module at 00000000
    Debugger can not determine kernel base address
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.x86fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0x82846000 PsLoadedModuleList = 0x8298e810
    Debug session time: Sun Mar 13 14:46:32.947 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:07.758
    
    "nt" was not found in the image list.
    Debugger will attempt to load "nt" at given base 00000000.
    
    Please provide the full image name, including the extension (i.e. kernel32.dll)
    for more reliable results.Base address and size overrides can be given as
    .reload <image.ext>=<base>,<size>.
    Unable to load image nt, Win32 error 0n2
    Unable to add module at 00000000
    Debugger can not determine kernel base address
    Loading Kernel Symbols
    
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {c63b5773, 2, 1, 828b258f}
    
    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    
    0: 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: c63b5773, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 828b258f, address which referenced memory
    
    Debugging Details:
    ------------------
    
    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
    
    
    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     c63b5773 
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    +3066363961666535
    828b258f 0fbe7357        movsx   esi,byte ptr [ebx+57h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    LAST_CONTROL_TRANSFER:  from 887424ac to 887423d7
    
    STACK_TEXT:  
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    8296cb24 887424ac 888fdda8 8296cbdc 00000000 0x887423d7
    8296cb38 828b016d 888fe000 888fdfd0 5ad6bb70 0x887424ac
    8296cb7c 828b0111 8296fd20 8296cca8 00000001 0x828b016d
    8296cc68 828affce 8296fd20 8296cca8 00000000 0x828b0111
    8296ccdc 828ae34e 000010f7 864bb608 82979280 0x828affce
    8296cd20 828ae178 00000000 0000000e 00000000 0x828ae34e
    8296cd24 00000000 0000000e 00000000 00000000 0x828ae178
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    BUCKET_ID:  CORRUPT_MODULELIST
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\031311-24632-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.x86fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0x82809000 PsLoadedModuleList = 0x82951810
    Debug session time: Sun Mar 13 10:33:36.665 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:13.600
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {80fdf8ec, 2, 0, 8287228c}
    
    Probably caused by : ntkrpamp.exe ( nt!KiSignalThread+9d )
    
    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: 80fdf8ec, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, 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: 8287228c, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82971718
    Unable to read MiSystemVaType memory at 82951160
     80fdf8ec 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiSignalThread+9d
    8287228c 8b8bcc030000    mov     ecx,dword ptr [ebx+3CCh]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  807dfa6c -- (.trap 0xffffffff807dfa6c)
    ErrCode = 00000000
    eax=00000000 ebx=80fdf520 ecx=861dcd01 edx=00000001 esi=861dcd48 edi=861dcc80
    eip=8287228c esp=807dfae0 ebp=807dfae8 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!KiSignalThread+0x9d:
    8287228c 8b8bcc030000    mov     ecx,dword ptr [ebx+3CCh] ds:0023:80fdf8ec=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 8287228c to 8284f81b
    
    STACK_TEXT:  
    807dfa6c 8287228c badb0d00 00000001 8e96d0b0 nt!KiTrap0E+0x2cf
    807dfae8 82872162 80fdf520 00000001 861d5bf8 nt!KiSignalThread+0x9d
    807dfb1c 82845a69 80fdf520 00000001 00000000 nt!KiTryUnwaitThread+0x60
    807dfb3c 828733ad 80fdf520 807dfba4 861d5bf0 nt!KiSignalNotificationObject+0x36
    807dfb80 8287309b 807c3120 00000001 807c4a80 nt!KiTimerWaitTest+0x1e6
    807dfc68 82872fce 807c3120 807dfca8 00000000 nt!KiProcessExpiredTimerList+0x8b
    807dfcdc 8287134e 0000126d 861dcd48 807c8800 nt!KiTimerExpiration+0x25c
    807dfd20 82871178 00000000 0000000e 6d236c5c nt!KiRetireDpcList+0xcb
    807dfd24 00000000 0000000e 6d236c5c 6e770057 nt!KiIdleLoop+0x38
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiSignalThread+9d
    8287228c 8b8bcc030000    mov     ecx,dword ptr [ebx+3CCh]
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!KiSignalThread+9d
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrpamp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4cc78ed4
    
    FAILURE_BUCKET_ID:  0xA_nt!KiSignalThread+9d
    
    BUCKET_ID:  0xA_nt!KiSignalThread+9d
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\031311-17815-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.x86fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0x82851000 PsLoadedModuleList = 0x82999810
    Debug session time: Sun Mar 13 14:44:54.481 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:04.432
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {191c, 2, 1, 828db54d}
    
    Probably caused by : cng.sys ( cng!GatherRandomKey+272 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: 0000191c, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 828db54d, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829b9718
    Unable to read MiSystemVaType memory at 82999160
     0000191c 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiAcquireThreadStateLock+7f
    828db54d 870a            xchg    ecx,dword ptr [edx]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  8a5232ac -- (.trap 0xffffffff8a5232ac)
    ErrCode = 00000002
    eax=0000191c ebx=ffffffff ecx=00000001 edx=0000191c esi=00000000 edi=86b9e498
    eip=828db54d esp=8a523320 ebp=8a523334 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    nt!KiAcquireThreadStateLock+0x7f:
    828db54d 870a            xchg    ecx,dword ptr [edx]  ds:0023:0000191c=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 828db54d to 8289781b
    
    STACK_TEXT:  
    8a5232ac 828db54d badb0d00 0000191c 00000053 nt!KiTrap0E+0x2cf
    8a523334 828f1829 8a523348 9bade6f8 9bade540 nt!KiAcquireThreadStateLock+0x7f
    8a523358 82a8ed11 ab9a8c15 00000000 0001ff68 nt!KeQueryValuesThread+0x6c
    8a5233f4 82a858a6 9bad3098 0001ff68 8a523844 nt!ExpGetProcessInformation+0x1ed
    8a523874 82a8795c 00000005 00000000 00000000 nt!ExpQuerySystemInformation+0x1086
    8a523890 8289443a 00000005 9bad3098 0001ff68 nt!NtQuerySystemInformation+0x76
    8a523890 82892e09 00000005 9bad3098 0001ff68 nt!KiFastCallEntry+0x12a
    8a523918 8859ffdf 00000005 9bad3098 0001ff68 nt!ZwQuerySystemInformation+0x11
    8a523c78 8857d15e 00000000 00000000 8a523c98 cng!GatherRandomKey+0x272
    8a523cdc 8857d1bf 00000000 8a523d00 82a71b2f cng!ReadExternalEntropyIntoPool+0x1a6
    8a523ce8 82a71b2f 85665cb0 00000000 8586ca48 cng!scavengingWorkItemRoutine+0x15
    8a523d00 828bf03b 8586ca48 00000000 84864d48 nt!IopProcessWorkItem+0x2d
    8a523d50 82a5f9df 00000001 ab9a8271 00000000 nt!ExpWorkerThread+0x10d
    8a523d90 829111d9 828bef2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    cng!GatherRandomKey+272
    8859ffdf 83fb20          cmp     ebx,20h
    
    SYMBOL_STACK_INDEX:  8
    
    SYMBOL_NAME:  cng!GatherRandomKey+272
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: cng
    
    IMAGE_NAME:  cng.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc427
    
    FAILURE_BUCKET_ID:  0xA_cng!GatherRandomKey+272
    
    BUCKET_ID:  0xA_cng!GatherRandomKey+272
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\031311-16551-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.x86fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0x8280f000 PsLoadedModuleList = 0x82957810
    Debug session time: Sun Mar 13 15:16:30.008 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:14.944
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000000A, {191c, 2, 1, 8289954d}
    
    Probably caused by : cng.sys ( cng!GatherRandomKey+272 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: 0000191c, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 8289954d, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82977718
    Unable to read MiSystemVaType memory at 82957160
     0000191c 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiAcquireThreadStateLock+7f
    8289954d 870a            xchg    ecx,dword ptr [edx]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    LAST_CONTROL_TRANSFER:  from 828af829 to 8289954d
    
    STACK_TEXT:  
    8a523334 828af829 8a523348 9b8f72b8 9b8f7100 nt!KiAcquireThreadStateLock+0x7f
    8a523358 82a4cd11 ab9c171b 00000000 0001ff68 nt!KeQueryValuesThread+0x6c
    8a5233f4 82a438a6 9b8ec098 0001ff68 8a523844 nt!ExpGetProcessInformation+0x1ed
    8a523874 82a4595c 00000005 00000000 00000000 nt!ExpQuerySystemInformation+0x1086
    8a523890 8285243a 00000005 9b8ec098 0001ff68 nt!NtQuerySystemInformation+0x76
    8a523890 82850e09 00000005 9b8ec098 0001ff68 nt!KiFastCallEntry+0x12a
    8a523918 885a7fdf 00000005 9b8ec098 0001ff68 nt!ZwQuerySystemInformation+0x11
    8a523c78 8858515e 00000000 00000000 8a523c98 cng!GatherRandomKey+0x272
    8a523cdc 885851bf 00000000 8a523d00 82a2fb2f cng!ReadExternalEntropyIntoPool+0x1a6
    8a523ce8 82a2fb2f 85665cb0 00000000 8687e1a0 cng!scavengingWorkItemRoutine+0x15
    8a523d00 8287d03b 8687e1a0 00000000 8484ad48 nt!IopProcessWorkItem+0x2d
    8a523d50 82a1d9df 00000001 ab9c197f 00000000 nt!ExpWorkerThread+0x10d
    8a523d90 828cf1d9 8287cf2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    cng!GatherRandomKey+272
    885a7fdf 83fb20          cmp     ebx,20h
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  cng!GatherRandomKey+272
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: cng
    
    IMAGE_NAME:  cng.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc427
    
    FAILURE_BUCKET_ID:  0xA_cng!GatherRandomKey+272
    
    BUCKET_ID:  0xA_cng!GatherRandomKey+272
    
    Followup: MachineOwner
    ---------
    
    
    
    



    Drivers:

    Code:
    start    end        module name
    82f9c000 82fe4000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
    8d28e000 8d2e8000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
    8f3e0000 8f3f2000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
    8d4e7000 8d4f9000   amdk8    amdk8.sys    Mon Jul 13 19:11:03 2009 (4A5BBF07)
    88379000 88382000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
    882e1000 882ea000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
    882ea000 8830d000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
    887ed000 887f4000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
    8d4b8000 8d4c6000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
    82e28000 82e30000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
    8d927000 8d940000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
    94cc0000 94cde000   cdd      cdd.dll      Mon Jul 13 21:04:18 2009 (4A5BD992)
    883c7000 883e6000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
    82e72000 82f1d000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
    887c1000 887e6000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
    82e30000 82e72000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
    8857f000 885dc000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
    8f3d3000 8f3e0000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
    8d9d2000 8d9db000   cpuz135_x32 cpuz135_x32.sys Wed Jan 19 11:45:17 2011 (4D37151D)
    8e536000 8e543000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
    8d43c000 8d4a0000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
    8d4a0000 8d4b8000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
    8d3f1000 8d3fd000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
    887b0000 887c1000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
    8e51d000 8e536000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
    8e572000 8e583000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
    8e54d000 8e572000   dump_nvstor dump_nvstor.sys Wed May 20 02:44:09 2009 (4A13A6B9)
    8e543000 8e54d000   dump_storport dump_storport.sys Mon Jul 13 19:45:49 2009 (4A5BC72D)
    8e59c000 8e5a6000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
    8f284000 8f33b000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1)
    8f33b000 8f374000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
    8d878000 8d8a2000   fastfat  fastfat.SYS  Mon Jul 13 19:14:01 2009 (4A5BBFB9)
    8f374000 8f37f000   fdc      fdc.sys      Mon Jul 13 19:45:45 2009 (4A5BC729)
    883b6000 883c7000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    88382000 883b6000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
    885ea000 885f3000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
    8877e000 887b0000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D)
    88970000 889a1000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
    82c1f000 82c56000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
    8d55d000 8d57c000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
    8e49e000 8e4ee000   HdAudio  HdAudio.sys  Mon Jul 13 19:51:46 2009 (4A5BC892)
    8d8a2000 8d927000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
    88810000 88818000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
    8f3a1000 8f3b9000   i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B)
    8f3c6000 8f3d3000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
    80bcd000 80bd5000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
    8e407000 8e43b000   ks       ks.sys       Mon Jul 13 19:45:13 2009 (4A5BC709)
    8856c000 8857f000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
    8872c000 88751000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
    8e5e6000 8e5f6000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
    8e5b1000 8e5cc000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
    82e0c000 82e17000   mcupdate mcupdate.dll Mon Jul 13 19:13:13 2009 (4A5BBF89)
    8e5a6000 8e5b1000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
    8f3b9000 8f3c6000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
    882cb000 882e1000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
    8d940000 8d952000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
    8d952000 8d975000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
    8d975000 8d9b0000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
    8d9b0000 8d9cb000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
    8d253000 8d25e000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
    82fed000 82ff5000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
    88541000 8856c000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
    8d3e7000 8d3f1000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
    88800000 88810000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
    88637000 886ee000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
    8f3f2000 8f3fd000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
    8d855000 8d865000   ndisuio  ndisuio.sys  Mon Jul 13 19:53:51 2009 (4A5BC90F)
    8d5dc000 8d5fe000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
    8e48d000 8e49e000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
    8d351000 8d35f000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
    8d2e8000 8d31a000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
    886ee000 8872c000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
    8d25e000 8d26c000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
    8d3dd000 8d3e7000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
    8280f000 82c1f000   nt       ntkrpamp.exe Tue Oct 26 22:30:44 2010 (4CC78ED4)
    88412000 88541000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
    887e6000 887ed000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
    8f282000 8f283040   nvBridge nvBridge.kmd Fri Jul 09 17:10:11 2010 (4C379033)
    8e804000 8f281dc0   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:14 2010 (4C379162)
    8d57c000 8d5c3280   nvmf6232 nvmf6232.sys Thu Aug 12 07:45:46 2010 (4C63DEEA)
    8830d000 88332000   nvstor   nvstor.sys   Wed May 20 02:44:09 2009 (4A13A6B9)
    8d80f000 8d855000   nwifi    nwifi.sys    Mon Jul 13 19:51:59 2009 (4A5BC89F)
    8d321000 8d340000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
    8f389000 8f3a1000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E)
    8824a000 8825b000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
    8d9cb000 8d9d2000   parvdm   parvdm.sys   Mon Jul 13 19:45:29 2009 (4A5BC719)
    88215000 8823f000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
    882b6000 882bd000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
    882bd000 882cb000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
    885dc000 885ea000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
    94629000 946c0000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
    8e4ee000 8e51d000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
    82e17000 82e28000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
    8d5c4000 8d5dc000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
    8d400000 8d418000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
    8d418000 8d42f000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
    883e6000 883fd000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
    8d39c000 8d3dd000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
    8d42f000 8d439000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20)
    8d23b000 8d243000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
    8d243000 8d24b000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
    8d24b000 8d253000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
    88751000 8877e000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
    8d865000 8d878000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
    946c0000 946ca000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
    8f37f000 8f389000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
    8d35f000 8d379000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
    889e9000 889f1000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
    94747000 94798000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
    946f8000 94747000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
    946ca000 946eb000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
    88332000 88379000   storport storport.sys Mon Jul 13 19:45:58 2009 (4A5BC736)
    8f3fd000 8f3fe380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
    88827000 88970000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
    946eb000 946f8000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
    8d283000 8d28e000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
    8d26c000 8d283000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
    8d38c000 8d39c000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
    94c90000 94c99000   TSDDD    TSDDD.dll    Mon Jul 13 20:01:40 2009 (4A5BCAE4)
    8d4c6000 8d4e7000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
    8e43b000 8e449000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
    8e59a000 8e59b700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
    8d54e000 8d55d000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
    8e449000 8e48d000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
    8d4f9000 8d503000   usbohci  usbohci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
    8d503000 8d54e000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
    8e583000 8e59a000   USBSTOR  USBSTOR.SYS  Mon Jul 13 19:51:19 2009 (4A5BC877)
    8823f000 8824a000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
    887f4000 88800000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
    8d20d000 8d22e000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
    889a1000 889a9380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
    8825b000 8826b000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
    8826b000 882b6000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
    889aa000 889e9000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
    8d340000 8d351000   vwififlt vwififlt.sys Mon Jul 13 19:52:03 2009 (4A5BC8A3)
    8d379000 8d38c000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
    8d22e000 8d23b000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
    82f1d000 82f8e000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
    82f8e000 82f9c000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
    8d31a000 8d321000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
    94a30000 94c7b000   win32k   win32k.sys   Tue Jan 04 22:37:16 2011 (4D23E76C)
    82fe4000 82fed000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
    8e5cc000 8e5e6000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)
    94798000 947b8480   WUDFRd   WUDFRd.sys   Mon Jul 13 19:50:44 2009 (4A5BC854)
    
    Unloaded modules:
    88818000 88825000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000D000
    889f1000 889fb000   dump_storpor
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000A000
    88600000 88625000   dump_nvstor.
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00025000
    88625000 88636000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00011000
    
    
     
  3. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    Hey thank you very much.
    How do i change that value?

    regards,
    ManojR
     
  4. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    In the bios > DRAM frequency.
     
  5. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    Hi there,
    thanks for your help but I cant find DRAM frequency in my bios at all.
    There's only CPU frequency that has the word "Frequency".

    or i dont know if i am not being able to find it?

    please advice

    regards,
    ManojR
     
  6. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    - see your bios manual
    - load setup/optimized defaults
     
  7. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    Hi i have now load optimized defaults.
    how do i make sure the RAM is running at relevant speed as you suggested?

    regards,
    ManojR
     
  8. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Let's see, re-attach your new CPU-Z MEMORY snap shot.
     
  9. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    here they are

    thank you
     

    Attached Files:

  10. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    Just had a restart again :(
    [ replying from my laptop atm ]

    Dont think the RAM bios thing worked?
     
  11. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Your RAM is 602 Mhz right now. You need 667.
     
  12. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    Hi there again,

    The dram frequency fluctuates between
    201.0
    200.9
    and 315.8

    Does it need to be static?
    I do*not* have much knowledge about dram frequency

    regards,
    ManojR
     
    #12 manojr, Mar 13, 2011
    Last edited: Mar 13, 2011
  13. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    1-3 Mhz fluctuation is OK. But it should be close to the rated frequency.
     
  14. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    The only place where I can actually set some kind of freuency on m bios is under "Performance booster zone =>> Cpu Frequency - which is set to 200 " at the moment . There 's DRAM configuration as well but it has only got settings such as memory timings and some other value.

    Do you think I need to update my bios ? and see if it works that way ?
     
  15. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    I have just managed to change a value in bios to Maxmemchk and that unlocked one of the features which let me set DDR 667 value. I hope this works
     
  16. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Well, reattach the memory snip.
     
  17. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    hi there,
    Again from my laptop.
    by the time i get the screen shots ready to upload anoter Blue screen appears.

    KERNEL_MODE_EXCEPTION_NOT_HANDLED ( win32k.sys)

    here's the attached

    I have noticed the the memory fluctuation on CPU happens when my computer is busy or idle. at idle its stingat 200.9
    and when its bit busier it goes upto 333

    This is giving me too much headache.
    What do you suggest?

    I do apologize as we're getting no where.
    I am very thankful for your help and time

    ManojR
     

    Attached Files:

  18. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    No problem. : )



    I'm just not sure it is a good idea if it goes from 200 to 333. If you have any overclocking setup in the bios or an overclocking utility, then disable it. No, it's not supposed to jump that much.
     
  19. manojr

    manojr New Member

    Joined:
    Mar 13, 2011
    Messages:
    28
    Likes Received:
    0
    Hi,

    I have not installed any such over clocking utility
    I just made some changes in BIOS earlier to get the DRAM frequency in line.
    I might try putting some new RAM
    Running out of options here.

    eeekk !!
     
  20. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Go ahead try it.
     

Share This Page

Loading...