Random BSOD


  1. Posts : 3
    Windows 7 Ultimate 64bit
       #1

    Random BSOD


    Hi guys

    I'm getting random BSOD REFERENCE_BY_POINTER (18)
    I've attached BSOD with Minidump and realy I'm not sure what can cause that,here is what OSR has come up

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0x18

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff8000393e034 to fffff800038bc5c0

    STACK_TEXT:
    fffff880`0d79c9e8 fffff800`0393e034 : 00000000`00000018 00000000`00000000 fffff8a0`252a3bb0 00000000`00000002 : nt!KeBugCheckEx
    fffff880`0d79c9f0 fffff800`03b9c679 : fffff880`0d79cca0 00000000`00000000 fffff8a0`252a3bb0 00000000`29edda40 : nt! ?? ::FNODOBFM::`string'+0x487c1
    fffff880`0d79ca50 fffff800`038bb853 : 00000000`00000000 00000000`00000015 00000000`00000001 00000000`29edda40 : nt!NtEnumerateValueKey+0x298
    fffff880`0d79cbb0 00000000`77a1daea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`29edd9c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a1daea


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+487c1
    fffff800`0393e034 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+487c1

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 55a6901f

    FAILURE_BUCKET_ID: X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+487c1

    BUCKET_ID: X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+487c1

    Followup: MachineOwner
    Looks like its Driver,but which one I'm not sure

    Thanks in advance for any help
      My Computer


  2. Posts : 449
    Windows 7 Home Premium
       #2

    I noticed in your event log you had a ton of these:


    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume J:

    Have you ran the chkdsk utility?
      My Computer


  3. Posts : 3
    Windows 7 Ultimate 64bit
    Thread Starter
       #3

    copiman said:
    I noticed in your event log you had a ton of these:


    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume J:

    Have you ran the chkdsk utility?
    Hi there

    Yes I know,but this not causing BSOD this I know for sure,previously I've never have any BSOD,two days in row I'm getting this BSOD REFERENCE_BY_POINTER when PC is idling for few hours

    This volume J I'm trying to recover via TestDisk,but I'm right now getting BSOD and I'm unable to recover and running chkdsk I will loose files like last time and due this I'm not running this at moment unless I will recover the files

    Thanks
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #4

    Hi eric78,

    You are running an Alienware Product ID on a Gigabyte board.
    This makes your installation counterfeit.
    Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
    A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
    For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
    Code:
    OS Manufacturer:           Microsoft Corporation
    OS Configuration:          Standalone Workstation
    OS Build Type:             Multiprocessor Free
    Registered Owner:          Jura
    Registered Organization:   
    Product ID:                00426-OEM-8992662-00008 <-- Alienware PID on Gigabyte board
    Original Install Date:     07/03/2014, 20:45:34
    System Boot Time:          02/11/2015, 11:56:39
    System Manufacturer:       Gigabyte Technology Co., Ltd.
    I recommend to install a genuine copy of Windows.
    If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.
      My Computer


  5. Posts : 3
    Windows 7 Ultimate 64bit
    Thread Starter
       #5

    axe0 said:
    Hi eric78,

    You are running an Alienware Product ID on a Gigabyte board.
    This makes your installation counterfeit.
    Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
    A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
    For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
    Code:
    OS Manufacturer:           Microsoft Corporation
    OS Configuration:          Standalone Workstation
    OS Build Type:             Multiprocessor Free
    Registered Owner:          Jura
    Registered Organization:   
    Product ID:                00426-OEM-8992662-00008 <-- Alienware PID on Gigabyte board
    Original Install Date:     07/03/2014, 20:45:34
    System Boot Time:          02/11/2015, 11:56:39
    System Manufacturer:       Gigabyte Technology Co., Ltd.
    I recommend to install a genuine copy of Windows.
    If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.
    That's strange,I bought the PC over on eBay few months back and this has been custom build PC and regarding the Alienware PID this I didn't know at all and I expected PC is running genuine Windows

    Thanks
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #6

    It actually isn't that strange at all, but to better understand it you would need some experience or read some reviews from people with the same experience.

    When you buy a pc, it is recommended to run the MGADiag from Windows Genuine and Activation Issue Posting Instruction and let someone who can read it check it.
      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 18:54.
Find Us