Solved

BSOD on new system consistently

Hey guys, so I bought a new PC about year ago and ive had over 100 blue screens on it and gone back to using my old PC, ive tested everything but the PSU MB and CPU. Its even blue screened while installing windows before, I have also tried 2 different legit operating systems windows 7 and 8 and it still blue screened. I have tested the ram multiple times and even left it running for a day and the ram came up with no errors. Is there anyone out there that knows how to read BSOD error log files that might be able to help me find out what my problem is? My guess is that it must be the PSU or the MB but I have no means of testing them here.
PC: i5 4670K
Gigabyte GA-H87-D3H Motherboard
Antec VP650P 650W Power Supply
G-skill 16gb ram
Radeon 5850
Thanks.
22 answers Last reply Best Answer
More about bsod system consistently
  1. I know how to google a bsod code, so you can tell the internet the codes. That generally tells the reason why you got it. Are your drivers okay? They can cause a bsod.
  2. best to put up current version of the memory dump files on a server like microsoft one drive, share the files as public and post a link.

    the files are located on c:\windows\minidump directory by default.

    Bluthazar said:
    Hey guys, so I bought a new PC about year ago and ive had over 100 blue screens on it and gone back to using my old PC, ive tested everything but the PSU MB and CPU. Its even blue screened while installing windows before, I have also tried 2 different legit operating systems windows 7 and 8 and it still blue screened. I have tested the ram multiple times and even left it running for a day and the ram came up with no errors. Is there anyone out there that knows how to read BSOD error log files that might be able to help me find out what my problem is? My guess is that it must be the PSU or the MB but I have no means of testing them here.
    PC: i5 4670K
    Gigabyte GA-H87-D3H Motherboard
    Antec VP650P 650W Power Supply
    G-skill 16gb ram
    Radeon 5850
    Thanks.
  3. So it would seem from multiple things ive read and programs ive downloaded its software/driver issues and I think they are corrupting the RAM and my ram is Non-Ecc do you guys think if I bought ECC ram it could fix my issues? Its the only thing I could possibly think of to fix my problem.
  4. Ok so I downloaded another program called HWmonitor by cupid to look at my voltages and all of them apart from 1 are no where near a tolerance of 10% could this mean I have a faulty psu? or is it MB? Could my PSU be the cause of all these blue screens? Even when doing nothing with my PC switched on should the voltages be showing close to what the voltage rails should be? Thanks guys.
  5. no, drivers don't corrupt the RAM. They may corrupt the data contained in the RAM.

    Bluthazar said:
    So it would seem from multiple things ive read and programs ive downloaded its software/driver issues and I think they are corrupting the RAM and my ram is Non-Ecc do you guys think if I bought ECC ram it could fix my issues? Its the only thing I could possibly think of to fix my problem.
  6. Ok so ive taken most things out of my PC atm its just the MB RAM PSU and CPU then ran Burnintest to see if it would crash again and it has so im going to post my dump files to see if you can figure out what it is. If I have to I can do another fresh install but ive got bsod even on fresh installs, is there anything that is likely to be from crashes from a fresh win 7 install? Ive even had bsod installing windows 7.
    Here is a link to a folder with my dump files in it:
    https://drive.google.com/folderview?id=0B9vT-4AJdkAYLVBHaGQ0dHV4MjA&usp=sharing
    Thanks guys
  7. Best answer
    second bugcheck was a corruption in a table that maps the swapping between physical memory and virutal memory (pagefile.sys)

    I would be looking for a updated sata driver, cpu chipset drivers and i would run memtest to confirm the machines memory is ok. The memory address used looks like it could have been valid, maybe just a driver problem.
    update the sata/storage drivers from the motheboard vendor:
    http://www.gigabyte.com/products/product-page.aspx?pid=4491#driver
    looks like this memory dump has a different network driver installed.

    ---------
    looking at one of the bugchecks, it was a crash in a graphics driver while reading a DMA bugffer. If it is not a simple overheating problem I would be looking at updating the motherboard sound driver and reset BIOS to defaults or update it so it will reassign resources and rebuild its database it send to windows.

    http://www.gigabyte.com/products/product-page.aspx?pid=4491#dl

    note your network driver is really out of date also, 2011 you should update it.
    Atheros network adapter driver

    machine:

    System Uptime: 0 days 6:12:43.394
    H87-D3H
    Gigabyte Technology Co., Ltd.

    BIOS_VERSION: F2

    BIOS_DATE: 04/19/2013

    looks like a bios update f10 is on the website: dated 2015/08/20
    Processor Version Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz
    Processor Voltage 8ah - 1.0V
    External Clock 100MHz
    Max Speed 7000MHz
    Current Speed 3600MHz
  8. Thanks for taking a look, im going to install the drivers now and let my computer run a burnintest now to try and get it to crash again. I haven't had it blue screen in a day but it has screen frozen a couple of times. I think you were right about it overheating because i was running tests while the gpu was in and its an old radeon 5850HD. What i dont get is that thousands of people probably bought the same internals as me yet i'm one of the few to get so many BSOD from what it seems to be driver/software and its weird that its done it on fresh installs of win 7 and win 8. Ive ran ram tests multiple times and it came up with no errors, not sure how to update the atheros driver but ill try. thanks
  9. Havent had any blue screens in 3 days and had only one since taking the wireless pci card out so hopefully it was just the card, still running tests because it has gone a week before with out any bsod, if it does bsod ill upload any logs to let you see them but so far so good, thanks all for your input so far.
  10. https://drive.google.com/file/d/0B9vT-4AJdkAYVnVTWEVyVHNvNkE/view?usp=sharing
    new bsod happened this morning while my dad was watching stuff on facebook through google chrome, never seen this error before out of all of my errors could just be a once off thing? thanks
  11. I tried two other tools to read the memory dump, each failed and indicated it was corrupted.
    tried:
    http://www.osronline.com/page.cfm?name=Analyze

    and a cmd.exe utility called dumpchk.exe failed

    ------------
    when I attempt to read this memory dump the debugger says it is corrupted and stops loading it.
    It may be corrupted but I seem to be seeing this error on about 5 % of the memory dumps I look at since the debugger was updated a month ago. (ie it can be a problem with the new debbuger build) I will see if i can figure out another way to read the info.

    Bluthazar said:
    https://drive.google.com/file/d/0B9vT-4AJdkAYVnVTWEVyVHNvNkE/view?usp=sharing
    new bsod happened this morning while my dad was watching stuff on facebook through google chrome, never seen this error before out of all of my errors could just be a once off thing? thanks
  12. https://drive.google.com/folderview?id=0B9vT-4AJdkAYckNBa29sQnZWdEk&usp=sharing
    Another new bsod with the same type as my last one "special pool detected memory corruption"
    Should i be running memtest again maybe?
  13. Just FYI: it appears that all three of the new memory dumps are corrupted and I can not open them in the debugger.
  14. http://www.newegg.com/Product/Product.aspx?Item=N82E16820231441
    http://www.newegg.com/Product/Product.aspx?Item=N82E16813128603
    They are my MB and ram do you think it could be random incompatibility issues? it does say the ram is for 1155/1156 but im not sure if that would matter? Do you think buying a new MB would fix these BSODs I don't get why im getting so many when other people don't with the same setups :|
    All 3 were that new error I haven't seen before, I did change a setting on how the dump files are saved from a windows forum I was reading maybe that's why you cant read them, any other suggestions to try?
  15. try and set the memory dump type to kernel, it will provide more debug info and it will store the file as c:\windows\memory.dmp

    also, the file might be getting corrupted after the memory dump.
    you might try another cloud storage site, like mediafire or onedrive.

    generally, when I can not read a memory dump it will be due to custom filesystem drivers or bugs in a SATA controller or driver for the motherboard, OR bugs in firmware for the sata device.

    if your system has more than one drive you might change the storage location of the memory dump.
    I have also see people have old network drivers that corrupted the file as they were being uploaded.
    I have see people copy memory dumps to thumbdrives but thumb drives do not verify the copy by default.
    just really hard to say without looking.
    also, microsoft has upgraded the debugger so they may have made some type of change that flags your memory dump as invalid in my debugger.


    Bluthazar said:
    http://www.newegg.com/Product/Product.aspx?Item=N82E16820231441
    http://www.newegg.com/Product/Product.aspx?Item=N82E16813128603
    They are my MB and ram do you think it could be random incompatibility issues? it does say the ram is for 1155/1156 but im not sure if that would matter? Do you think buying a new MB would fix these BSODs I don't get why im getting so many when other people don't with the same setups :|
    All 3 were that new error I haven't seen before, I did change a setting on how the dump files are saved from a windows forum I was reading maybe that's why you cant read them, any other suggestions to try?
  16. Log Name: System
    Source: Microsoft-Windows-Kernel-Power
    Date: 22/01/2016 6:03:06 AM
    Event ID: 41
    Task Category: (63)
    Level: Critical
    Keywords: (2)
    User: SYSTEM
    Computer: Snake-PC
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Under computer management > Event viewer this is what is shown as all my critical errors, do you think that my psu could be causing the BSODs and just be playing up intermitently? i guess ill have to find another psu to use to see if i still get errors? You would think it would must be my m/b or psu playing up because ive had bsod with fresh installs of win 7 and 8 and think even ubuntu and even had bsod while trying to install windows. Atm all that is in my computer is 2 ram sticks, m/b, psu, cpu and 1 hdd. The only things that would make sense to me is m/b or psu playing up. What do you think? Thanks
  17. event 41 is logged when a machine boots up and the "dirty" bit is set.
    this just means the last shutdown never fully completed for what ever reason.
    you could turn off the power to the machine, the next boot will log a error 41,
    - the machine could bugcheck, the next boot will log the error 41.

    you want to look at entries that happen before the error 41 entry.


    Bluthazar said:
    Log Name: System
    Source: Microsoft-Windows-Kernel-Power
    Date: 22/01/2016 6:03:06 AM
    Event ID: 41
    Task Category: (63)
    Level: Critical
    Keywords: (2)
    User: SYSTEM
    Computer: Snake-PC
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Under computer management > Event viewer this is what is shown as all my critical errors, do you think that my psu could be causing the BSODs and just be playing up intermitently? i guess ill have to find another psu to use to see if i still get errors? You would think it would must be my m/b or psu playing up because ive had bsod with fresh installs of win 7 and 8 and think even ubuntu and even had bsod while trying to install windows. Atm all that is in my computer is 2 ram sticks, m/b, psu, cpu and 1 hdd. The only things that would make sense to me is m/b or psu playing up. What do you think? Thanks
  18. https://drive.google.com/folderview?id=0B9vT-4AJdkAYckNBa29sQnZWdEk&usp=sharing
    3 bsod in 1 day, what would you think is wrong if im getting bsod on 3 different OS? Driver issues on 3 different OS you would think something of my hardware is playing up? Is there anything else i can upload to here to get you to take a look at? thanks
  19. it is hard to guess without seeing the bugcheck codes, even a photo of the bugcheck can help narrow down where to look.

    Generally, I would be looking at the drive subsystem IE put the drive on a different sata port or sata controller on the same machine. Check the cables to the drive, I assume you are not using raid, anything special about the drive?
    run crystaldiskinfo.exe to read the smart data from the drive and the drive firmware version.

    also, there are some malware that infect storage drivers.

    you can try and download bluescreenview.exe or whocrashed.exe and see if either of those programs can read from your memory dump files.


    Bluthazar said:
    https://drive.google.com/folderview?id=0B9vT-4AJdkAYckNBa29sQnZWdEk&usp=sharing
    3 bsod in 1 day, what would you think is wrong if im getting bsod on 3 different OS? Driver issues on 3 different OS you would think something of my hardware is playing up? Is there anything else i can upload to here to get you to take a look at? thanks
  20. Thanks again, yeh I already have bsview and whocrashed which ive used and they don't really tell me anything unfortunately, what I have done though is updated my bios and I haven't had a crash in over a day while running tests so im hoping that is the fix, I tried installing my m/b utility program but it kept Bsoding so ive got rid of that, for now im just running tests after flashing my bios which so far so good. My plan was to keep testing it for at least a week then start adding parts again to see how it goes, re add all the ram + gpu + wireless card eventually see if its all good. I read a windows forum that said that a bios and video drivers are often culprits for bsod so I guess ill see how it goes over the next week.
  21. Video driver account for major number of the bugchecks. Mainly because they have to work pretty fast and have limited error checking that would slow them down. Not to mention that if you reduce the error checking you assume everything else is set up without conflicts or problems. (sound driver conflicts, Ethernet driver problems, and power problems) Also, they are pretty complex, almost like a limited operating system all by their self. I would not be surprised to see entire systems come out just based on a GPU and ethernet.

    Bluthazar said:
    Thanks again, yeh I already have bsview and whocrashed which ive used and they don't really tell me anything unfortunately, what I have done though is updated my bios and I haven't had a crash in over a day while running tests so im hoping that is the fix, I tried installing my m/b utility program but it kept Bsoding so ive got rid of that, for now im just running tests after flashing my bios which so far so good. My plan was to keep testing it for at least a week then start adding parts again to see how it goes, re add all the ram + gpu + wireless card eventually see if its all good. I read a windows forum that said that a bios and video drivers are often culprits for bsod so I guess ill see how it goes over the next week.
  22. So i havent had a BSOD for almost a week after updating my bios, so im about 80% sure it was an outdated bios causing my problems. Going to start adding stuff back to my computer soon to see how it goes with all my sticks of ram and my network card etc. If thats all it was causing so many problems that was so simple to fix im going to have to face palm myself. I did think of doing it sooner but ive read stories of ppl having alot of problems after flashing there bios so thats the main reason i didnt do it sooner, any way thanks for your help ppls.
Ask a new question

Read More

Blue Screen Operating Systems