locked
BSOD event ID 1001 Bugcheck 0x000000d1 (0x00000000000000ff, 0x0000000000000002, 0x0000000000000008, 0x00000000000000ff). RRS feed

  • Question

  • Hi

    I am facing a problem with Windows 8 64bit.

    I have a Complete memory Dump file of my BSOD.

    And I have checked my memory.

    Srry for my badly english

    Below is my BSOD report:

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


    Loading Dump File [C:\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available

    Symbol search path is: SRV*C:\sym*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
    Machine Name:
    Kernel base = 0xfffff801`a9816000 PsLoadedModuleList = 0xfffff801`a9ae2a20
    Debug session time: Tue Jun  4 19:42:39.177 2013 (UTC + 2:00)
    System Uptime: 0 days 4:02:57.861
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`7f213018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {ff, 2, 8, ff}

    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000000000000ff, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: 00000000000000ff, address which referenced memory

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


    READ_ADDRESS:  00000000000000ff

    CURRENT_IRQL:  2

    FAULTING_IP:
    +0
    00000000`000000ff ??              ???

    PROCESS_NAME:  iexplore.exe

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  AV

    TAG_NOT_DEFINED_c000000f:  FFFFF801A9782FB0

    TRAP_FRAME:  fffff801a9782940 -- (.trap 0xfffff801a9782940)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff801a9b0e180
    rdx=fffffa80082e1b00 rsi=0000000000000000 rdi=0000000000000000
    rip=00000000000000ff rsp=fffff801a9782ad8 rbp=fffff801a9782b29
     r8=fffffa8008737b00  r9=0000000000000000 r10=0000000000000000
    r11=fffff801a9782b08 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    00000000`000000ff ??              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff801a986f769 to fffff801a9870440

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00000000`000000ff ??              ???

    STACK_TEXT: 
    fffff801`a97827f8 fffff801`a986f769 : 00000000`0000000a 00000000`000000ff 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff801`a9782800 fffff801`a986dfe0 : 00000000`00000008 fffff801`a98a00c9 fffffa80`077b5c00 fffff801`a9782940 : nt!KiBugCheckDispatch+0x69
    fffff801`a9782940 00000000`000000ff : 00000000`00000005 fffffa80`087de640 fffff801`a9782ba9 fffff880`01951180 : nt!KiPageFault+0x260
    fffff801`a9782ad8 00000000`00000005 : fffffa80`087de640 fffff801`a9782ba9 fffff880`01951180 fffff801`a9a9c000 : 0xff
    fffff801`a9782ae0 fffffa80`087de640 : fffff801`a9782ba9 fffff880`01951180 fffff801`a9a9c000 fffff801`a9b0e180 : 0x5
    fffff801`a9782ae8 fffff801`a9782ba9 : fffff880`01951180 fffff801`a9a9c000 fffff801`a9b0e180 00000000`00000000 : 0xfffffa80`087de640
    fffff801`a9782af0 fffff880`01951180 : fffff801`a9a9c000 fffff801`a9b0e180 00000000`00000000 00000000`00000000 : 0xfffff801`a9782ba9
    fffff801`a9782af8 fffff801`a9a9c000 : fffff801`a9b0e180 00000000`00000000 00000000`00000000 fffff801`a98a00c9 : 0xfffff880`01951180
    fffff801`a9782b00 fffff801`a9b0e180 : 00000000`00000000 00000000`00000000 fffff801`a98a00c9 fffff880`018dc180 : nt!ExNode0
    fffff801`a9782b08 00000000`00000000 : 00000000`00000000 fffff801`a98a00c9 fffff880`018dc180 fffff801`a9a9c000 : nt!KiInitialPCR+0x180


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!KiPageFault+260
    fffff801`a986dfe0 440f20c0        mov     rax,cr8

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  nt!KiPageFault+260

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  5165e551

    BUCKET_ID_FUNC_OFFSET:  260

    FAILURE_BUCKET_ID:  AV_CODE_AV_BAD_IP_nt!KiPageFault

    BUCKET_ID:  AV_CODE_AV_BAD_IP_nt!KiPageFault

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

    So can anyone help me to get a resolution for this issue.

    Regards,

    unknown0001

    Thursday, June 6, 2013 6:17 PM

Answers

  • You get an access violation with a BAD Instruction Pointer.

    Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2][3] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If memtest86+ detects errors, test each module its own and replace the faulty RAM.

    If the memtest tells no error, please download CPU-Z [4], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes.

    André

    [1] http://www.memtest.org/download/4.20/memtest86+-4.20.iso.zip
    [2] http://www.imgburn.com/index.php?act=download
    [3] http://forum.imgburn.com/index.php?showtopic=61
    [4] http://www.cpuid.com/softwares/cpu-z.html


    "A programmer is just a tool which converts caffeine into code"

    • Proposed as answer by ZigZag3143x Friday, June 7, 2013 6:16 PM
    • Marked as answer by Leo Huang Tuesday, June 18, 2013 7:37 AM
    Thursday, June 6, 2013 6:25 PM
    Answerer
  • I have read software setup guide.
    found the option CR in the BIOS and I have changed to 2T
    really thanks for your time.

    i hope the BSOD are gone now.

    Regards,

    unknown0001

    • Marked as answer by Leo Huang Tuesday, June 18, 2013 7:37 AM
    Friday, June 7, 2013 4:03 PM

