A acole Active member Joined Jan 20, 2016 Posts 26 Jan 27, 2016 #21 Just want to add something further to the following comment (quoted below) to not confuse things. Sorry if I don't sound very computer savvy. This is my brothers PC and he is the guy who knows more about this than I do. Comment made earlier : "He (my brother) stated he updated the BIOS (to F8 version I think) when the manufacturer advised him to do so when the motherboard was repaired (I think the video card slot or something was fixed). He was advised that the BIOS version was fine and there was no reason to update it and that updating it could cause more problems, especially with the RAID 0." What I meant to say is that the manufacturer told him to update the BIOS version, to I think, "F8" when he got the motherboard back from the repair shop. This was back in 2011. Then a couple of months ago, my brother contacted the manufacturer about the BSOD and they said that it is very rare that a BIOS problem causes intermittent BSOD's. They further added that updating it to the latest BIOS version is not advisable, unless the system fails to boot entirely because of something to do with the BIOS itself and usually BIOS problems result in PC's not booting at all. The support people he spoke to (or emailed, I don't know), gave him a link to their website that actually says BIOS updates aren't recommended. On top of that I don't think I am skilled enough with that process! :) Hope this clarifies things. Anyway, look forward to getting help here and seeing how great you guys have been so far - I am excited about the prospects of getting the BSOD problem solved. My brother will be really happy if he gets back and the system is back to normal. Thanks in advance, Joe.
Just want to add something further to the following comment (quoted below) to not confuse things. Sorry if I don't sound very computer savvy. This is my brothers PC and he is the guy who knows more about this than I do. Comment made earlier : "He (my brother) stated he updated the BIOS (to F8 version I think) when the manufacturer advised him to do so when the motherboard was repaired (I think the video card slot or something was fixed). He was advised that the BIOS version was fine and there was no reason to update it and that updating it could cause more problems, especially with the RAID 0." What I meant to say is that the manufacturer told him to update the BIOS version, to I think, "F8" when he got the motherboard back from the repair shop. This was back in 2011. Then a couple of months ago, my brother contacted the manufacturer about the BSOD and they said that it is very rare that a BIOS problem causes intermittent BSOD's. They further added that updating it to the latest BIOS version is not advisable, unless the system fails to boot entirely because of something to do with the BIOS itself and usually BIOS problems result in PC's not booting at all. The support people he spoke to (or emailed, I don't know), gave him a link to their website that actually says BIOS updates aren't recommended. On top of that I don't think I am skilled enough with that process! :) Hope this clarifies things. Anyway, look forward to getting help here and seeing how great you guys have been so far - I am excited about the prospects of getting the BSOD problem solved. My brother will be really happy if he gets back and the system is back to normal. Thanks in advance, Joe.
Xer Sysnative Staff, BSOD Kernel Dump Senior Analyst Staff member Joined Nov 10, 2015 Posts 117 Location Canada Jan 27, 2016 #22 Hi Joe, Please perform the instructions listed in the "Blue Screen of Death (BSOD) Posting Instructions" thread, except in step 4, please post back here instead of making a new thread. That will give us the info we need in order to be able to start helping you. Edit: I see you already ran the collection app on BleepingComputer, so you can re-attach that zip here. If there have been more crashes since you ran that collection, it would still be appreciated if you could run a new collection and post it here. Last edited: Jan 27, 2016
Hi Joe, Please perform the instructions listed in the "Blue Screen of Death (BSOD) Posting Instructions" thread, except in step 4, please post back here instead of making a new thread. That will give us the info we need in order to be able to start helping you. Edit: I see you already ran the collection app on BleepingComputer, so you can re-attach that zip here. If there have been more crashes since you ran that collection, it would still be appreciated if you could run a new collection and post it here.
A acole Active member Joined Jan 20, 2016 Posts 26 Jan 27, 2016 #23 Hi, I will run new tests because I don't even know if I have the old logs anymore. I am just about to go to bed now (4am here), so I will report back tomorrow some time. Cheers, Joe
Hi, I will run new tests because I don't even know if I have the old logs anymore. I am just about to go to bed now (4am here), so I will report back tomorrow some time. Cheers, Joe
A acole Active member Joined Jan 20, 2016 Posts 26 Jan 27, 2016 #24 Hi, I couldn't sleep so I decided to run those tasks requested. Unfortunately I could not get perfmon /report to work. I waited about 30 minutes and it sat on "generating report for 60 seconds". SysnativeFileCollectionApp ran fine and I have attached it. The answer to the questions from step 5. · OS - Windows 8.1, 8, 7, Vista ? Windows 10 Pro · x86 (32-bit) or x64 ? 64 bit · What was original installed OS on system? Windows 7, then we clean installed Windows 10 about 2 months ago. · Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Retail Version of 7, but with the same code we got a Windows 10 key. · Age of system (hardware) RAM and Video Card are 1 month old, rest of system was purchased in 2011. We overclocked the system in 2013 I believe. We only started getting issues 3-4 months ago, maybe 5 months. We initially thought RAM was the problem because the BSOD said "Memory Management", So we got brand new RAM from a friend and replaced the old RAM. Then we got a new video card because our old one was outdated. So we can be pretty sure it's not the RAM or the Video Card I guess. · Age of OS installation - have you re-installed the OS? A clean install (not update) of Windows 10 was done a couple of months ago. · CPU i7 2600k · Video Card GTX980 · MotherBoard - (if NOT a laptop) Gigabyte ud7-b3 · Power Supply - brand & wattage (if laptop, skip this one) Corsair 1200w · System Manufacturer We purchased parts and had a shop build the pc for us. · Exact model number (if laptop, check label on bottom) n/a · Laptop or Desktop? Desktop PC. Hope this helps, Cheers, Joe Attachments SysnativeFileCollectionApp.zip 1,006.7 KB · Views: 2
Hi, I couldn't sleep so I decided to run those tasks requested. Unfortunately I could not get perfmon /report to work. I waited about 30 minutes and it sat on "generating report for 60 seconds". SysnativeFileCollectionApp ran fine and I have attached it. The answer to the questions from step 5. · OS - Windows 8.1, 8, 7, Vista ? Windows 10 Pro · x86 (32-bit) or x64 ? 64 bit · What was original installed OS on system? Windows 7, then we clean installed Windows 10 about 2 months ago. · Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Retail Version of 7, but with the same code we got a Windows 10 key. · Age of system (hardware) RAM and Video Card are 1 month old, rest of system was purchased in 2011. We overclocked the system in 2013 I believe. We only started getting issues 3-4 months ago, maybe 5 months. We initially thought RAM was the problem because the BSOD said "Memory Management", So we got brand new RAM from a friend and replaced the old RAM. Then we got a new video card because our old one was outdated. So we can be pretty sure it's not the RAM or the Video Card I guess. · Age of OS installation - have you re-installed the OS? A clean install (not update) of Windows 10 was done a couple of months ago. · CPU i7 2600k · Video Card GTX980 · MotherBoard - (if NOT a laptop) Gigabyte ud7-b3 · Power Supply - brand & wattage (if laptop, skip this one) Corsair 1200w · System Manufacturer We purchased parts and had a shop build the pc for us. · Exact model number (if laptop, check label on bottom) n/a · Laptop or Desktop? Desktop PC. Hope this helps, Cheers, Joe
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore Jan 27, 2016 #25 Hi. . . If there is a BIOS update available, it should be installed. A non-updated BIOS could indeed cause BSODs as you're dealing with an unstable system. Speaking of which -- (unstable systems) - all over-clocking has been reset to factory system default settings...? If not, please do so as over-clocking definitely can easily cause BSODs. 3 of the 5 BSODs had bugcheck 0x1a - severe memory management error; the others: 0x12b - hardware memory error 0x7a (0xc0000005,,,) - requested page of kernel data could not be read into RAM; exception error code = 0xc0000005 = memory access violation Read More: Code: BugCheck 1A, {411, ffffc000506f6060, edc00002340f78a4, ffffc0004048d368} BugCheck 7A, {1, ffffffffc0000005, ffffe001fc24a6c0, fffff6fb5ffce000} BugCheck 1A, {41793, fffff6800000cbf8, 5, 4} BugCheck 1A, {41793, fffff68000040bf8, 3, 2} BugCheck 12B, {ffffffffc00002c4, a15, 2bfa2780000, ffffd00027b1a000} You have 2 HDDs - a 500GB + a 1TB. Run SeaTools for DOS, LONG test on both - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html I know the RAM is new, but you're going to have to test it. I've seen brand new RAM bad right out of the box. Run memtest86+; 1 stick at a time; alternate the slots; 7 passes MINIMUM - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html Run Driver Verifier - see if any 3rd party drivers are flagged - https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html Regards. . . jcgriff2 BSOD SUMMARY Code: Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012016-7609-01.dmp] Built by: 10586.63.amd64fre.th2_release.160104-1513 Debug session time: Wed Jan 20 05:13:47.295 2016 (UTC - 5:00) System Uptime: 0 days 8:11:58.937 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+270df ) BUGCHECK_STR: 0x1a_411 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: NexusClient.ex FAILURE_BUCKET_ID: 0x1a_411_nt!_??_::FNODOBFM::_string_ Bugcheck code 0000001A Arguments 00000000`00000411 ffffc000`506f6060 edc00002`340f78a4 ffffc000`4048d368 BiosVersion = F8 BiosReleaseDate = 07/19/2011 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = Z68X-UD7-B3 MaxSpeed: 3400 CurrentSpeed: 3401 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012016-8031-01.dmp] Built by: 10586.63.amd64fre.th2_release.160104-1513 Debug session time: Tue Jan 19 20:57:58.000 2016 (UTC - 5:00) System Uptime: 4 days 9:09:23.056 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f4f ) BUGCHECK_STR: 0x7a_c0000005 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: ShellExperienc FAILURE_BUCKET_ID: 0x7a_c0000005_nt!_??_::FNODOBFM::_string_ Bugcheck code 0000007A Arguments 00000000`00000001 ffffffff`c0000005 ffffe001`fc24a6c0 fffff6fb`5ffce000 BiosVersion = F8 BiosReleaseDate = 07/19/2011 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = Z68X-UD7-B3 MaxSpeed: 3400 CurrentSpeed: 3401 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012116-6765-01.dmp] Built by: 10586.63.amd64fre.th2_release.160104-1513 Debug session time: Wed Jan 20 22:50:00.344 2016 (UTC - 5:00) System Uptime: 0 days 9:50:51.972 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ed59 ) BUGCHECK_STR: 0x1a_41793 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: nvSCPAPISvr.ex FAILURE_BUCKET_ID: 0x1a_41793_nt!_??_::FNODOBFM::_string_ Bugcheck code 0000001A Arguments 00000000`00041793 fffff680`0000cbf8 00000000`00000005 00000000`00000004 BiosVersion = F8 BiosReleaseDate = 07/19/2011 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = Z68X-UD7-B3 MaxSpeed: 3400 CurrentSpeed: 3401 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012216-6687-01.dmp] Built by: 10586.63.amd64fre.th2_release.160104-1513 Debug session time: Fri Jan 22 01:39:24.595 2016 (UTC - 5:00) System Uptime: 1 days 0:15:51.223 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ed59 ) BUGCHECK_STR: 0x1a_41793 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: GameScannerSer FAILURE_BUCKET_ID: 0x1a_41793_nt!_??_::FNODOBFM::_string_ Bugcheck code 0000001A Arguments 00000000`00041793 fffff680`00040bf8 00000000`00000003 00000000`00000002 BiosVersion = F8 BiosReleaseDate = 07/19/2011 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = Z68X-UD7-B3 MaxSpeed: 3400 CurrentSpeed: 3401 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012016-7578-01.dmp] Built by: 10586.63.amd64fre.th2_release.160104-1513 Debug session time: Wed Jan 20 07:35:49.493 2016 (UTC - 5:00) System Uptime: 0 days 2:21:15.133 Probably caused by : hardware ( REGION_PAGED_OUT ) BUGCHECK_STR: PAGE_NOT_ZERO DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: PAGE_NOT_ZERO_REGION_PAGED_OUT Bugcheck code 0000012B Arguments ffffffff`c00002c4 00000000`00000a15 000002bf`a2780000 ffffd000`27b1a000 BiosVersion = F8 BiosReleaseDate = 07/19/2011 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = Z68X-UD7-B3 MaxSpeed: 3400 CurrentSpeed: 3401 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Hi. . . If there is a BIOS update available, it should be installed. A non-updated BIOS could indeed cause BSODs as you're dealing with an unstable system. Speaking of which -- (unstable systems) - all over-clocking has been reset to factory system default settings...? If not, please do so as over-clocking definitely can easily cause BSODs. 3 of the 5 BSODs had bugcheck 0x1a - severe memory management error; the others: 0x12b - hardware memory error 0x7a (0xc0000005,,,) - requested page of kernel data could not be read into RAM; exception error code = 0xc0000005 = memory access violation Read More: Code: BugCheck 1A, {411, ffffc000506f6060, edc00002340f78a4, ffffc0004048d368} BugCheck 7A, {1, ffffffffc0000005, ffffe001fc24a6c0, fffff6fb5ffce000} BugCheck 1A, {41793, fffff6800000cbf8, 5, 4} BugCheck 1A, {41793, fffff68000040bf8, 3, 2} BugCheck 12B, {ffffffffc00002c4, a15, 2bfa2780000, ffffd00027b1a000} You have 2 HDDs - a 500GB + a 1TB. Run SeaTools for DOS, LONG test on both - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html I know the RAM is new, but you're going to have to test it. I've seen brand new RAM bad right out of the box. Run memtest86+; 1 stick at a time; alternate the slots; 7 passes MINIMUM - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html Run Driver Verifier - see if any 3rd party drivers are flagged - https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html Regards. . . jcgriff2 BSOD SUMMARY Code: Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012016-7609-01.dmp] Built by: 10586.63.amd64fre.th2_release.160104-1513 Debug session time: Wed Jan 20 05:13:47.295 2016 (UTC - 5:00) System Uptime: 0 days 8:11:58.937 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+270df ) BUGCHECK_STR: 0x1a_411 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: NexusClient.ex FAILURE_BUCKET_ID: 0x1a_411_nt!_??_::FNODOBFM::_string_ Bugcheck code 0000001A Arguments 00000000`00000411 ffffc000`506f6060 edc00002`340f78a4 ffffc000`4048d368 BiosVersion = F8 BiosReleaseDate = 07/19/2011 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = Z68X-UD7-B3 MaxSpeed: 3400 CurrentSpeed: 3401 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012016-8031-01.dmp] Built by: 10586.63.amd64fre.th2_release.160104-1513 Debug session time: Tue Jan 19 20:57:58.000 2016 (UTC - 5:00) System Uptime: 4 days 9:09:23.056 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f4f ) BUGCHECK_STR: 0x7a_c0000005 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: ShellExperienc FAILURE_BUCKET_ID: 0x7a_c0000005_nt!_??_::FNODOBFM::_string_ Bugcheck code 0000007A Arguments 00000000`00000001 ffffffff`c0000005 ffffe001`fc24a6c0 fffff6fb`5ffce000 BiosVersion = F8 BiosReleaseDate = 07/19/2011 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = Z68X-UD7-B3 MaxSpeed: 3400 CurrentSpeed: 3401 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012116-6765-01.dmp] Built by: 10586.63.amd64fre.th2_release.160104-1513 Debug session time: Wed Jan 20 22:50:00.344 2016 (UTC - 5:00) System Uptime: 0 days 9:50:51.972 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ed59 ) BUGCHECK_STR: 0x1a_41793 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: nvSCPAPISvr.ex FAILURE_BUCKET_ID: 0x1a_41793_nt!_??_::FNODOBFM::_string_ Bugcheck code 0000001A Arguments 00000000`00041793 fffff680`0000cbf8 00000000`00000005 00000000`00000004 BiosVersion = F8 BiosReleaseDate = 07/19/2011 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = Z68X-UD7-B3 MaxSpeed: 3400 CurrentSpeed: 3401 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012216-6687-01.dmp] Built by: 10586.63.amd64fre.th2_release.160104-1513 Debug session time: Fri Jan 22 01:39:24.595 2016 (UTC - 5:00) System Uptime: 1 days 0:15:51.223 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ed59 ) BUGCHECK_STR: 0x1a_41793 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: GameScannerSer FAILURE_BUCKET_ID: 0x1a_41793_nt!_??_::FNODOBFM::_string_ Bugcheck code 0000001A Arguments 00000000`00041793 fffff680`00040bf8 00000000`00000003 00000000`00000002 BiosVersion = F8 BiosReleaseDate = 07/19/2011 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = Z68X-UD7-B3 MaxSpeed: 3400 CurrentSpeed: 3401 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012016-7578-01.dmp] Built by: 10586.63.amd64fre.th2_release.160104-1513 Debug session time: Wed Jan 20 07:35:49.493 2016 (UTC - 5:00) System Uptime: 0 days 2:21:15.133 Probably caused by : hardware ( REGION_PAGED_OUT ) BUGCHECK_STR: PAGE_NOT_ZERO DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: PAGE_NOT_ZERO_REGION_PAGED_OUT Bugcheck code 0000012B Arguments ffffffff`c00002c4 00000000`00000a15 000002bf`a2780000 ffffd000`27b1a000 BiosVersion = F8 BiosReleaseDate = 07/19/2011 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = Z68X-UD7-B3 MaxSpeed: 3400 CurrentSpeed: 3401 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Xer Sysnative Staff, BSOD Kernel Dump Senior Analyst Staff member Joined Nov 10, 2015 Posts 117 Location Canada Jan 27, 2016 #26 We overclocked the system in 2013 I believe Click to expand... Thanks for the update. Which components had you overclocked? More specifically, I'd be curious to know if the RAM was ever overclocked. Also: has the CMOS ever been reset/have the BIOS settings been defaulted since the crashing started?
We overclocked the system in 2013 I believe Click to expand... Thanks for the update. Which components had you overclocked? More specifically, I'd be curious to know if the RAM was ever overclocked. Also: has the CMOS ever been reset/have the BIOS settings been defaulted since the crashing started?
A acole Active member Joined Jan 20, 2016 Posts 26 Jan 27, 2016 #27 Hi, I want to apologise in advance if I am not the most computer savvy. The little that I know I have actually picked up only recently, as I am usually a console guy but in the last year or so I have been living with my bro (house sitting/babysitting him) and unfortunately I have seen my brother get really frustrated with this system. Thankfully I have gotten a hold of my brother on Facebook so I can ask him some questions again and get some feedback. A lot of this stuff I think is already in the first page link from bleepingcomputer. There are some tests I possibly cannot do because of my skill level and also because I don't have a USB or a CD Burn disc thing. :grin1: I will do my best where I can. I won't be able to do the BIOS update because my brother and the manufacturer said not to. Unfortunately this is not my pc and my brother is just worried that updating the BIOS could cause another issue, where the computer will just stop working altogether. As stated this motherboard is no longer made and last time he had a problem with the video card pci slot and it took 4 months for him to get his system back. The manufacturer told him to install the F8 version at the time. The problem even back then, when the PC was only days old, was that this was a high end motherboard and they had to send it overseas for repair and it took a long time for them to figure out the problem (or so they told us). This is the comment from the manufacturer, curtesy of my brother... "As per Gigabyte Support Download 'Because BIOS flashing is potentially risky, if you do not encounter problems using the current version of BIOS, it is recommended that you not flash the BIOS. To flash the BIOS, do it with caution. Inadequate BIOS flashing may result in system malfunction.' Considering your current system configuration and recent lengthyreturn merchandise authorization (RMA) and the potential risk-reward of flashing the BIOS to newer versions, it is quite possibly in your best interest to remain with the current version (F8). Unless there is evident requirement to do so in terms of new driver functionality for new system devices or for troubleshooting your product if such it refuses to boot to Windows, then we would recommend to flash the motherboard again. " I honestly don't understand a word of that, but my brother was pretty stubborn about this BIOS update, even when bleepingcomputer guys asked for it to be done. I think the first time he did it was when the pc screwed up (not 100% sure on that though), then when the motherboard returned after 4 months (yes it took 4 months and my brother even took the manufacturer to Fair Trading to get compensation) he was told to try and update it to F8 - and at the time he said F9 was the latest. He has no idea why they chose F8. My brother was really upset because he wondered why they wouldn't first do it and test it, instead of sending it back and asking to flash it and hope for the best? Maybe you guys might know why? With regards to Memtest... Will this test the motherboard slots, like where you plug the RAM in? I know you said you saw brand new RAM fail. But if you read the link on the first page - we went through this troubleshooting before. We tried FOUR different RAM sets, 4GB, 8GB and 16GB (twice, two different products). One set of RAM we found was faulty, because as soon as we put it into our friends pc, his pc wouldn't boot. We have since thrown that RAM away. We tried our friends RAM, some old backup RAM we had and then BRAND new RAM we only just opened right out of the packet - that is 4 sets of RAM. The chances that ALL the RAM is faulty seems a bit low. I don't know much about computers, but wouldn't it be best to focus elsewhere unless memtest checks the motherboard slots? Also all of the BSOD you stated "memory" issues. If it is more than likely NOT the RAM what could it be? Drivers or the Motherboard? Regarding the overclock. Yes I have just put it back to default, but as stated previously - even with the "optimized" settings in the BIOS, we still got Blue Screen errors. Also only the CPU was overclocked, nothing else is overclocked - it is all running as per the settings that came out of the box. Sorry I don't know what "CMOS ever been reset" means. Does that mean just setting BIOS to default settings? The system has run fine for about 2 1/2 years with the overclock 24/7 and as also stated in the first post I ran prime95 (which was advised by a friend) overnight while I slept and it had 0 errors after 6 or so hours. "Driver Verifier" - yes I ran Driver Verifier a few weeks back, for about 8 hours I guess, again while I slept. When I first kicked it off, it had an error with avast I think and a second time with Marvell Driver package (mv91cons.sys). So I uninstalled Avast and I uninstalled the driver package and re-installed the updated ones from the Gigabyte site. I then kicked off driver verifier and this time it booted into Windows and there was no BSOD. So I went to bed, woke up 8 hrs later or so and it was still running. Once I shut it off, I got a BSOD I think later than night - randomly. So even though all the drivers were meant to be fine, I still got the BSOD. This computer has 2 SSD's in RAID 0. It also has a 1TB hard drive for backups and music/movies. I ran chkdsk on them, but I am not sure if anything was found. I looked at your link on how to run the tests but it seems very confusing to me as I am not very skilled. I also don't have a USB or any CD ROMS. Could you help me understand how to run a test on the SSD and HDD in a simpler way? (simple steps) I think I covered all your questions. Sorry if I sound a bit thick headed - as stated I am not the best when it comes to some of these things. I just wish the BSOD errors would just say EXACTLY what the error is, why do they make these computers so difficult to diagnose a problem?
Hi, I want to apologise in advance if I am not the most computer savvy. The little that I know I have actually picked up only recently, as I am usually a console guy but in the last year or so I have been living with my bro (house sitting/babysitting him) and unfortunately I have seen my brother get really frustrated with this system. Thankfully I have gotten a hold of my brother on Facebook so I can ask him some questions again and get some feedback. A lot of this stuff I think is already in the first page link from bleepingcomputer. There are some tests I possibly cannot do because of my skill level and also because I don't have a USB or a CD Burn disc thing. :grin1: I will do my best where I can. I won't be able to do the BIOS update because my brother and the manufacturer said not to. Unfortunately this is not my pc and my brother is just worried that updating the BIOS could cause another issue, where the computer will just stop working altogether. As stated this motherboard is no longer made and last time he had a problem with the video card pci slot and it took 4 months for him to get his system back. The manufacturer told him to install the F8 version at the time. The problem even back then, when the PC was only days old, was that this was a high end motherboard and they had to send it overseas for repair and it took a long time for them to figure out the problem (or so they told us). This is the comment from the manufacturer, curtesy of my brother... "As per Gigabyte Support Download 'Because BIOS flashing is potentially risky, if you do not encounter problems using the current version of BIOS, it is recommended that you not flash the BIOS. To flash the BIOS, do it with caution. Inadequate BIOS flashing may result in system malfunction.' Considering your current system configuration and recent lengthyreturn merchandise authorization (RMA) and the potential risk-reward of flashing the BIOS to newer versions, it is quite possibly in your best interest to remain with the current version (F8). Unless there is evident requirement to do so in terms of new driver functionality for new system devices or for troubleshooting your product if such it refuses to boot to Windows, then we would recommend to flash the motherboard again. " I honestly don't understand a word of that, but my brother was pretty stubborn about this BIOS update, even when bleepingcomputer guys asked for it to be done. I think the first time he did it was when the pc screwed up (not 100% sure on that though), then when the motherboard returned after 4 months (yes it took 4 months and my brother even took the manufacturer to Fair Trading to get compensation) he was told to try and update it to F8 - and at the time he said F9 was the latest. He has no idea why they chose F8. My brother was really upset because he wondered why they wouldn't first do it and test it, instead of sending it back and asking to flash it and hope for the best? Maybe you guys might know why? With regards to Memtest... Will this test the motherboard slots, like where you plug the RAM in? I know you said you saw brand new RAM fail. But if you read the link on the first page - we went through this troubleshooting before. We tried FOUR different RAM sets, 4GB, 8GB and 16GB (twice, two different products). One set of RAM we found was faulty, because as soon as we put it into our friends pc, his pc wouldn't boot. We have since thrown that RAM away. We tried our friends RAM, some old backup RAM we had and then BRAND new RAM we only just opened right out of the packet - that is 4 sets of RAM. The chances that ALL the RAM is faulty seems a bit low. I don't know much about computers, but wouldn't it be best to focus elsewhere unless memtest checks the motherboard slots? Also all of the BSOD you stated "memory" issues. If it is more than likely NOT the RAM what could it be? Drivers or the Motherboard? Regarding the overclock. Yes I have just put it back to default, but as stated previously - even with the "optimized" settings in the BIOS, we still got Blue Screen errors. Also only the CPU was overclocked, nothing else is overclocked - it is all running as per the settings that came out of the box. Sorry I don't know what "CMOS ever been reset" means. Does that mean just setting BIOS to default settings? The system has run fine for about 2 1/2 years with the overclock 24/7 and as also stated in the first post I ran prime95 (which was advised by a friend) overnight while I slept and it had 0 errors after 6 or so hours. "Driver Verifier" - yes I ran Driver Verifier a few weeks back, for about 8 hours I guess, again while I slept. When I first kicked it off, it had an error with avast I think and a second time with Marvell Driver package (mv91cons.sys). So I uninstalled Avast and I uninstalled the driver package and re-installed the updated ones from the Gigabyte site. I then kicked off driver verifier and this time it booted into Windows and there was no BSOD. So I went to bed, woke up 8 hrs later or so and it was still running. Once I shut it off, I got a BSOD I think later than night - randomly. So even though all the drivers were meant to be fine, I still got the BSOD. This computer has 2 SSD's in RAID 0. It also has a 1TB hard drive for backups and music/movies. I ran chkdsk on them, but I am not sure if anything was found. I looked at your link on how to run the tests but it seems very confusing to me as I am not very skilled. I also don't have a USB or any CD ROMS. Could you help me understand how to run a test on the SSD and HDD in a simpler way? (simple steps) I think I covered all your questions. Sorry if I sound a bit thick headed - as stated I am not the best when it comes to some of these things. I just wish the BSOD errors would just say EXACTLY what the error is, why do they make these computers so difficult to diagnose a problem?
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore Jan 28, 2016 #28 acole said: "As per Gigabyte Support Download 'Because BIOS flashing is potentially risky, if you do not encounter problems using the current version of BIOS, it is recommended that you not flash the BIOS. To flash the BIOS, do it with caution. Inadequate BIOS flashing may result in system malfunction.' Click to expand... But you are encountering problems; namely - BSODs. acole said: I don't know much about computers, but wouldn't it be best to focus elsewhere unless memtest checks the motherboard slots? Click to expand... memtest86+ does not check RAM slots, but you sort of do during the test because you run memtest86+ one stick at a time IN EACH SLOT; then move onto the next stick - test in each slot; 7 passes minimum for the same stick in each slot. So - at least 28 passes per stick. acole said: Also all of the BSOD you stated "memory" issues. If it is more than likely NOT the RAM what could it be? Drivers or the Motherboard? Click to expand... "memory issues" does not necessarily mean bad RAM. It could be bad RAM or invalid virtual memory or a driver improperly referencing memory or a driver referencing an invalid memory address. acole said: "Driver Verifier" - yes I ran Driver Verifier a few weeks back, for about 8 hours I guess, again while I slept. When I first kicked it off, it had an error with avast I think and a second time with Marvell Driver package (mv91cons.sys). Click to expand... Good work, but Driver Verifier must run for at least 24 hours - minimum. acole said: This computer has 2 SSD's in RAID 0. It also has a 1TB hard drive for backups and music/movies. Click to expand... Make sure that you check the SSD's manufacturer's support site for SSD firmware upgrades. For the HDD - run SeaTools for DOS, LONG test - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html acole said: I ran chkdsk on them, but I am not sure if anything was found. Click to expand... The results are in the Event Viewer Application log. acole said: I looked at your link on how to run the tests but it seems very confusing to me as I am not very skilled. I also don't have a USB or any CD ROMS. Could you help me understand how to run a test on the SSD and HDD in a simpler way? (simple steps) Click to expand... Find a computer that can burn bootable CD-R discs or USB for memtest86+ and SeaTools. I guess USB would be best considering you can't run CDs! acole said: Sorry if I sound a bit thick headed - as stated I am not the best when it comes to some of these things. I just wish the BSOD errors would just say EXACTLY what the error is, why do they make these computers so difficult to diagnose a problem? Click to expand... Don't worry about your level of expertise. BSODs are rather difficult to figure out as everything is in hex. Regards. . . jcgriff2
acole said: "As per Gigabyte Support Download 'Because BIOS flashing is potentially risky, if you do not encounter problems using the current version of BIOS, it is recommended that you not flash the BIOS. To flash the BIOS, do it with caution. Inadequate BIOS flashing may result in system malfunction.' Click to expand... But you are encountering problems; namely - BSODs. acole said: I don't know much about computers, but wouldn't it be best to focus elsewhere unless memtest checks the motherboard slots? Click to expand... memtest86+ does not check RAM slots, but you sort of do during the test because you run memtest86+ one stick at a time IN EACH SLOT; then move onto the next stick - test in each slot; 7 passes minimum for the same stick in each slot. So - at least 28 passes per stick. acole said: Also all of the BSOD you stated "memory" issues. If it is more than likely NOT the RAM what could it be? Drivers or the Motherboard? Click to expand... "memory issues" does not necessarily mean bad RAM. It could be bad RAM or invalid virtual memory or a driver improperly referencing memory or a driver referencing an invalid memory address. acole said: "Driver Verifier" - yes I ran Driver Verifier a few weeks back, for about 8 hours I guess, again while I slept. When I first kicked it off, it had an error with avast I think and a second time with Marvell Driver package (mv91cons.sys). Click to expand... Good work, but Driver Verifier must run for at least 24 hours - minimum. acole said: This computer has 2 SSD's in RAID 0. It also has a 1TB hard drive for backups and music/movies. Click to expand... Make sure that you check the SSD's manufacturer's support site for SSD firmware upgrades. For the HDD - run SeaTools for DOS, LONG test - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html acole said: I ran chkdsk on them, but I am not sure if anything was found. Click to expand... The results are in the Event Viewer Application log. acole said: I looked at your link on how to run the tests but it seems very confusing to me as I am not very skilled. I also don't have a USB or any CD ROMS. Could you help me understand how to run a test on the SSD and HDD in a simpler way? (simple steps) Click to expand... Find a computer that can burn bootable CD-R discs or USB for memtest86+ and SeaTools. I guess USB would be best considering you can't run CDs! acole said: Sorry if I sound a bit thick headed - as stated I am not the best when it comes to some of these things. I just wish the BSOD errors would just say EXACTLY what the error is, why do they make these computers so difficult to diagnose a problem? Click to expand... Don't worry about your level of expertise. BSODs are rather difficult to figure out as everything is in hex. Regards. . . jcgriff2
A acole Active member Joined Jan 20, 2016 Posts 26 Jan 28, 2016 #29 Thanks for the post and breaking it down. Sorry for making it so long, I just felt nervous because I clearly want to help my bro before he gets back but I clearly feel some of those tests are probably beyond my skill level. I will see if I can buy a USB drive, hopefully they aren't too expensive. I have never really used one and this will sound silly, but I don't really even know what it is, though I think I know what it is - but I am confusing myself. (lack of sleep talking here). Okay if you can please give me a couple of days to try and get some of the easier tests done. Can I ask why some of these tests can't be run like those other programs, like an exe file from desktop or running a program from desktop then rebooting and letting it run, like chkdsk. I am even terrified of running verifier.exe again because the last time I had trouble booting back in and I had issues with restore! On the up side, it's been a few days without a BSOD and hopefully those Windows fixes that Aura did may have fixed the issue. Also I am shocked that all the reports are in some computer code, why not make errors report in plain English or with proper codes, like Event Viewer? When I get a BSOD on this system, it just says a sentence. I remember Windows 7 had a lot more info! Anyway I will report back after I perform each test. Thanks so much for being patient with me! Joe.
Thanks for the post and breaking it down. Sorry for making it so long, I just felt nervous because I clearly want to help my bro before he gets back but I clearly feel some of those tests are probably beyond my skill level. I will see if I can buy a USB drive, hopefully they aren't too expensive. I have never really used one and this will sound silly, but I don't really even know what it is, though I think I know what it is - but I am confusing myself. (lack of sleep talking here). Okay if you can please give me a couple of days to try and get some of the easier tests done. Can I ask why some of these tests can't be run like those other programs, like an exe file from desktop or running a program from desktop then rebooting and letting it run, like chkdsk. I am even terrified of running verifier.exe again because the last time I had trouble booting back in and I had issues with restore! On the up side, it's been a few days without a BSOD and hopefully those Windows fixes that Aura did may have fixed the issue. Also I am shocked that all the reports are in some computer code, why not make errors report in plain English or with proper codes, like Event Viewer? When I get a BSOD on this system, it just says a sentence. I remember Windows 7 had a lot more info! Anyway I will report back after I perform each test. Thanks so much for being patient with me! Joe.
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore Jan 28, 2016 #30 acole said: ...I will see if I can buy a USB drive, hopefully they aren't too expensive. I have never really used one and this will sound silly, but I don't really even know what it is, though I think I know what it is - but I am confusing myself. (lack of sleep talking here). Click to expand... You're looking for a USB stick (a/k/a "flash drive") - like this - USB Flash Drives | Thumb Drive & USB Stick Drive Deals | Staples® acole said: Can I ask why some of these tests can't be run like those other programs, like an exe file from desktop or running a program from desktop then rebooting and letting it run, like chkdsk. Click to expand... SeaTools for DOS and memtest86+ are DOS based tests. Windows never loads. The tests are executed by booting with the CD or USB stick containing the bootable diagnostic program. And yes - "DOS" as in the operating system from the 1980s. I know that SeaTools is DOS-based because DOS can access every byte of an HDD; Windows cannot. Why memtest86+ is DOS-based -- no idea. acole said: On the up side, it's been a few days without a BSOD and hopefully those Windows fixes that Aura did may have fixed the issue. Click to expand... That's good - maybe Aura's help in fixing corrupted OS files fixed the BSODs too. Only time will tell. acole said: Okay if you can please give me a couple of days to try and get some of the easier tests done. Click to expand... Take your time - we'll be here. Regards. . . jcgriff2
acole said: ...I will see if I can buy a USB drive, hopefully they aren't too expensive. I have never really used one and this will sound silly, but I don't really even know what it is, though I think I know what it is - but I am confusing myself. (lack of sleep talking here). Click to expand... You're looking for a USB stick (a/k/a "flash drive") - like this - USB Flash Drives | Thumb Drive & USB Stick Drive Deals | Staples® acole said: Can I ask why some of these tests can't be run like those other programs, like an exe file from desktop or running a program from desktop then rebooting and letting it run, like chkdsk. Click to expand... SeaTools for DOS and memtest86+ are DOS based tests. Windows never loads. The tests are executed by booting with the CD or USB stick containing the bootable diagnostic program. And yes - "DOS" as in the operating system from the 1980s. I know that SeaTools is DOS-based because DOS can access every byte of an HDD; Windows cannot. Why memtest86+ is DOS-based -- no idea. acole said: On the up side, it's been a few days without a BSOD and hopefully those Windows fixes that Aura did may have fixed the issue. Click to expand... That's good - maybe Aura's help in fixing corrupted OS files fixed the BSODs too. Only time will tell. acole said: Okay if you can please give me a couple of days to try and get some of the easier tests done. Click to expand... Take your time - we'll be here. Regards. . . jcgriff2
A acole Active member Joined Jan 20, 2016 Posts 26 Feb 1, 2016 #31 Just an update. I ran driver verifier for 24 hours, actually probably closer to like 30+ hours and I did not see a single BSOD. Will there be any logs for this somewhere? I checked event viewer but I couldn't see anything. I left a DOS window open to check the status and when I got back to the machine it was still there, and no horrid BSOD screen. Thankfully I did not have to do any restore. As stated previously I had run driver verifier before and fixed 2 drivers and then proceeded to update every other driver as well. The computer hasn't had a BSOD since Aura helped fix the Windows Drives. I haven't run any other tests yet because I have been very busy with work stuff. Hopefully in the next few days I can run the SEA tools to test the hard-drives and SSD. I will probably do the RAM last seeing as I already swapped out the RAM before so I don't think the RAM is the problem, but I think it's likely a motherboard issue because lately I have noticed weird "robotic" sounding echo with sound at times and when this happens games suddenly lag down to like 10fps even on lowest settings (this pc has a gtx980 and should be getting a smooth 60fps). A reboot of the system usually fixes this problem. Unfortunately my bro has his heart set on dismantling this pc and upgrading it when he gets back later this week. He told me he is going to keep the SSD's, power supply, water coolers, DVD player and the case. So I will make it my priority to test the SSD's because they will go to the upgraded pc. Just a question, how can I test the power supply? My bro told me he had to fix the fan on it because it suddenly stopped spinning and began making weird whining sounds. The new fan works fine, but he is just worried it could be a problem with the PSU cause he thinks the BSOD happen when a lot of stuff is going on and the PSU isn't giving the appropriate power. Anyways as always, I just wanna help out - and I am glad and appreciative for the help you guys have given thus far. Thanks for putting up with my lack of computer knowledge. Joe.
Just an update. I ran driver verifier for 24 hours, actually probably closer to like 30+ hours and I did not see a single BSOD. Will there be any logs for this somewhere? I checked event viewer but I couldn't see anything. I left a DOS window open to check the status and when I got back to the machine it was still there, and no horrid BSOD screen. Thankfully I did not have to do any restore. As stated previously I had run driver verifier before and fixed 2 drivers and then proceeded to update every other driver as well. The computer hasn't had a BSOD since Aura helped fix the Windows Drives. I haven't run any other tests yet because I have been very busy with work stuff. Hopefully in the next few days I can run the SEA tools to test the hard-drives and SSD. I will probably do the RAM last seeing as I already swapped out the RAM before so I don't think the RAM is the problem, but I think it's likely a motherboard issue because lately I have noticed weird "robotic" sounding echo with sound at times and when this happens games suddenly lag down to like 10fps even on lowest settings (this pc has a gtx980 and should be getting a smooth 60fps). A reboot of the system usually fixes this problem. Unfortunately my bro has his heart set on dismantling this pc and upgrading it when he gets back later this week. He told me he is going to keep the SSD's, power supply, water coolers, DVD player and the case. So I will make it my priority to test the SSD's because they will go to the upgraded pc. Just a question, how can I test the power supply? My bro told me he had to fix the fan on it because it suddenly stopped spinning and began making weird whining sounds. The new fan works fine, but he is just worried it could be a problem with the PSU cause he thinks the BSOD happen when a lot of stuff is going on and the PSU isn't giving the appropriate power. Anyways as always, I just wanna help out - and I am glad and appreciative for the help you guys have given thus far. Thanks for putting up with my lack of computer knowledge. Joe.
A acole Active member Joined Jan 20, 2016 Posts 26 Feb 1, 2016 #32 Oh and I almost forgot, the case has a broken usb connector thing (at the front of the case). We had a game pad plugged in I think and my brother bumped it, snapping off the usb component internally. Could that cause those memory BSODs? I think he said he disconnected it so that it shouldn't cause problems, but I am not 100% sure. I looked inside the case and I can't see any cables!
Oh and I almost forgot, the case has a broken usb connector thing (at the front of the case). We had a game pad plugged in I think and my brother bumped it, snapping off the usb component internally. Could that cause those memory BSODs? I think he said he disconnected it so that it shouldn't cause problems, but I am not 100% sure. I looked inside the case and I can't see any cables!
A acole Active member Joined Jan 20, 2016 Posts 26 Feb 1, 2016 #33 I have run the test on the SSD's. Was quicker than I had expected. I have attached the log (doesn't make much sense to me) and screen shots of each SSD drive. This pc has 2 SSD's in RAID 0. I tried to attach it via this site and it wouldn't let me, so I used Mega File Upload. Link is below; Mega File Upload - SSD Test.7
I have run the test on the SSD's. Was quicker than I had expected. I have attached the log (doesn't make much sense to me) and screen shots of each SSD drive. This pc has 2 SSD's in RAID 0. I tried to attach it via this site and it wouldn't let me, so I used Mega File Upload. Link is below; Mega File Upload - SSD Test.7
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore Feb 2, 2016 #34 Hi Joe - acole said: I ran driver verifier for 24 hours, actually probably closer to like 30+ hours and I did not see a single BSOD. Will there be any logs for this somewhere? Click to expand... No, there are no logs for Driver Verifier. The fact that D/V did not BSOD your system would indicate that it did not find any driver violations, acole said: Just a question, how can I test the power supply? Click to expand... I don't know of any software test for the PSU. acole said: ...the case has a broken usb connector thing (at the front of the case). We had a game pad plugged in I think and my brother bumped it, snapping off the usb component internally. Could that cause those memory BSODs? Click to expand... The broken USB would not cause BSODs. I was unable to download your attachment. Please zip the file up (*.zip file) and attach it to your post. 7z files cannot be attached; although if no errors were reported, you passed the test. Regards. . . jcgriff2
Hi Joe - acole said: I ran driver verifier for 24 hours, actually probably closer to like 30+ hours and I did not see a single BSOD. Will there be any logs for this somewhere? Click to expand... No, there are no logs for Driver Verifier. The fact that D/V did not BSOD your system would indicate that it did not find any driver violations, acole said: Just a question, how can I test the power supply? Click to expand... I don't know of any software test for the PSU. acole said: ...the case has a broken usb connector thing (at the front of the case). We had a game pad plugged in I think and my brother bumped it, snapping off the usb component internally. Could that cause those memory BSODs? Click to expand... The broken USB would not cause BSODs. I was unable to download your attachment. Please zip the file up (*.zip file) and attach it to your post. 7z files cannot be attached; although if no errors were reported, you passed the test. Regards. . . jcgriff2
A acole Active member Joined Jan 20, 2016 Posts 26 Feb 2, 2016 #35 I ran the SSD test again and have uploaded it using winzip. Does this mean both drives are okay? (they are currently used as 1 drive in raid 0) Attachments SSD Logs.zip 157 KB · Views: 1
I ran the SSD test again and have uploaded it using winzip. Does this mean both drives are okay? (they are currently used as 1 drive in raid 0)
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore Feb 3, 2016 #36 I don't know from the attachments if the drives are healthy or not. Didn't the test say "pass" or "fail" at the end?
I don't know from the attachments if the drives are healthy or not. Didn't the test say "pass" or "fail" at the end?
A acole Active member Joined Jan 20, 2016 Posts 26 Feb 3, 2016 #37 No? It runs instantly and says what it says in the screenshots, "excellent condition". Am I running the test wrong? Or am I using the wrong program? You linked me to the HDD tests and this pc has SSD's and one big hard drive that rarely gets used. (No programs, just a backup and old music files). At the bottom of the link it says something like "follow this link for SSD's and it sent me to that utility and I downloaded it". *shrug*
No? It runs instantly and says what it says in the screenshots, "excellent condition". Am I running the test wrong? Or am I using the wrong program? You linked me to the HDD tests and this pc has SSD's and one big hard drive that rarely gets used. (No programs, just a backup and old music files). At the bottom of the link it says something like "follow this link for SSD's and it sent me to that utility and I downloaded it". *shrug*
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore Feb 3, 2016 #38 Well then - I would say the drives are healthy. Be sure to check the SSD manufacturer's support site for firmware upgrades if you haven't already done so. Regards. . . jcgriff2
Well then - I would say the drives are healthy. Be sure to check the SSD manufacturer's support site for firmware upgrades if you haven't already done so. Regards. . . jcgriff2