Random BSOD, plz help

Page 1 of 4 123 ... LastLast

  1. Posts : 17
    Windows 7 64 bit
       #1

    Random BSOD, plz help


    I brought my new pc about 2 weeks ago (you can see my specs in my profile). At first everything worked great but after about a week i got a BSOD. I restarted my PC and it happened again after another 4 hours, and again after another hour.

    So I restored my PC to an earlier setting (I set it to how it was 3 days earlier). But after another 6 or so hours the Blue Screen apeared again. So I took it back to the store (I brought it from a small store that specialised in custom PCs - I got my last 3 Pcs from them with no problem) and for the last week we have tried everything from changing my memory, to upgrading it, to changing motherboards (it was an ASUS Deluxe v2) and nothing worked.
    I even tried the everest system stability tset to see if i can force a blue screen but it didnt work.

    In the Blues screen I keep getting diffrent kind of errors:
    FAUALT_IN_NONPAGED_AVED
    NOT_LESS_OR_EQUAL
    and the last occured when I was playing an online game
    SYSTEM_SERVICE_EXCEPT 0X0000003B

    I have attached the minidump file.
    Thank you all for your time and help.

    (please note that I'm not very skilled with computers)
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    fahadalrefaei said:
    I brought my new pc about 2 weeks ago (you can see my specs in my profile). At first everything worked great but after about a week i got a BSOD. I restarted my PC and it happened again after another 4 hours, and again after another hour.

    So I restored my PC to an earlier setting (I set it to how it was 3 days earlier). But after another 6 or so hours the Blue Screen apeared again. So I took it back to the store (I brought it from a small store that specialised in custom PCs - I got my last 3 Pcs from them with no problem) and for the last week we have tried everything from changing my memory, to upgrading it, to changing motherboards (it was an ASUS Deluxe v2) and nothing worked.
    I even tried the everest system stability tset to see if i can force a blue screen but it didnt work.

    In the Blues screen I keep getting diffrent kind of errors:
    FAUALT_IN_NONPAGED_AVED
    NOT_LESS_OR_EQUAL
    and the last occured when I was playing an online game
    SYSTEM_SERVICE_EXCEPT 0X0000003B

    I have attached the minidump file.
    Thank you all for your time and help.

    (please note that I'm not very skilled with computers)

    These both were caused by memory_corruption. I think given that you just "updated" the memory I would run a memory test

    Run a system file check to verify and repair your system files.
    To do this type cmd in search, then right click to run as administrator, then
    SFC /SCANNOW

    read here for more information SFC /SCANNOW Command - System File Checker

    Let us know the results from the report at the end.

    Ken





    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\091010-24195-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03059000 PsLoadedModuleList = 0xfffff800`03296e50
    Debug session time: Fri Sep 10 13:54:05.407 2010 (GMT-4)
    System Uptime: 0 days 0:40:23.547
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 24, {1904fb, fffff880062c9508, fffff880062c8d70, fffff880012eded9}
    
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    NTFS_FILE_SYSTEM (24)
        If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Arguments:
    Arg1: 00000000001904fb
    Arg2: fffff880062c9508
    Arg3: fffff880062c8d70
    Arg4: fffff880012eded9
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff880062c9508 -- (.exr 0xfffff880062c9508)
    ExceptionAddress: fffff880012eded9 (Ntfs!NtfsOpenExistingAttr+0x00000000000001d9)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000000000e8
    Attempt to read from address 00000000000000e8
    
    CONTEXT:  fffff880062c8d70 -- (.cxr 0xfffff880062c8d70)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
    rdx=fffff8a00372a810 rsi=0000000000020002 rdi=fffff88007d083b0
    rip=fffff880012eded9 rsp=fffff880062c9740 rbp=0000000000000000
     r8=fffff8a00309d900  r9=fffff880062c9ca8 r10=fffff880062c9a30
    r11=fffff880062c9710 r12=fffffa800e31f010 r13=fffff88007d08420
    r14=fffff8a00309d900 r15=fffffa800beaaae0
    iopl=0         nv up ei ng nz ac pe cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010293
    Ntfs!NtfsOpenExistingAttr+0x1d9:
    fffff880`012eded9 81bc25e8000000a0000000 cmp dword ptr [rbp+0E8h],0A0h ss:0018:00000000`000000e8=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  raptr.exe
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  00000000000000e8
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033010e0
     00000000000000e8 
    
    FOLLOWUP_IP: 
    Ntfs!NtfsOpenExistingAttr+1d9
    fffff880`012eded9 81bc25e8000000a0000000 cmp dword ptr [rbp+0E8h],0A0h
    
    FAULTING_IP: 
    Ntfs!NtfsOpenExistingAttr+1d9
    fffff880`012eded9 81bc25e8000000a0000000 cmp dword ptr [rbp+0E8h],0A0h
    
    BUGCHECK_STR:  0x24
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    LAST_CONTROL_TRANSFER:  from fffff880012ea78b to fffff880012eded9
    
    STACK_TEXT:  
    fffff880`062c9740 fffff880`012ea78b : fffff880`07d083b0 fffffa80`0beaaae0 fffff8a0`0309dc98 fffff8a0`00000020 : Ntfs!NtfsOpenExistingAttr+0x1d9
    fffff880`062c9800 fffff880`012eaeff : fffffa80`0beaaae0 fffffa80`0e31f010 fffff8a0`0309dc98 fffff880`00000020 : Ntfs!NtfsOpenAttributeInExistingFile+0x5ab
    fffff880`062c9990 fffff880`012fbe76 : fffffa80`0beaaae0 fffffa80`0e31f010 fffff8a0`0309dc98 fffff880`062c9c10 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef
    fffff880`062c9a80 fffff880`012f628d : fffffa80`0beaaae0 fffffa80`0e31f010 fffff880`062c9c60 fffff880`062c9ca8 : Ntfs!NtfsFindStartingNode+0x5e6
    fffff880`062c9b50 fffff880`0125fc0d : fffffa80`0beaaae0 fffffa80`0e31f010 fffff880`07d083b0 fffffa80`0d602b00 : Ntfs!NtfsCommonCreate+0x3dd
    fffff880`062c9d30 fffff800`030c15c7 : fffff880`07d08320 00000000`ffffffff 00000000`7efd8000 00000000`3a13ff40 : Ntfs!NtfsCommonCreateCallout+0x1d
    fffff880`062c9d60 fffff800`030c1581 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
    fffff880`07d081f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
    
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
        fffff880012ededb - Ntfs!NtfsOpenExistingAttr+1db
        [ 24:25 ]
    1 error : !Ntfs (fffff880012ededb)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  ONE_BIT
    
    STACK_COMMAND:  .cxr 0xfffff880062c8d70 ; kb
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
    
    Followup: memory_corruption
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    NTFS_FILE_SYSTEM (24)
        If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Arguments:
    Arg1: 00000000001904fb
    Arg2: fffff880062c9508
    Arg3: fffff880062c8d70
    Arg4: fffff880012eded9
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff880062c9508 -- (.exr 0xfffff880062c9508)
    ExceptionAddress: fffff880012eded9 (Ntfs!NtfsOpenExistingAttr+0x00000000000001d9)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000000000e8
    Attempt to read from address 00000000000000e8
    
    CONTEXT:  fffff880062c8d70 -- (.cxr 0xfffff880062c8d70)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
    rdx=fffff8a00372a810 rsi=0000000000020002 rdi=fffff88007d083b0
    rip=fffff880012eded9 rsp=fffff880062c9740 rbp=0000000000000000
     r8=fffff8a00309d900  r9=fffff880062c9ca8 r10=fffff880062c9a30
    r11=fffff880062c9710 r12=fffffa800e31f010 r13=fffff88007d08420
    r14=fffff8a00309d900 r15=fffffa800beaaae0
    iopl=0         nv up ei ng nz ac pe cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010293
    Ntfs!NtfsOpenExistingAttr+0x1d9:
    fffff880`012eded9 81bc25e8000000a0000000 cmp dword ptr [rbp+0E8h],0A0h ss:0018:00000000`000000e8=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  raptr.exe
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  00000000000000e8
    
    READ_ADDRESS:  00000000000000e8 
    
    FOLLOWUP_IP: 
    Ntfs!NtfsOpenExistingAttr+1d9
    fffff880`012eded9 81bc25e8000000a0000000 cmp dword ptr [rbp+0E8h],0A0h
    
    FAULTING_IP: 
    Ntfs!NtfsOpenExistingAttr+1d9
    fffff880`012eded9 81bc25e8000000a0000000 cmp dword ptr [rbp+0E8h],0A0h
    
    BUGCHECK_STR:  0x24
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    LAST_CONTROL_TRANSFER:  from fffff880012ea78b to fffff880012eded9
    
    STACK_TEXT:  
    fffff880`062c9740 fffff880`012ea78b : fffff880`07d083b0 fffffa80`0beaaae0 fffff8a0`0309dc98 fffff8a0`00000020 : Ntfs!NtfsOpenExistingAttr+0x1d9
    fffff880`062c9800 fffff880`012eaeff : fffffa80`0beaaae0 fffffa80`0e31f010 fffff8a0`0309dc98 fffff880`00000020 : Ntfs!NtfsOpenAttributeInExistingFile+0x5ab
    fffff880`062c9990 fffff880`012fbe76 : fffffa80`0beaaae0 fffffa80`0e31f010 fffff8a0`0309dc98 fffff880`062c9c10 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef
    fffff880`062c9a80 fffff880`012f628d : fffffa80`0beaaae0 fffffa80`0e31f010 fffff880`062c9c60 fffff880`062c9ca8 : Ntfs!NtfsFindStartingNode+0x5e6
    fffff880`062c9b50 fffff880`0125fc0d : fffffa80`0beaaae0 fffffa80`0e31f010 fffff880`07d083b0 fffffa80`0d602b00 : Ntfs!NtfsCommonCreate+0x3dd
    fffff880`062c9d30 fffff800`030c15c7 : fffff880`07d08320 00000000`ffffffff 00000000`7efd8000 00000000`3a13ff40 : Ntfs!NtfsCommonCreateCallout+0x1d
    fffff880`062c9d60 fffff800`030c1581 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
    fffff880`07d081f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
    
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
        fffff880012ededb - Ntfs!NtfsOpenExistingAttr+1db
        [ 24:25 ]
    1 error : !Ntfs (fffff880012ededb)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  ONE_BIT
    
    STACK_COMMAND:  .cxr 0xfffff880062c8d70 ; kb
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
    
    Followup: memory_corruption
    ---------
      My Computer


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

    I ran a system file check and everything checks out - i tried a few other memory programmes and they all say my memory is fine. The people from the store also thought it was a memory issue but nothing they did, wether it was changing the memory sticks to new ones, or upgrade it (I originally had only 10GB ram but i changed to 12GB after the blue screens started apearing), was able to fix it.
      My Computer


  4. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #4

    Ken is spot on about memory corruption. Memory corruption can be caused by many thing besides bad RAM - faulty drivers, incompatible software or hardware, defective hardware, etc.

    I suggest that you uninstall Eset NOD32 while you are troubleshooting using this removal tool: Info > Tool. Eset has been know to cause BSOD's on some Win 7 systems. You can always try it again after you get your system running smoothly. Download and install Microsoft Security Essentials in its place.

    You also have some very out of date drivers. Generally speaking, Win 7 does not like out of date third party drivers. They can and do cause memory corruption. Update the following drivers:

    000.fcl Fri Sep 26 09:11:22 2008 -
    CyberLink FCL Driver http://www.gocyberlink.com. This software is obsolete. Update the driver or uninstall the software.

    e1y60x64.sys Mon Aug 18 17:45:05 2008 -
    Intel(R) 82567LM Gigabit Network Connection http://downloadcenter.intel.com/Default.aspx.

    ezplay.sys Mon Apr 30 06:08:55 2007 - Helper driver to facilitate play of cd backups belongs to the software autoplay Application by VSO Software (www.vso-software.fr). This software is very obsolete. I suggest you uninstall it.

    If you need help with the drivers, please post back.

    After you uninstall NOD32 and take care of the above drivers, reboot and run your system. If you get another BSOD, please upload it and we will go from there. If your system is running smoothly, post back in a two or three days and let us know.



      My Computer


  5. Posts : 17
    Windows 7 64 bit
    Thread Starter
       #5

    I'm Uninstalling ESET NOD32 right now, thanks for the advice.
    I'll post back in 24 hours whether this works or not, thanks agian.
      My Computer


  6. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #6

    You are very welcome. We will be here:)
      My Computer


  7. Posts : 17
    Windows 7 64 bit
    Thread Starter
       #7

    I think the BSOD may have gotten a bit worse.
    I now am getting an 0X0000000A error instead, but my pc freezes completely before the dump can be completed ><.
    I changed my antiviruse to norton 360, I updated all the drives I can find and deleted all the out-dated and unimportant software.
    The good news is that it seems the blue screen will only occur when im playing my online game. day-to-day stuff like web browsing will not cause it to crash anymore or at least not nearly as often.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    fahadalrefaei said:
    I think the BSOD may have gotten a bit worse.
    I now am getting an 0X0000000A error instead, but my pc freezes completely before the dump can be completed ><.
    I changed my antiviruse to norton 360, I updated all the drives I can find and deleted all the out-dated and unimportant software.
    The good news is that it seems the blue screen will only occur when im playing my online game. day-to-day stuff like web browsing will not cause it to crash anymore or at least not nearly as often.

    Just a quick note in support of Carl. He is absolutely right about removing the AV, but Norton is one of the worst offenders.


    The AV of choice for BSOD's is Microsoft Security Essentials.

    Ken J
      My Computer


  9. Posts : 17
    Windows 7 64 bit
    Thread Starter
       #9

    Thanks, I'll switch it to Microsoft Security Essentials right now, wish me luck :)
      My Computer


  10. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #10

    Thank you, Ken. :)

    @ fahadalrefaaei - Ken is absolutely correct; Norton is, indeed, one of the worst offenders. For troubleshooting BSOD's, you want MSE and Windows Firewall.

    Error code A is usually caused by Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility. Notice that antivirus is shown as one of the causes. I do wish you luck; post back and let us know.
      My Computer


 
Page 1 of 4 123 ... LastLast

  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 04:57.
Find Us