Window 7 x64 BSODs on newly built computer

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 7 x64
       #1

    Window 7 x64 BSODs on newly built computer


    So, I have recently built a new computer over the holidays and I am running into some issues with BSODs. I am trying to narrow down the culprit and resolve the issues. Initially, the main problem I was having was with my XFX Radeon 5770, but XFX has released updated drivers. I have updated all my drivers... that I know of, but I am still getting BSODs. I have included the most recent BSODs so someone could take a look and maybe shed some light on my issues. Any help or suggestions would be greatly appreciated.
      My Computer


  2. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #2

    jl3nz said:
    So, I have recently built a new computer over the holidays and I am running into some issues with BSODs. I am trying to narrow down the culprit and resolve the issues. Initially, the main problem I was having was with my XFX Radeon 5770, but XFX has released updated drivers. I have updated all my drivers... that I know of, but I am still getting BSODs. I have included the most recent BSODs so someone could take a look and maybe shed some light on my issues. Any help or suggestions would be greatly appreciated.

    Hello Welcome to SF,

    I guess it's pointing to a Core Windows driver Cryptography Next Generation (cng.sys)


    CNG provides a set of APIs that are used to:
    • Perform basic cryptographic operations, such as creating hashes and encrypting and decrypting data.
    • Create, store, and retrieve cryptographic keys.
    • Install and use additional cryptographic providers.
    So long story short its related to your security. More info refer this link Cryptography Next Generation

    Run the Memory Diagnostic & HD Diagnostic.

    Download Malwarebytes and run a complete scan


    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff800009ea060, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80003067b5c, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000000, (reserved)



    Hope this helps,
    Captain
      My Computer


  3. Posts : 10
    Windows 7 x64
    Thread Starter
       #3

    Thanks Capt. for the help. Last night I ran Memtest 86+ for 5 pass' without any errors. I ran the HD Diagnostics extended test as well and passed without errors. As for those tests, I didn't have any problems. I downloaded Malwarebytes and started a "complete scan" and then went to bed. (it was late by this time) The computer had a BSOD last night sometime so I started another scan this morning... same thing, but different BSOD. I will run Malwarebytes again tonight when I get home from work, but could you take a look at my newest addition to my BSOD collection and let me know what you thing? :)
      My Computer


  4. Posts : 10
    Windows 7 x64
    Thread Starter
       #4

    Anyone have an idea what to try next?
      My Computer


  5. Posts : 10
    Windows 7 x64
    Thread Starter
       #5

    Ok, so I was able to run Malwarebytes and it did find a "hacked.displayproperties" in the registry. While trying to run Malwarebytes I did receive a few BSODs and I am wondering if the ATI Catylist software is causing issues. Can someone take a look at these BSODs and let me know what they find?
      My Computer


  6. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #6

    jl3nz said:
    Ok, so I was able to run Malwarebytes and it did find a "hacked.displayproperties" in the registry. While trying to run Malwarebytes I did receive a few BSODs and I am wondering if the ATI Catylist software is causing issues. Can someone take a look at these BSODs and let me know what they find?
    Sorry for the late replay i was kinda busy lately. OK i guess its time to Run the Driver verifier follow this link Using Driver Verifier to identify issues with Drivers

    Good Luck,
    Captain
      My Computer


  7. Posts : 10
    Windows 7 x64
    Thread Starter
       #7

    Ok, I ran Driver Verifier last night to see what was up. I did receive a few BSODs. It's hard to know what is causing the BSODs, but I have a feeling it is video card related. I have attached to BSODs. Also, while verifier was "on"... my video would "freak out" and I would get the error "The ATI Display Drivers Have Stopped Working But Has Recovered..." or something like that. This happened quite a bit while verifier was turned on.

    I also tried running WEI to see if I could get something to happen. Which it did... I wouldn't give me a reading. It would error out. I also ran the SFC /scannow. There was a file that I couldn't repair, but I have no clue what to do with it. From the CBS.log file, I was able to extract the files that it repaired and couldn't repair. Let me know your thoughts... Thanks!
      My Computer


  8. Posts : 10
    Windows 7 x64
    Thread Starter
       #8

    Does anyone have any suggestions as to what I can try?
      My Computer


  9. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #9

    You've received some excellent suggestions so far, but I'll attack this from the same approach that has been used thru all computer generations.
    Nr 1 suspect: video driver,
    Nr 2 suspect: video card (sometimes these two are reversed but still tops of list)
    Nr 3 suspect: ram (incorrect type, speed, or not all from same manufacturer)
    Nr 4 suspect: defective/temperamental power supply
    Nr 5 suspect: heat (inadequate ventilation, fan not working, fan loose)
    Nr 6 suspect: mains (the power from the wall)

    Review following:
    Why is my screen black when I start Windows 7?
      My Computer


  10. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #10

    jl3nz said:
    Ok, I ran Driver Verifier last night to see what was up. I did receive a few BSODs. It's hard to know what is causing the BSODs, but I have a feeling it is video card related. I have attached to BSODs. Also, while verifier was "on"... my video would "freak out" and I would get the error "The ATI Display Drivers Have Stopped Working But Has Recovered..." or something like that. This happened quite a bit while verifier was turned on.

    I also tried running WEI to see if I could get something to happen. Which it did... I wouldn't give me a reading. It would error out. I also ran the SFC /scannow. There was a file that I couldn't repair, but I have no clue what to do with it. From the CBS.log file, I was able to extract the files that it repaired and couldn't repair. Let me know your thoughts... Thanks!
    Hello,

    Sorry for delayed replay was busy with lot of things.
    OK i ran the Dump its poiniting to your Hard Drive it happen while running Windows Shadow Copy. So Run HD Diagnostic.

    Good Luck,
    Captain
      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 18:28.
Find Us