BDOS - Need Some Help, Not Too Computer Savvy


  1. Posts : 1
    Windows 7 x64
       #1

    BDOS - Need Some Help, Not Too Computer Savvy


    Hey guys, ordered a Clevo gaming laptop from AVAdirect about a month ago, and about four days into it, after re-installing all my regular programs and what not, I start getting these random bluescreens. I was wondering if someone here could help me get rid of these.

    My Windows Seven is...
    The original x64 Home Premium, originally installed with the system by the manufacturer, OEM. About a month old, and I haven't re-installed anything related to the operating system.

    It seems the problem is that kernal file. Anyone have any ideas?
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    No probable cause is indicated. Boot in safe mode then enable driver verifier. Use the laptop normal until it crashes then upload the newest dump file located in C:\Windows\Minidump
    Driver Verifier - Enable and Disable


    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {ffffda80094f9b40, 2, 1, fffff800036d332f}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+20f )
    
    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: ffffda80094f9b40, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff800036d332f, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800039010e0
     ffffda80094f9b40 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiTimerWaitTest+20f
    fffff800`036d332f 488908          mov     qword ptr [rax],rcx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff80000b9c3d0 -- (.trap 0xfffff80000b9c3d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffda80094f9b40 rbx=0000000000000000 rcx=fffffa8009124260
    rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800036d332f rsp=fffff80000b9c560 rbp=fffffa800940b708
     r8=fffff8000386b201  r9=0000000000000086 r10=fffff80003843e80
    r11=fffff8000386b2d0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!KiTimerWaitTest+0x20f:
    fffff800`036d332f 488908          mov     qword ptr [rax],rcx ds:0001:ffffda80`094f9b40=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800036c8ca9 to fffff800036c9740
    
    STACK_TEXT:  
    fffff800`00b9c288 fffff800`036c8ca9 : 00000000`0000000a ffffda80`094f9b40 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff800`00b9c290 fffff800`036c7920 : ffffffff`fff63c00 fffffa80`0940b708 fffffa80`08355780 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00b9c3d0 fffff800`036d332f : ffffffff`fffb6c20 fffff800`036d529e fffff800`00b9c618 00000000`00000000 : nt!KiPageFault+0x260
    fffff800`00b9c560 fffff800`036d4d7d : fffffa80`0940b700 fffffa80`095e9100 fffffa80`095e9100 00000000`00000102 : nt!KiTimerWaitTest+0x20f
    fffff800`00b9c5e0 fffff800`036d54be : 00000000`24f2542d fffff800`00b9cc58 00000000`00000f85 fffff800`03847328 : nt!KiProcessExpiredTimerList+0x6d
    fffff800`00b9cc30 fffff800`036d4cb7 : 00000000`0c14cdc5 00000000`00000f85 00000000`0c14cde1 00000000`00000085 : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`036d1eea : fffff800`03843e80 fffff800`03851c40 00000000`00000000 fffff880`113584c0 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiTimerWaitTest+20f
    fffff800`036d332f 488908          mov     qword ptr [rax],rcx
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KiTimerWaitTest+20f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+20f
    
    BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+20f
    
    Followup: MachineOwner
    ---------
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:55.
Find Us