All replies

  • You get an access violation with a BAD Instruction Pointer.

    Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2][3] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If memtest86+ detects errors, test each module its own and replace the faulty RAM.

    If the memtest tells no error, please download CPU-Z [4], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes.

    André

    [1] http://www.memtest.org/download/4.20/memtest86+-4.20.iso.zip
    [2] http://www.imgburn.com/index.php?act=download
    [3] http://forum.imgburn.com/index.php?showtopic=61
    [4] http://www.cpuid.com/softwares/cpu-z.html


    "A programmer is just a tool which converts caffeine into code"

    • Proposed as answer by ZigZag3143x Friday, June 7, 2013 6:16 PM
    • Marked as answer by Leo Huang Tuesday, June 18, 2013 7:37 AM
    Thursday, June 6, 2013 6:25 PM
    Answerer
  • Well tnx to replying so fast.

    and i checked my memory a few day's ago with hiren's boot cd.

    for about 7 hours and did try a other memory too, and got no error's

    if i watch CPU-Z i see:

    Memory:

    type DDR3

    Size 4096 MB

    channel# Singel

    NB Frequency 2209.7 MHz

    DRAM Frequency 669.6MHz

    FSB:DRAM 3:10

    CAS# Latency (CL) 9.0 clocks

    RAS# to CAS# Delay (tRCD) 9 clocks

    RAS# Precharge (tRP) 9 clocks

    Cycle Time (tRAS) 24 clocks

    Bank Cycle Time (tRC) 33 clocks

    SPD

    Slot#1 DDR3

    Module Size 4096 MB

    Max Bandwidth PC3-10700 (667 MHz)

    Manufacture Kingstom

    Part Number ....

    S/N 162CB679

    Week/Year 25/12

    Timings Table

    JEDEC #1

    frequency 457 MHz

    CAS# Latency 6.0

    RAS# to CAS# 6

    RAS# Precharge 6

    tRAS 17

    tRP 23

    JEDEC #2

    frequency 533 MHz

    CAS# Latency 7.0

    RAS# to CAS# 7

    RAS# Precharge  7

    tRAS 20

    tRP 27

    JEDEC #3

    frequency 609 MHz

    CAS# Latency 8.0

    RAS# to CAS# 8

    RAS# Precharge 8

    tRAS 22

    tRP 30

    JEDEC #4

    frequency 685 MHz

    CAS# Latency 9.0

    RAS# to CAS# 9

    RAS# Precharge 9

    tRAS 25

    tRP 35

    All have voltage 1.50V

    so I need to change my CR to 2T in the BIOS ?

    Edit: i only saw one option in the BIOS for the memory that was:

    DRAM auto (DDR3-1333)



    Thursday, June 6, 2013 8:32 PM
  • change it to manual and set CR to 2.

    "A programmer is just a tool which converts caffeine into code"

    Friday, June 7, 2013 5:14 AM
    Answerer
  • I have read software setup guide.
    found the option CR in the BIOS and I have changed to 2T
    really thanks for your time.

    i hope the BSOD are gone now.

    Regards,

    unknown0001

    • Marked as answer by Leo Huang Tuesday, June 18, 2013 7:37 AM
    Friday, June 7, 2013 4:03 PM