Windows 10: Random crashes since computer was first built Solved

Page 1 of 2 12 LastLast
  1.    29 Nov 2015 #1

    Random crashes since computer was first built


    System:
    CPU: FX 9590
    MB: m5a99fx pro r2.0
    GPU: sapphire trix 290x
    ram: 16gb
    Powersupply: 1000w

    So before this setup, I had a fatal1ty fx 990 that would cause random blue screens, I RMA'd my CPU, my motherboard two times, and replaced my ram, ram slots, harddrive, and video cards with a lower end one, but it would still randomly blue screen with a error and sometimes to the hard drive controller or something (I forgot exactly)
    I attempted to install drivers with the CD, updated drivers from online, etc.
    So I decided to replace my MB and got the one I have right now (m5a99fx pro r2.0) And like magic I dont have any more blue screens, instead the computer just locks up, no response and I have to hard reset it with the button... I tried reinstalling windows on a whole new hard drive with only having the same exact issues.
    And I checked the registry with it showing me no major errors except that there was a unexpected shutdown

    So I decided I am just too bad with computers and decided to give tech support a visit the first time in my life (UbreakitIfixit) with 1 week later them telling my my MB is the issue, then another week them saying they dont know what the issue after they attempted to replace my MB and for me to pick it up with no charge.

    I am planning to go to another place but before I do I want to try with someone on the forums. I am desperate, I really need to get my pc back so I can start school work again (Its a pain on this laptop...)



    (EDIT)
    SOLUTION:
    Heating issues. Upgraded to a water cooler and had no issues ever since
    Last edited by rowow; 14 Feb 2016 at 12:37.
      My ComputerSystem Spec

  2.    29 Nov 2015 #2

    I also forgot to add that I also attempted to update the bios with that also not helping...
      My ComputerSystem Spec


  3. Posts : 11,522
    Windows 10 Pro
       30 Nov 2015 #3
      My ComputersSystem Spec

  4.    30 Nov 2015 #4

    Please read my post, ive explained that this is a system lockup that does not show any crash in winregistry, so in short, it is NOT a blue screen and does not show any crash reports
      My ComputerSystem Spec

  5.    01 Dec 2015 #5

    So I decided to give the DMcollector a try and it turns out there are two mini dumps that where made, weird as I have not been able to find them.
    1: When I ran the program the first time withing a few seconds the computer went into a blue screen...
    2: Ive tried again and it managed to get about 85% on the refreshing system information loading thing and it locked up
    3: tried again and it was on the refreshing system information loading thing for about 30% and said cd rom and blue screened
    4: tried again and it went through and made a successful file

    Ive added a number to the begging of each file it made on the desktop corresponding to each situation explained above.
      My ComputerSystem Spec


  6. Posts : 11,522
    Windows 10 Pro
       01 Dec 2015 #6

    Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
    A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
    For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
    I recommend to install a genuine copy of Windows.
    If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.
    Code:
      <ActivePartialProductKey>T83GX</ActivePartialProductKey>  <ActiveProductKeyPid2>00331-10000-00001-AA200</ActiveProductKeyPid2>
      <OSVersion>10.0.10240.2.00010100.0.0.048</OSVersion>
      <ProductName>Windows 10 Pro</ProductName>
      <ProcessorArchitecture>x64</ProcessorArchitecture>
      <EditionId>Professional</EditionId>
      <BuildLab>10240.th1.150930-1750</BuildLab>
      <TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone>
      <ActiveSkuId>2de67392-b7a7-462a-b1ca-108dd189f588</ActiveSkuId>
      <ActiveSkuDescription>Windows(R) Operating System, VOLUME_KMSCLIENT channel</ActiveSkuDescription>
      <ProductUniquenessGroups>55c92734-d682-4d71-983e-d6ec3f16059f</ProductUniquenessGroups>
      <ActiveProductKeyPKeyId>08e404fb-41f3-77ac-59ef-6e9f2d3f499d</ActiveProductKeyPKeyId>
      <ActiveProductKeyPidEx>03612-03311-000-000001-03-1033-10240.0000-2642015</ActiveProductKeyPidEx>
      <ActiveProductKeyChannel>Volume:GVLK</ActiveProductKeyChannel>
      <ActiveVolumeCustomerPid>55041-00168-381-204556-03-1033-7601.0000-2142015</ActiveVolumeCustomerPid>
      <OfflineInstallationId>318582010731661336001829671088516316938333279228570853536002246</OfflineInstallationId>
      <DomainJoined>false</DomainJoined>
    Forum rules
    4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).
      My ComputersSystem Spec

  7.    01 Dec 2015 #7

    axe0 said: View Post
    Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
    A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
    For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
    I recommend to install a genuine copy of Windows.
    If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.
    Code:
      <ActivePartialProductKey>T83GX</ActivePartialProductKey>  <ActiveProductKeyPid2>00331-10000-00001-AA200</ActiveProductKeyPid2>
      <OSVersion>10.0.10240.2.00010100.0.0.048</OSVersion>
      <ProductName>Windows 10 Pro</ProductName>
      <ProcessorArchitecture>x64</ProcessorArchitecture>
      <EditionId>Professional</EditionId>
      <BuildLab>10240.th1.150930-1750</BuildLab>
      <TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone>
      <ActiveSkuId>2de67392-b7a7-462a-b1ca-108dd189f588</ActiveSkuId>
      <ActiveSkuDescription>Windows(R) Operating System, VOLUME_KMSCLIENT channel</ActiveSkuDescription>
      <ProductUniquenessGroups>55c92734-d682-4d71-983e-d6ec3f16059f</ProductUniquenessGroups>
      <ActiveProductKeyPKeyId>08e404fb-41f3-77ac-59ef-6e9f2d3f499d</ActiveProductKeyPKeyId>
      <ActiveProductKeyPidEx>03612-03311-000-000001-03-1033-10240.0000-2642015</ActiveProductKeyPidEx>
      <ActiveProductKeyChannel>Volume:GVLK</ActiveProductKeyChannel>
      <ActiveVolumeCustomerPid>55041-00168-381-204556-03-1033-7601.0000-2142015</ActiveVolumeCustomerPid>
      <OfflineInstallationId>318582010731661336001829671088516316938333279228570853536002246</OfflineInstallationId>
      <DomainJoined>false</DomainJoined>
    Forum rules
    Ive purchased a windows license and should arrive in a few hours, if not then hopefully tomorrow.
    But ive used this same iso on my laptop which had windows 8 and a whole bunch of bloatware and on my 3d printer's computer, both I am not willing to pay for a whole new windows for as the printing computer I never use (and I know you can upgrade for free but the issue is the bloatware comes along with the upgrade)
    But like I said, once I get the "legal" version of windows ill post back immediately, and I really hope this solves my issue, because I tried EVERYTHING
      My ComputerSystem Spec

  8.    01 Dec 2015 #8

    axe0 said: View Post
    Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
    A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
    For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
    I recommend to install a genuine copy of Windows.
    If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.
    Code:
      <ActivePartialProductKey>T83GX</ActivePartialProductKey>  <ActiveProductKeyPid2>00331-10000-00001-AA200</ActiveProductKeyPid2>
      <OSVersion>10.0.10240.2.00010100.0.0.048</OSVersion>
      <ProductName>Windows 10 Pro</ProductName>
      <ProcessorArchitecture>x64</ProcessorArchitecture>
      <EditionId>Professional</EditionId>
      <BuildLab>10240.th1.150930-1750</BuildLab>
      <TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone>
      <ActiveSkuId>2de67392-b7a7-462a-b1ca-108dd189f588</ActiveSkuId>
      <ActiveSkuDescription>Windows(R) Operating System, VOLUME_KMSCLIENT channel</ActiveSkuDescription>
      <ProductUniquenessGroups>55c92734-d682-4d71-983e-d6ec3f16059f</ProductUniquenessGroups>
      <ActiveProductKeyPKeyId>08e404fb-41f3-77ac-59ef-6e9f2d3f499d</ActiveProductKeyPKeyId>
      <ActiveProductKeyPidEx>03612-03311-000-000001-03-1033-10240.0000-2642015</ActiveProductKeyPidEx>
      <ActiveProductKeyChannel>Volume:GVLK</ActiveProductKeyChannel>
      <ActiveVolumeCustomerPid>55041-00168-381-204556-03-1033-7601.0000-2142015</ActiveVolumeCustomerPid>
      <OfflineInstallationId>318582010731661336001829671088516316938333279228570853536002246</OfflineInstallationId>
      <DomainJoined>false</DomainJoined>
    Forum rules
    So I reinstalled with a usb creator directly from microsoft and activated with a valid key,
    First time it locked up
    Second time it blue screened
    Third time it locked up
    Fourth time it locked up on startup
    Fifth time it locked up
    And finally I was able to start and finish the collecting tool
    Here are the minidumps
      My ComputerSystem Spec

  9.    02 Dec 2015 #9

    Just got another blue screen two times, WHEA_UNCORRECTABLE_ERROR
    But I waited for 5 mins and it was stuck at 0%, so I force restarted and it did not create a mini dump.

    Did a stress test with prime95 while viewing with AMD SYSTEM MONITOR and CPUID HWMonitor
    Temperatures where fine but then core#4 dropped to 30% and immediately locked up

    After that I hard reset the computer and it was stuck on the asus logo, after a few mins the computer shut down and the cpu cooler was hot, defiantly over 70c

    Ill try to run another test once the computer cools down, but this is weird, maybe the cpu is bad?
      My ComputerSystem Spec

  10.    02 Dec 2015 #10

    So it was difficult to boot back up, many times it would boot to a black screen and reset after a min, or boot to the asus logo and get stuck again, but eventually I got it booted on and did a stress test
    Temperatures went to 65C and locked up, no cores dropped like last time
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
I have a new PC that I built and i'll include the parts at the end. I'm running Windows 10 Pro Insider Preview. Eval copy. Build 10565. This machine randomly freezes on me(No BSOD) and I haven't been able to figure out the cause. It does not matter...
Solved Random BSOD crashes in BSOD Crashes and Debugging
BSOD seem completely random.
Random BSOD crashes. in BSOD Crashes and Debugging
I am running Windows 10 on a desktop computer about a year old. Custom built by Hard Drives Northwest. Dual boots Windows 10 and 8.1. Windows 10 is the default, which replaced Windows 7 that dual booted with Windows 8.1. Windows 10 seemed to run...
So I've just built a PC and within a day it has had BSOD a couple of times. The event viewer says event 41, kernel-power, category 63 When I did build my computer the RAM was an issue, and was fixed after moving it to a different slot. It's DDR4...
Hello, Can I install Preview version 10130 on a brand new computer I'm building myself, without any Win7 or 8 or 8.1 disk/license? If yes, will I have any license/activation problem when I replace the Preview with the purchased release Pro...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:07.
Find Us