Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 7 BSOD Help


  • Please log in to reply
21 replies to this topic

#1 Swanky67

Swanky67

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:01 PM

Posted 20 February 2017 - 12:41 AM

(It won't allow me to attach files? I'm not permitted to do so apparently. I've instead uploaded the information you requested to a dropbox.)

 

https://www.dropbox.com/s/id95u49qhyjcdyg/SysnativeFileCollectionApp.zip?dl=0

https://www.dropbox.com/s/iyvvd2qex246dnz/Perf%20Report.html?dl=0

 

· OS - Windows 8.1, 8, 7, Vista? - Windows 7.
· x86 (32-bit) or x64? - x64 bit
· What was original installed OS on system? Windows 7 Home premium. 
· Is the OS an OEM version? - I used a CD.
· Age of system (hardware) - With these new parts I have in about two months old.
· Age of OS installation - About half a year ago.

· CPU - i7 6700k processor
· Video Card - NVIDIA Geforce GTX 1070
· MotherBoard - Z170A GAMING M7
· Power Supply - 750 Watt, HCG-750

· System Manufacturer - MSI
· Exact model number - MS-7976

· Laptop or Desktop? - Desktop

 

 

Hey guys, I would really value any help given. Even if we don't figure out the problem I appreciate you guys taking time out of your day to help me out. Have a good one.



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:01:01 PM

Posted 20 February 2017 - 10:41 PM

Hello, Swanky67 and :welcome: to BleepingComputer's Windows Crashes, BSOD, and Hangs Help and Support forum.

Please follow these instructions to run Driver Verifier. I can't tell too much from your dumps. While you're doing that, I suggest you uninstall your MSI utilities from the Control Panel and test your RAM.

Thank you.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 Swanky67

Swanky67
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:01 PM

Posted 20 February 2017 - 10:57 PM

Thank you for your quick response, will have the information for you around 24 hours.

 

 

Have a good one.



#4 Swanky67

Swanky67
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:01 PM

Posted 21 February 2017 - 10:13 AM

Please follow these instructions to run Driver Verifier.

 

 

 

Hey, just followed those instructions and finally restarted my computer. It booted up just like it normally would as if nothing had changed. Is something wrong here, or does this mean everything went smoothly?



#5 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:01:01 PM

Posted 21 February 2017 - 10:33 AM

Nope, that's perfectly fine. You can continue to use your PC normally, but performance will be reduced, which is normal. In a nutshell, Driver Verifier stresses and monitors the drivers to detect illegal function calls or actions that might corrupt the system. Typically it will call a bugcheck (BSOD) when it detects a violation. Since I couldn't tell much from your memory dumps, it is necessary.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#6 Swanky67

Swanky67
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:01 PM

Posted 21 February 2017 - 01:03 PM

Nope, that's perfectly fine. You can continue to use your PC normally, but performance will be reduced, which is normal. In a nutshell, Driver Verifier stresses and monitors the drivers to detect illegal function calls or actions that might corrupt the system. Typically it will call a bugcheck (BSOD) when it detects a violation. Since I couldn't tell much from your memory dumps, it is necessary.

 

Hey thanks for the speedy response yet again.

 

I don't mean to sound ungrateful but is it really necessary to keep my computer in this state for 24 hours? It's affecting my performance a lot lol.



#7 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:01:01 PM

Posted 21 February 2017 - 01:15 PM

Yes, unfortunately, it is. We need Driver Verifier's help to pinpoint the driver.

 

Thank you for your understanding.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#8 Swanky67

Swanky67
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:01 PM

Posted 22 February 2017 - 11:39 AM

Yes, unfortunately, it is. We need Driver Verifier's help to pinpoint the driver.

 

Thank you for your understanding.

 

It's been on for 24 hours and the computer ran normally no problem. I just restarted the computer. I just wanted if I am done with that and the processing power of my computer should have returned to normal, correct?



#9 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:01:01 PM

Posted 22 February 2017 - 11:48 AM

Strange... :(

Let's try to have a look at MEMORY.DMP:

• Press and hold the Windows Key + R on your keyboard at the same time.
• In the Run box, type in %WinDir% and hit Enter on your keyboard.
• Find the file MEMORY.DMP and copy/paste it on to your Desktop.
• Zip up MEMORY.DMP (use .ZIP please!!!) and upload it to Dropbox (since you use Dropbox).


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#10 Swanky67

Swanky67
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:01 PM

Posted 22 February 2017 - 11:59 AM

Strange... :(

Let's try to have a look at MEMORY.DMP:

• Press and hold the Windows Key + R on your keyboard at the same time.
• In the Run box, type in %WinDir% and hit Enter on your keyboard.
• Find the file MEMORY.DMP and copy/paste it on to your Desktop.
• Zip up MEMORY.DMP (use .ZIP please!!!) and upload it to Dropbox (since you use Dropbox).

 

This is from 2/19/2017 10:36 pm. It was the only MEMORY.DMP file in the windows folder.

 

https://www.dropbox.com/s/9jhkre93dyrtfhd/MEMORY.zip?dl=0

 

Did I do something wrong? I noticed a definite decrease in performance in my computer when I followed the instructions but was something supposed to happen at the end of it?



#11 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:01:01 PM

Posted 22 February 2017 - 12:22 PM

Yes, you were supposed to disable Driver Verifier. :) There are instructions in the Driver Verifier guide.

I had a look at MEMORY.DMP, and it blamed the following drivers:

fffff800`04006a10  fffff880`04e71de8*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
 iusb3xhc+0x6fde8
fffff800`04006778  fffff880`0f53058d*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x28658d
fffff800`040063d0  fffff880`0586a040*** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys
 bcmwl664+0x36040
fffff800`040052c8  fffff880`04a443de*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
 IDSvia64+0x443de
fffff800`04005148  fffff880`03e2f0a2*** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS
 SYMNETS+0x190a2

The bugcheck was a STOP 0x0000001A: MEMORY_MANAGEMENT. However, I saw that NTFS.sys was referenced many times. This probably points to virtual memory corruption. I'd like you to perform a CHKDSK:

:step1: Check Disk

WARNING: It is recommended that you backup ALL your files. If CHKDSK finds and repairs a corrupted sector, you may lose your data.
 
• Open Start, and in the Search programs and files box, type cmd.
• Right-click on cmd, select Run as administrator, and accept any User Account Control prompts.
• In the Elevated Command Prompt type:

chkdsk /R

• You should see this message:

The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process.  Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

• Type Y and hit Enter on your keyboard.
• Restart your computer and CHKDSK will run.
 
Once CHKDSK is compete, we need the log:
 
• Open the Start Menu, and in the Search programs and files box, type powershell.exe.
• Right-click on powershell.exe, select Run as administrator, and accept any User Account Control prompts.
• Copy this command:

Get-WinEvent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file $Env:UserProfile\Desktop\CHKDSKResults.txt

Right-click in Powershell to paste the command.
• You will find CHKDSKResults.txt on your Desktop. Copy/paste the log in your next reply.

Thanks.

 


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#12 Swanky67

Swanky67
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:01 PM

Posted 22 February 2017 - 03:16 PM

TimeCreated : 2/22/2017 2:07:57 PM
Message     : 
              
              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)...
                531200 file records processed.                                 
                      
              File verification completed.
                1142 large file records processed.                             
                    
                0 bad file records processed.                                  
                 
                0 EA records processed.                                        
                 
                47 reparse records processed.                                  
                  
              CHKDSK is verifying indexes (stage 2 of 5)...
                693154 index entries processed.                                
                      
              Index verification completed.
                0 unindexed files scanned.                                     
                 
                0 unindexed files recovered.                                   
                 
              CHKDSK is verifying security descriptors (stage 3 of 5)...
                531200 file SDs/SIDs processed.                                
                      
              Cleaning up 139 unused index entries from index $SII of file 0x9.
              Cleaning up 139 unused index entries from index $SDH of file 0x9.
              Cleaning up 139 unused security descriptors.
              Security descriptor verification completed.
                80978 data files processed.                                    
                     
              CHKDSK is verifying Usn Journal...
                35658216 USN bytes processed.                                  
                        
              Usn Journal verification completed.
              CHKDSK is verifying file data (stage 4 of 5)...
                531184 files processed.                                        
                      
              File data verification completed.
              CHKDSK is verifying free space (stage 5 of 5)...
                21127039 free clusters processed.                              
                        
              Free space verification is complete.
              Windows has checked the file system and found no problems.
              
               468616188 KB total disk space.
               383332764 KB in 207762 files.
                  127160 KB in 80979 indexes.
                       0 KB in bad sectors.
                  648108 KB in use by the system.
                   65536 KB occupied by the log file.
                84508156 KB available on disk.
              
                    4096 bytes in each allocation unit.
               117154047 total allocation units on disk.
                21127039 allocation units available on disk.
              
              Internal Info:
              00 1b 08 00 f1 67 04 00 30 c7 07 00 00 00 00 00  .....g..0.......
              8d 01 00 00 2f 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.
              
 
TimeCreated : 2/13/2017 10:32:56 AM
Message     : 
              
              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 3)...
                531200 file records processed.                                 
                      
              File verification completed.
                1315 large file records processed.                             
                    
                0 bad file records processed.                                  
                 
                0 EA records processed.                                        
                 
                47 reparse records processed.                                  
                  
              CHKDSK is verifying indexes (stage 2 of 3)...
                641484 index entries processed.                                
                      
              Index verification completed.
                0 unindexed files scanned.                                     
                 
                0 unindexed files recovered.                                   
                 
              CHKDSK is verifying security descriptors (stage 3 of 3)...
                531200 file SDs/SIDs processed.                                
                      
              Cleaning up 405 unused index entries from index $SII of file 0x9.
              Cleaning up 405 unused index entries from index $SDH of file 0x9.
              Cleaning up 405 unused security descriptors.
              Security descriptor verification completed.
                55143 data files processed.                                    
                     
              CHKDSK is verifying Usn Journal...
                37642120 USN bytes processed.                                  
                        
              Usn Journal verification completed.
              Windows has checked the file system and found no problems.
              
               468616188 KB total disk space.
               345648908 KB in 183670 files.
                  114184 KB in 55144 indexes.
                       0 KB in bad sectors.
                  650148 KB in use by the system.
                   65536 KB occupied by the log file.
               122202948 KB available on disk.
              
                    4096 bytes in each allocation unit.
               117154047 total allocation units on disk.
                30550737 allocation units available on disk.
              
              Internal Info:
              00 1b 08 00 ea a4 03 00 19 a6 06 00 00 00 00 00  ................
              50 01 00 00 2f 00 00 00 00 00 00 00 00 00 00 00  P.../...........
              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.
              
 
