Frequent BSODs--Hardware or Software?

Page 1 of 2 12 LastLast

  1. Posts : 11
    Windows 7 Home Premium 64-bit
       #1

    Frequent BSODs--Hardware or Software?


    Hello all!

    I am fairly ignorant when it comes to PCs, so I finally broke down and bought a Cyberpower PC off of Newegg for my online gaming. I noticed my first BSOD shortly after purchasing it, but thought nothing of it since I had no idea what it was. Then about 6 months ago, they started to get worse and more frequent.

    The issue tends to come and go, but finally I am at the point where I simply cannot take it anymore.

    For a brief history:

    I reformatted my C: drive yesterday. I used my provided Win7 CD and installed my Motherboard drivers via the disc I was also provided. I then went to ATI's website and downloaded the latest drivers for my video card (ATI Radeon HD 5800 Series, 11.5).

    I then proceeded to allow Windows to update itself. It seems like I have gotten most of the windows updates out of the way, but as I speak I am currently downloading another one that just popped up.

    I am STILL getting BSODs. Whether it be while playing Rift, WoW, or simply browsing the internet or doing miniscule tasks, they just keep happening. Usually it is associated with an annoying sound (the sound looping into just an awful noise) along with lines running across the screen, quickly followed by a BSOD doing a memory dump.

    Again, this is all after reformatting. I am not sure what all my Windows_NT6_BSOD_jcgriff2 folder will contain, so I will include the following 3 dump logs:

    Code:
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 1000007e
      BCP1: FFFFFFFFC0000005
      BCP2: FFFFF88004CE3153
      BCP3: FFFFF880021BF9E8
      BCP4: FFFFF880021BF250
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 768_1
    Code:
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 24
      BCP1: 00000000001904FB
      BCP2: FFFFF88007861BB8
      BCP3: FFFFF88007861420
      BCP4: FFFFF80002ED0995
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 768_1
    Code:
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 1e
      BCP1: 0000000000000000
      BCP2: 0000000000000000
      BCP3: 0000000000000000
      BCP4: 0000000000000000
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 768_1
    After looking up BCCode 24, I saw advice on checking my drive for corruption. So I ran a check drive scan, which required me to restart my PC since C: is the only drive I use. Here are the results of that:

    Code:
    Checking file system on C:
    The type of the file system is NTFS.
    A disk check has been scheduled.
    Windows will now check the disk.                         
    CHKDSK is verifying files (stage 1 of 5)...
      90112 file records processed.                                          
    File verification completed.
      109 large file records processed.                                      
    0 bad file records processed.                                        
    0 EA records processed.                                              
    44 reparse records processed.                                       
    CHKDSK is verifying indexes (stage 2 of 5)...
      130784 index entries processed.                                         
    Index verification completed.
      0 unindexed files scanned.                                           
    0 unindexed files recovered.                                       
    CHKDSK is verifying security descriptors (stage 3 of 5)...
      90112 file SDs/SIDs processed.                                         
    Cleaning up 149 unused index entries from index $SII of file 0x9.
    Cleaning up 149 unused index entries from index $SDH of file 0x9.
    Cleaning up 149 unused security descriptors.
    Security descriptor verification completed.
      20337 data files processed.                                            
    CHKDSK is verifying Usn Journal...
      34528872 USN bytes processed.                                             
    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
      90096 files processed.                                                 
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      222729480 free clusters processed.                                         
    Free space verification is complete.
    Windows has checked the file system and found no problems.
     976657407 KB total disk space.
      85471012 KB in 66939 files.
         48456 KB in 20338 indexes.
             0 KB in bad sectors.
        220015 KB in use by the system.
         65536 KB occupied by the log file.
     890917924 KB available on disk.
          4096 bytes in each allocation unit.
     244164351 total allocation units on disk.
     222729481 allocation units available on disk.
    Internal Info:
    00 60 01 00 f9 54 01 00 b6 a5 02 00 00 00 00 00  .`...T..........
    7d 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  }...,...........
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    Windows has finished checking your disk.
    Please wait while your computer restarts.
    At any rate, perhaps I am supplying too much information. I attached the ZIP folder. I also ran the System Health Report as asked, but I am unsure how to include that here as I saved it as an HTML. Here is the link to that ( not sure if that's how I'm supposed to include it)

    C:\Users\CaseyTout\Documents\systemhealthreport.html

    Also, my system specs:

    Windows 7 home premium 64-bit
    -came preinstalled

    8gigs of ram
    -I bought two new sticks to replace the originals. problem still occured, so I went ahead and put the other two sticks in, going from 4 to 8 gigs

    AMD Phenom II X4 965 Processor 3.4 GHz

    Gigabyte GA-77OT-USB 3 Motherboard
    -let it be KNOWN that some of my USB ports DO NOT WORK. I cannot plug in my mouse or keyboard to some of the ports. I largely ignored this issue, but now I wonder if I shouldn't have?

    ATI Radeon HD 5800 Series graphics card
    -yes, up to date as of 5-9-11 drivers
    Any and all help would be GREATLY appreciated.
      My Computer


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

    ramennoodleking said:
    Hello all!

    I am fairly ignorant when it comes to PCs, so I finally broke down and bought a Cyberpower PC off of Newegg for my online gaming. I noticed my first BSOD shortly after purchasing it, but thought nothing of it since I had no idea what it was. Then about 6 months ago, they started to get worse and more frequent.

    The issue tends to come and go, but finally I am at the point where I simply cannot take it anymore.

    For a brief history:

    I reformatted my C: drive yesterday. I used my provided Win7 CD and installed my Motherboard drivers via the disc I was also provided. I then went to ATI's website and downloaded the latest drivers for my video card (ATI Radeon HD 5800 Series, 11.5).

    I then proceeded to allow Windows to update itself. It seems like I have gotten most of the windows updates out of the way, but as I speak I am currently downloading another one that just popped up.

    I am STILL getting BSODs. Whether it be while playing Rift, WoW, or simply browsing the internet or doing miniscule tasks, they just keep happening. Usually it is associated with an annoying sound (the sound looping into just an awful noise) along with lines running across the screen, quickly followed by a BSOD doing a memory dump.

    Again, this is all after reformatting. I am not sure what all my Windows_NT6_BSOD_jcgriff2 folder will contain, so I will include the following 3 dump logs:

    Code:
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 1000007e
      BCP1: FFFFFFFFC0000005
      BCP2: FFFFF88004CE3153
      BCP3: FFFFF880021BF9E8
      BCP4: FFFFF880021BF250
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 768_1
    Code:
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 24
      BCP1: 00000000001904FB
      BCP2: FFFFF88007861BB8
      BCP3: FFFFF88007861420
      BCP4: FFFFF80002ED0995
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 768_1
    Code:
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 1e
      BCP1: 0000000000000000
      BCP2: 0000000000000000
      BCP3: 0000000000000000
      BCP4: 0000000000000000
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 768_1
    After looking up BCCode 24, I saw advice on checking my drive for corruption. So I ran a check drive scan, which required me to restart my PC since C: is the only drive I use. Here are the results of that:

    Code:
    Checking file system on C:
    The type of the file system is NTFS.
    A disk check has been scheduled.
    Windows will now check the disk.                         
    CHKDSK is verifying files (stage 1 of 5)...
      90112 file records processed.                                          
    File verification completed.
      109 large file records processed.                                      
    0 bad file records processed.                                        
    0 EA records processed.                                              
    44 reparse records processed.                                       
    CHKDSK is verifying indexes (stage 2 of 5)...
      130784 index entries processed.                                         
    Index verification completed.
      0 unindexed files scanned.                                           
    0 unindexed files recovered.                                       
    CHKDSK is verifying security descriptors (stage 3 of 5)...
      90112 file SDs/SIDs processed.                                         
    Cleaning up 149 unused index entries from index $SII of file 0x9.
    Cleaning up 149 unused index entries from index $SDH of file 0x9.
    Cleaning up 149 unused security descriptors.
    Security descriptor verification completed.
      20337 data files processed.                                            
    CHKDSK is verifying Usn Journal...
      34528872 USN bytes processed.                                             
    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
      90096 files processed.                                                 
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      222729480 free clusters processed.                                         
    Free space verification is complete.
    Windows has checked the file system and found no problems.
     976657407 KB total disk space.
      85471012 KB in 66939 files.
         48456 KB in 20338 indexes.
             0 KB in bad sectors.
        220015 KB in use by the system.
         65536 KB occupied by the log file.
     890917924 KB available on disk.
          4096 bytes in each allocation unit.
     244164351 total allocation units on disk.
     222729481 allocation units available on disk.
    Internal Info:
    00 60 01 00 f9 54 01 00 b6 a5 02 00 00 00 00 00  .`...T..........
    7d 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  }...,...........
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    Windows has finished checking your disk.
    Please wait while your computer restarts.
    At any rate, perhaps I am supplying too much information. I attached the ZIP folder. I also ran the System Health Report as asked, but I am unsure how to include that here as I saved it as an HTML. Here is the link to that ( not sure if that's how I'm supposed to include it)

    C:\Users\CaseyTout\Documents\systemhealthreport.html

    Any and all help would be GREATLY appreciated.
    The newest crash was caused by cpudrv64.sys (suspect the others as well) (System Requirements Lab)

    I would remove it for several reasons. Its older than windows, installed in the 32 bit programs folder (it is 64 bit) and is supect for other reasons

    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\051511-27237-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    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 (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Machine Name:
    Kernel base = 0xfffff800`02e1f000 PsLoadedModuleList = 0xfffff800`0305ce50
    Debug session time: Sun May 15 15:30:38.888 2011 (GMT-4)
    System Uptime: 0 days 0:12:36.620
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000096, fffff88007d8d912, 0, 0}
    
    Unable to load image \??\C:\Program Files (x86)\SystemRequirementsLab\cpudrv64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for cpudrv64.sys
    *** ERROR: Module load completed but symbols could not be loaded for cpudrv64.sys
    Probably caused by : cpudrv64.sys ( cpudrv64+1912 )
    
    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: ffffffffc0000096, The exception code that was not handled
    Arg2: fffff88007d8d912, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.
    
    FAULTING_IP: 
    cpudrv64+1912
    fffff880`07d8d912 0f32            rdmsr
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  inteldriver.ex
    
    CURRENT_IRQL:  0
    
    EXCEPTION_RECORD:  fffff8800a2e56c8 -- (.exr 0xfffff8800a2e56c8)
    ExceptionAddress: fffff88007d8d912 (cpudrv64+0x0000000000001912)
       ExceptionCode: c0000096
      ExceptionFlags: 00000000
    NumberParameters: 0
    
    TRAP_FRAME:  fffff8800a2e5770 -- (.trap 0xfffff8800a2e5770)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000102b780 rbx=0000000000000000 rcx=0000000000000017
    rdx=fffff8800a2e59b4 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88007d8d912 rsp=fffff8800a2e5908 rbp=fffff8800a2e5ca0
     r8=fffff8800a2e59b8  r9=000000000000000e r10=fffff88002f64ca0
    r11=fffff8800a2e5a08 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cpudrv64+0x1912:
    fffff880`07d8d912 0f32            rdmsr
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ec9ab9 to fffff80002e8f700
    
    STACK_TEXT:  
    fffff880`0a2e4ef8 fffff800`02ec9ab9 : 00000000`0000001e ffffffff`c0000096 fffff880`07d8d912 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0a2e4f00 fffff800`02e8ed42 : fffff880`0a2e56c8 fffffa80`070a2840 fffff880`0a2e5770 fffffa80`0942e280 : nt!KiDispatchException+0x1b9
    fffff880`0a2e5590 fffff800`02e8d64a : 00000000`00000000 00000000`a000000c fffffa01`0942e280 fffff800`02eaed1c : nt!KiExceptionDispatch+0xc2
    fffff880`0a2e5770 fffff880`07d8d912 : fffff880`0a2e59b8 fffff880`0a2e59b4 fffffa80`0942e280 fffffa80`0942e280 : nt!KiGeneralProtectionFault+0x10a
    fffff880`0a2e5908 fffff880`0a2e59b8 : fffff880`0a2e59b4 fffffa80`0942e280 fffffa80`0942e280 fffff880`0a2e5ca0 : cpudrv64+0x1912
    fffff880`0a2e5910 fffff880`0a2e59b4 : fffffa80`0942e280 fffffa80`0942e280 fffff880`0a2e5ca0 fffffa80`070a2840 : 0xfffff880`0a2e59b8
    fffff880`0a2e5918 fffffa80`0942e280 : fffffa80`0942e280 fffff880`0a2e5ca0 fffffa80`070a2840 fffff880`07d903c3 : 0xfffff880`0a2e59b4
    fffff880`0a2e5920 fffffa80`0942e280 : fffff880`0a2e5ca0 fffffa80`070a2840 fffff880`07d903c3 fffffa80`070a2840 : 0xfffffa80`0942e280
    fffff880`0a2e5928 fffff880`0a2e5ca0 : fffffa80`070a2840 fffff880`07d903c3 fffffa80`070a2840 00000000`00000000 : 0xfffffa80`0942e280
    fffff880`0a2e5930 fffffa80`070a2840 : fffff880`07d903c3 fffffa80`070a2840 00000000`00000000 fffff680`00005918 : 0xfffff880`0a2e5ca0
    fffff880`0a2e5938 fffff880`07d903c3 : fffffa80`070a2840 00000000`00000000 fffff680`00005918 00000000`00000000 : 0xfffffa80`070a2840
    fffff880`0a2e5940 fffffa80`070a2840 : 00000000`00000000 fffff680`00005918 00000000`00000000 00000000`000000fc : cpudrv64+0x43c3
    fffff880`0a2e5948 00000000`00000000 : fffff680`00005918 00000000`00000000 00000000`000000fc fffff880`0a2e59a8 : 0xfffffa80`070a2840
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    cpudrv64+1912
    fffff880`07d8d912 0f32            rdmsr
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  cpudrv64+1912
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: cpudrv64
    
    IMAGE_NAME:  cpudrv64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a819eb1
    
    FAILURE_BUCKET_ID:  X64_0x1E_cpudrv64+1912
    
    BUCKET_ID:  X64_0x1E_cpudrv64+1912
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm cpudrv64
    start             end                 module name
    fffff880`07d8c000 fffff880`07d94000   cpudrv64 T (no symbols)           
        Loaded symbol image file: cpudrv64.sys
        Image path: \??\C:\Program Files (x86)\SystemRequirementsLab\cpudrv64.sys
        Image name: cpudrv64.sys
        Timestamp:        Tue Aug 11 12:39:13 2009 (4A819EB1)
        CheckSum:         0000D622
        ImageSize:        00008000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 11
    Windows 7 Home Premium 64-bit
    Thread Starter
       #3

    Ok, there's an excellent first step for me. Now, seeing as I am ignorant, how do I go about removing it?

    EDIT: let me add that the "new windows update" i spoke of was actually Service Pack 1. The crashes appeared prior to the installation of this service pack. Actually, I need to restart my PC as we speak. Just adding this info in case it helps.
      My Computer


  4. Posts : 11
    Windows 7 Home Premium 64-bit
    Thread Starter
       #4

    Ok I went into my C: Drive, fround Prgram Files(x86) then found SystemRequirementsLab and deleted cpudrv64.sys

    It is currently in my recycling bin. Is that all I needed to do?
      My Computer


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

    ramennoodleking said:
    Ok I went into my C: Drive, fround Prgram Files(x86) then found SystemRequirementsLab and deleted cpudrv64.sys

    It is currently in my recycling bin. Is that all I needed to do?
    Wasnt it listed in add remove? If it loaded something loaded it. check the control panel
      My Computer


  6. Posts : 11
    Windows 7 Home Premium 64-bit
    Thread Starter
       #6

    zigzag3143 said:
    ramennoodleking said:
    Ok I went into my C: Drive, fround Prgram Files(x86) then found SystemRequirementsLab and deleted cpudrv64.sys

    It is currently in my recycling bin. Is that all I needed to do?
    Wasnt it listed in add remove? If it loaded something loaded it. check the control panel
    Ah, so I should delete systemrequirementslab altogether?

    I see it in control panel. I'll gladly delete it if it won't effect something important.
      My Computer


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

    ramennoodleking said:
    zigzag3143 said:
    ramennoodleking said:
    Ok I went into my C: Drive, fround Prgram Files(x86) then found SystemRequirementsLab and deleted cpudrv64.sys

    It is currently in my recycling bin. Is that all I needed to do?
    Wasnt it listed in add remove? If it loaded something loaded it. check the control panel
    Ah, so I should delete systemrequirementslab altogether?

    I see it in control panel. I'll gladly delete it if it won't effect something important.
    It is not part of the operating system. I dont know if you use it for anything so I would make a backup and restore point just in case.

    You want to un-install it , not delete it.
      My Computer


  8. Posts : 11
    Windows 7 Home Premium 64-bit
    Thread Starter
       #8

    Ok I've done that.

    Is there anything else that I should worry about? No BSODs yet, but I have a feeling one will occur sooner rather than later.
      My Computer


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

    ramennoodleking said:
    Ok I've done that.

    Is there anything else that I should worry about? No BSODs yet, but I have a feeling one will occur sooner rather than later.
    All you can do is wait for the BSOD and its data.
      My Computer


  10. Posts : 11
    Windows 7 Home Premium 64-bit
    Thread Starter
       #10

    I really appreciate the help zigzag. So far, so good. Any additional BSODs and I will zip up the file and send it again in a reply post here.

    Until then--how do i Rep you?
      My Computer


 
Page 1 of 2 12 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 13:34.
Find Us