BSOD maybe due to new components?

Page 1 of 2 12 LastLast

  1. Posts : 12
    Windows 7 Home Premimum 64 bit
       #1

    BSOD maybe due to new components?


    Hi, i recently had a new graphics card, processor and power supply fitted to my pc. The pc itself was only 2 months old. After 2 days of using it, i got a BSOD whilst gaming. It happened again about 2 hours later. I believe all my drivers are up to date, i tried to run windows memory diagnostic tool but it just kept freezing my pc. Im not very clued up with all this and need help big time.

    Windows 7 Home Premium 64bit OEM
    Processor is AMD Athlon II x4 630
    Graphics card is Novatech ATI Radeon HD
    Now the power supply i originally bought was a Corsair 430w, but it was faulty. The shop i had all this work done at ordered in a 480w supply which is in there now, but i believe to be a much cheaper one. Note they did all the work, did not do it myself.

    Any help would be much appreciated

    Matt
    Last edited by GrolUk; 25 Nov 2010 at 09:07.
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    i tried to run windows memory diagnostic tool but it just kept freezing my pc
    Your RAM may be damaged, run RAM - Test with Memtest86+
      My Computer


  3. Posts : 12
    Windows 7 Home Premimum 64 bit
    Thread Starter
       #3

    Ok i see this may take a while and so il run it overnight as suggested.
      My Computer


  4. Posts : 12
    Windows 7 Home Premimum 64 bit
    Thread Starter
       #4

    Ok i ran that, was on for a few hours didnt find any errors
      My Computer


  5. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #5

    How many passes? It needs to run for at least 7 passes. Run it from a cold boot after your computer has been off for a while.
      My Computer


  6. Posts : 12
    Windows 7 Home Premimum 64 bit
    Thread Starter
       #6

    Yeh it ran for more than 7 and found nothing. Now i have taken the side off, all cables that are plugged in are in fine. Im not very clued up with whats what when i open the damn thing up but iv checked a few sites and everything seems in order. I have just installed a package for graphics drivers. Il try run a game at full settings again to see if the probelm persists. Iv turned off auto reboot after bluescreen too so il catch the error code this time :)
    Last edited by GrolUk; 26 Nov 2010 at 07:04.
      My Computer


  7. Posts : 12
    Windows 7 Home Premimum 64 bit
    Thread Starter
       #7

    Right, this time instead of blue screening me my pc just rebooted itself out of nowhere. Any ideas?
      My Computer


  8. Posts : 12
    Windows 7 Home Premimum 64 bit
    Thread Starter
       #8

    Anyone?

    EDIT: I can upload another dump file and health report if needed
    Last edited by GrolUk; 27 Nov 2010 at 06:19.
      My Computer


  9. Posts : 12
    Windows 7 Home Premimum 64 bit
    Thread Starter
       #9

    I have just run the bluescreen viewer, and two things are shoing in red. The first is ATIKMDAG.SYS, which i see is something to with ATI drivers. However i recently isntalled the newest version possible. The second showing in red is something called NTOSKRNL.EXE, i have no idea what this is.

    So can anyone lend a hand please :)

    PS: The time string dates dont match though, unless thats just me being a total nub
      My Computer


  10. Posts : 11,840
    64-bit Windows 8.1 Pro
       #10

    Use DriverSweeper to completely uninstall your video drivers ... then reinstall the latest version available ... if this doesn't resolve your problem, then run driver verifier ...


    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    upload any new .dmp files that driver verifier creates...
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:51.
Find Us