TimeCreated : 1/7/2017 2:24:07 PM
Message     : 
              
              Checking file system on C:
              The type of the file system is NTFS.
              
              
              One of your disks needs to be checked for consistency. You
              may cancel the disk check, but it is strongly recommended
              that you continue.
              Windows will now check the disk.                         
              
              CHKDSK is verifying files (stage 1 of 3)...
              Attribute record of type 0x80 and instance tag 0x3 is cross linke
              d
              starting at 0x5151d4 for possibly 0x1 clusters.
              Some clusters occupied by attribute of type 0x80 and instance tag
               0x3
              in file 0x18c98 is already in use.
              Deleting corrupt attribute record (128, "")
              from file record segment 101528.
              Attribute record of type 0x80 and instance tag 0x3 is cross linke
              d
              starting at 0xefdab5 for possibly 0x1 clusters.
              Some clusters occupied by attribute of type 0x80 and instance tag
               0x3
              in file 0x1f60b is already in use.
              Deleting corrupt attribute record (128, "")
              from file record segment 128523.
              Attribute record of type 0x80 and instance tag 0x4 is cross linke
              d
              starting at 0x39aadf for possibly 0x71 clusters.
              Some clusters occupied by attribute of type 0x80 and instance tag
               0x4
              in file 0x1f610 is already in use.
              Deleting corrupt attribute record (128, "")
              from file record segment 128528.
                531200 file records processed.                                 
                      
              File verification completed.
                1066 large file records processed.                             
                    
                0 bad file records processed.                                  
                 
                0 EA records processed.                                        
                 
                1008 reparse records processed.                                
                    
              CHKDSK is verifying indexes (stage 2 of 3)...
              The two index entries of length 0x58 and 0x60 are either identica
              l
              or appear in the wrong order.
              20 00 38 00 00 00 00 00 58 00 10 00 00 00 00 00   .8.....X.......
              33 b4 1f d5 12 5d e6 11 a9 2d 1c 1b 0d 01 48 26  3....]...-....H&
              0a 2c 01 00 00 00 b6 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
              00 00 00 00 00 00 00 00 0c 00 00 00 00 00 00 00  ................
              6c 00 61 00 74 00 61 00 00 00 00 00 00 00 00 00  l.a.t.a.........
              -----------------------------------------------------------------
              -----
              20 00 38 00 00 00 00 00 60 00 10 00 01 00 00 00   .8.....`.......
              33 b4 1f d5 12 5d e6 11 a9 2d 1c 1b 0d 01 48 26  3....]...-....H&
              0a 2c 01 00 00 00 b6 00 9a 26 12 d6 35 0d 43 46  .,.......&..5.CF
              a9 d8 7e 89 38 e9 9e e5 33 b4 1f d5 12 5d e6 11  ..~.8...3....]..
              a9 2d 1c 1b 0d 01 48 26 00 00 00 00 00 00 00 00  .-....H&........
              00 00 00 00 00 00 00 00 2f 00 00 00 00 00 00 00  ......../.......
              20 00 38 00 00 00 00 00 60 00 10 00 01 00 00 00   .8.....`.......
              Sorting index $O in file 25.
              The object id in file 0x3 does not appear in the object
              id index in file 0x19.
              Inserting an index entry into index $O of file 25.
              Index entry Report.wer of index $I30 in file 0x5943 points to unu
              sed file 0x42ec5.
              Deleting index entry Report.wer in index $I30 of file 22851.
              The file reference 0xe9000000005943 of index entry NO9416~1 of in
              dex $I30
              with parent 0x1361d is not the same as 0xe8000000005943.
              Deleting index entry NO9416~1 in index $I30 of file 79389.
              The file reference 0x1d00000000a7ec of index entry NO98ED~1 of in
              dex $I30
              with parent 0x1361d is not the same as 0x1c00000000a7ec.
              Deleting index entry NO98ED~1 in index $I30 of file 79389.
              Index entry NonCritical_x64_7efcf8572ce122df90381734faa8afdf75518
              e29_cab_0bc48f82 of index $I30 in file 0x1361d points to unused f
              ile 0x42eb6.
              Deleting index entry NonCritical_x64_7efcf8572ce122df90381734faa8
              afdf75518e29_cab_0bc48f82 in index $I30 of file 79389.
              The file reference 0x1d00000000a7ec of index entry NonCritical_x6
              4_ba606e5787c8c5fa59c399fd1c74d36b8348b22d_cab_13ccd161 of index 
              $I30
              with parent 0x1361d is not the same as 0x1c00000000a7ec.
              Deleting index entry NonCritical_x64_ba606e5787c8c5fa59c399fd1c74
              d36b8348b22d_cab_13ccd161 in index $I30 of file 79389.
              The file reference 0xe9000000005943 of index entry NonCritical_x6
              4_bd72832a98c07a48883316be53d8d8c334daa29_cab_13ccc6e6 of index $
              I30
              with parent 0x1361d is not the same as 0xe8000000005943.
              Deleting index entry NonCritical_x64_bd72832a98c07a48883316be53d8
              d8c334daa29_cab_13ccc6e6 in index $I30 of file 79389.
              Index entry NonCritical_x64_d2215d630f577ddef4464d3f0b2326c3dd874
              6_cab_0bc4978d of index $I30 in file 0x1361d points to unused fil
              e 0x42ebb.
              Deleting index entry NonCritical_x64_d2215d630f577ddef4464d3f0b23
              26c3dd8746_cab_0bc4978d in index $I30 of file 79389.
                649662 index entries processed.                                
                      
              Index verification completed.
              CHKDSK is scanning unindexed files for reconnect to their origina
              l directory.
              Recovering orphaned file NO4260~1 (22851) into directory file 793
              89.
              Recovering orphaned file NonCritical_x64_1d35b80a5154488b340fd09f
              4eb99e773d3392_cab_0bc4b5b7 (22851) into directory file 79389.
              Recovering orphaned file NOEA41~1 (42988) into directory file 793
              89.
              Recovering orphaned file NonCritical_x64_fcd3d224ca8bd461c4dca7e6
              48fef6e125073de_cab_0bc4cadc (42988) into directory file 79389.
              Recovering orphaned file GPBCAE~1.DMP (72768) into directory file
               269545.
              Recovering orphaned file GPUTweakII.exe.2544.dmp (72768) into dir
              ectory file 269545.
              Recovering orphaned file NonCritical_x64_7ddc7e2d2a6d21b3ab18c31a
              1d1667307a1bb056_cab_127a79ef (114447) into directory file 79389.
                10 unindexed files scanned.                                    
                  
              Recovering orphaned file NonCritical_x64_cf4d16b1a7c97adfd188d34d
              297dab5ab41f710_cab_127ac476 (115289) into directory file 79389.
              CHKDSK is recovering remaining unindexed files.
                5 unindexed files recovered.                                   
                 
              CHKDSK is verifying security descriptors (stage 3 of 3)...
                531200 file SDs/SIDs processed.                                
                      
              Cleaning up 542 unused index entries from index $SII of file 0x9.
              Cleaning up 542 unused index entries from index $SDH of file 0x9.
              Cleaning up 542 unused security descriptors.
              Security descriptor verification completed.
              Inserting data attribute into file 101528.
              Inserting data attribute into file 128523.
              Inserting data attribute into file 128528.
                59235 data files processed.                                    
                     
              CHKDSK is verifying Usn Journal...
                35989552 USN bytes processed.                                  
                        
              Usn Journal verification completed.
              Correcting errors in the master file table's (MFT) BITMAP attribu
              te.
              Correcting errors in the Volume Bitmap.
              Windows has made corrections to the file system.
              
               468616188 KB total disk space.
               438214200 KB in 293304 files.
                  155040 KB in 59236 indexes.
                       0 KB in bad sectors.
                  650868 KB in use by the system.
                   65536 KB occupied by the log file.
                29596080 KB available on disk.
              
                    4096 bytes in each allocation unit.
               117154047 total allocation units on disk.
                 7399020 allocation units available on disk.
              
              Internal Info:
              00 1b 08 00 28 61 05 00 9d ac 09 00 00 00 00 00  ....(a..........
              51 03 00 00 f0 03 00 00 00 00 00 00 00 00 00 00  Q...............
              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.


#13 Swanky67

Swanky67
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:01 PM

Posted 22 February 2017 - 03:19 PM

I'm a little confused on the driver ordeal. I did exactly what the instructions told me to do earlier and no results.



#14 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:01:01 PM

Posted 22 February 2017 - 04:07 PM

Thanks for the log. Please don't worry about Driver Verifier — just turn it off.

From your CHKDSK log, I noticed that CHKDSK ran by itself twice. This may point to a failing drive. Can you follow these instructions by TsVk! (thanks TsVk!!) to check the integrity of ALL your drives? Of course, post here, not there. :thumbup2:


Edited by bwv848, 22 February 2017 - 04:07 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#15 Swanky67

Swanky67
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:01 PM

Posted 23 February 2017 - 05:20 AM

Ran those tests on all of my three hard drives nothing wrong with them. I ran memtest for about 10 hours. A lot of errors.

 

So it looks like we've exhausted all of our resources, the ram test was the only one that got any results.

 

So how do I determine if it's my motherboard ram slots or my actual ram? My ram is pretty new, drr4 ram I got about two months ago.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users