1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Quad Q6600 and Vista x64, Intel chipset, Java, Azureus cause for BSOD?

Discussion in 'Windows Vista' started by Norstedt, Nov 5, 2007.

Thread Status:
Not open for further replies.
Advertisement
  1. Norstedt

    Norstedt Thread Starter

    Joined:
    Nov 5, 2007
    Messages:
    3
    Hi guys,

    I've located the source of the problem but don't know how to fix it.

    I get random BSOD's but they all point to the same error
    Probably caused by : ntkrnlmp.exe witch according to Microsoft has to do with

    CAUSE
    This problem occurs if one or more of the processors in the computer:
    •Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
    •Are damaged or defective.
    •Are operating outside their specified ranges for temperature, power, or other conditions.

    temperature are fine, power should be fine have a 630Watt. You may read the whole bug check and tell me what u think.

    Microsoft (R) Windows Debugger Version 6.8.0004.0 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini110507-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*c:\websymbols*msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6000.16514.amd64fre.vista_gdr.070627-1500
    Kernel base = 0xfffff800`01c00000 PsLoadedModuleList = 0xfffff800`01d9af50
    Debug session time: Mon Nov 5 15:49:35.237 2007 (GMT+1)
    System Uptime: 0 days 3:41:45.140
    Loading Kernel Symbols
    ...................................................................... .....................................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    ********************************************************************** *********
    * *
    * Bugcheck Analysis *
    * *
    ********************************************************************** *********

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, 0, 8, 0}

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

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

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

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000008, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception

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

    FAULTING_IP:
    +0
    00000000`00000000 ?? ???

    EXCEPTION_PARAMETER1: 0000000000000008

    EXCEPTION_PARAMETER2: 0000000000000000

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001dfa0b0
    0000000000000000

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x1E

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    TRAP_FRAME: fffff98001213a90 -- (.trap 0xfffff98001213a90)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffff98000c307f0 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000000 rsp=fffff98001213c20 rbp=fffff98000c30180
    r8=0000000000000000 r9=0000000000000000 r10=fffff80001d68958
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    00000000`00000000 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80001cbab47 to fffff80001c4dbd0

    STACK_TEXT:
    fffff980`012132a8 fffff800`01cbab47 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
    fffff980`012132b0 fffff800`01c4da2e : fffff980`012139e8 fffff980`00c30180 fffff980`01213a90 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x12767
    fffff980`012138b0 fffff800`01c4c825 : 00000000`00000008 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xae
    fffff980`01213a90 00000000`00000000 : 00000000`00000000 fffff980`15038d2b fffffa80`0540ff01 00000000`00000000 : nt!KiPageFault+0x1e5

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+12767
    fffff800`01cbab47 cc int 3

    SYMBOL_STACK_INDEX: 1

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

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 46830f41

    FAILURE_BUCKET_ID: X64_0x1E_W_nt!_??_::FNODOBFM::_string_+12767

    BUCKET_ID: X64_0x1E_W_nt!_??_::FNODOBFM::_string_+12767

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

    2: kd> .trap 0xfffff98001213a90
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffff98000c307f0 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000000 rsp=fffff98001213c20 rbp=fffff98000c30180
    r8=0000000000000000 r9=0000000000000000 r10=fffff80001d68958
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    00000000`00000000 ?? ???

    so what's up!?

    System Spec:
    CPU: QuadCore Intel Core 2 Quad Q6600 @3420GHz
    Mobo: Gigabyte GA-P35C-DS3R
    Mem: Crucial DDR2 BallistiX PC8500 4096MB CL5 ,Kit
    Video: ASUS NVIDIA GeForce 8800 GTS (320 MB)
    HDD: 2* SAMSUNG HD501LJ 500 GB, 7200 RPM, SATA-II, and so on...
    Sound: Wicked
    OS: Windows Vista Ultimate x64
    __________________
    I'm here to learn.
     

    Attached Files:

  2. wendelstam

    wendelstam

    Joined:
    Jan 10, 2008
    Messages:
    2
    Hi

    I also have a Q6600 proc and 4gb Crusial Ballistix DDR2 (but:6400) CL4.

    I get the exact same error, did you find any solution? My was to install the x86 version of vista intead.

    The system seems to crash only when i stared a WebProject in debug mode in Visual Studio 2008. Besides that the computer seemed to run fine.

    Best reagard
    /Johan
     
  3. Norstedt

    Norstedt Thread Starter

    Joined:
    Nov 5, 2007
    Messages:
    3
    Hi, for me the problem was my ram setup. The ram was not paired on the right slots on the motherboard. Try mixing them around if ur not sure they are in there right slots.
     
  4. wendelstam

    wendelstam

    Joined:
    Jan 10, 2008
    Messages:
    2
    Okay, so what you are saying is that even if I have 4 sticks of ram all of them the same sort (2x (2x1gb matched pairs)) I have to pair them as the came I cant mix between the pairs?

    Best regards
    Johan
     
As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/648150

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice