Windows 8 and 8.1 Forums


Near Daily BSOD Since Hardware Upgrade

  1. #1


    Posts : 9
    Windows 8

    Near Daily BSOD Since Hardware Upgrade


    So for the longest time I was on my Bloomfield i7 920 processor and with a sale on newegg for the new Haswell i7 4770k I decided to take the plunge and upgrade.

    I reformatted my SSD and reinstalled everything, however ever since, I have been getting BSODs almost every day. Sometimes it is the KMODE_EXCEPTION_NOT_HANDLED message, but mostly it is the IRQL_NOT_LESS_OR_EQUAL message. It has happened in all circumstances, be it active gaming, active web browsing, or an idle state with just a web browser left open (meaning I left the computer on, went downstairs to water plants, and came back to a rebooted machine 15 minutes later, with power savings features disabled).

    Processor: i7 4770k
    Mobo: Asus Z87-Pro
    GFX: EVGA GTX 560 2gb
    PSU: Corsair TX750

    All the motherboard drivers are up to date, and the motherboard released a BIOS update which I installed, to still continue to see BSODs before and after the update.

    Everything worked perfectly fine before the hardware upgrade, so hopefully the dump data can shine a light on the cause. Thanks ahead of time for any help.

      My System SpecsSystem Spec

  2. #2


    Posts : 1,093
    Windows 8 Pro Windows 8.1 Preview


    Hello,

    I'm not going to be the guy that provides the ultimate soultion for you; however, your plight has raised some curiosity on my part. Anyway, I looked up your specs and I see that Intel lists the i7 920 processor as being compatible with DDR3-800/1066 memory and the new Processor: i7 4770k is compatible with DDR3-1366/1600 memory. So, given that you have not mentioned anything about a memory upgrade that was coincident with your CPU upgrade, and given that your BSODs could point to a memory management problem, how did you handle the memory requirements for the new processor. Specifically, did you just overclock the old memory? Did you buy new memory and just forgot to mention it? Did you just leave the old memory running at 800/1066? I suspect that trying to use the old memory could be causing an issue for your new processor.


    EDIT:
    I see your mobo starts support at 1333Mhz memory so I assume all of my previous assumption do not apply
    Last edited by JustATest; 18 Jul 2013 at 04:52.
      My System SpecsSystem Spec

  3. #3


    Posts : 9
    Windows 8


    The memory was the same memory, Corsair XMS DDR3-1600. I never overclocked it on my old system and both there and on this one it shows up in the BIOS as 1366. The original kit was a 3x4gb, since Bloomfield was triple channel, and so I simply only put in 2 of the sticks in the proper channel slots.
      My System SpecsSystem Spec

  4. #4


    Posts : 1,093
    Windows 8 Pro Windows 8.1 Preview


    Quote Originally Posted by Whirlwind View Post
    The memory was the same memory, Corsair XMS DDR3-1600. I never overclocked it on my old system and both there and on this one it shows up in the BIOS as 1366. The original kit was a 3x4gb, since Bloomfield was triple channel, and so I simply only put in 2 of the sticks in the proper channel slots.
    Yes, see my edit in previous post. So, you used slots DIMM_A2 and slots DIMM_B2 I assume?
      My System SpecsSystem Spec

  5. #5


    Posts : 1,093
    Windows 8 Pro Windows 8.1 Preview


    Just a few more thoughts and then I'll be on my way and make room for the experts:

    Make sure the memory you moved is securely seated. ( I worked the Crucial forums for quite a while and I can't tell you how many time that a reseating of the memory fixed a problem)
    Try running on 1 stick at a time (in slot DIMM_A2) and see if that helps. If so, repeat for all 3 sticks individually. (This will test* to see if any memory chips have been damaged by static discharge while handling) *If some work and some don't.
      My System SpecsSystem Spec

  6. #6


    Posts : 9
    Windows 8


    Yes, I used DIMM A2 and B2 as those are the slots that my mobo's manual suggested for only running 2 sticks.

    As for proper seating, having had a problem in the past also remedied (not BSODs, but i forget what) through reseating, i've always made sure in following builds/case moves/etc you always make sure that the memory is fully seated, push tot he click and then a couple extra pushes just to be sure. But that is something that will be done regardless because I borrowed a pair of 1600 sticks (only 4gb total ick) from my friend who is going out of town for the weekend, so I've stuck those in and am testing now.

    I had hoped that someone examining my dmp files could have confirmed it, but it was my primary suspicion that using pieces of a "triple channel kit" might be the cause, enen though just logically it feels like it shouldnt, since kits aren't really tuned for each other as much as just making sure proper quality is the same for all 3.

    Mixed feelings, i'm hoping that it still BSODs because that means I won't have to spend money buying new memory, but I also hope that this is the problem so that I know for sure what it is.
      My System SpecsSystem Spec

  7. #7


    Posts : 1,093
    Windows 8 Pro Windows 8.1 Preview


    Quote Originally Posted by Whirlwind View Post
    Yes, I used DIMM A2 and B2 as those are the slots that my mobo's manual suggested for only running 2 sticks.

    As for proper seating, having had a problem in the past also remedied (not BSODs, but i forget what) through reseating, i've always made sure in following builds/case moves/etc you always make sure that the memory is fully seated, push tot he click and then a couple extra pushes just to be sure. But that is something that will be done regardless because I borrowed a pair of 1600 sticks (only 4gb total ick) from my friend who is going out of town for the weekend, so I've stuck those in and am testing now.

    I had hoped that someone examining my dmp files could have confirmed it, but it was my primary suspicion that using pieces of a "triple channel kit" might be the cause, enen though just logically it feels like it shouldnt, since kits aren't really tuned for each other as much as just making sure proper quality is the same for all 3.

    Mixed feelings, i'm hoping that it still BSODs because that means I won't have to spend money buying new memory, but I also hope that this is the problem so that I know for sure what it is.
    Well, I think you took a good step towards trying to resolve your issue but you also could have tried your own RAM (one module at a time) as previously suggested. There is still a slight possibility that one of those modules is defective and the only way you'll find out is to try them one at a time. Good luck and let us know how you make out.
      My System SpecsSystem Spec

  8. #8


    Posts : 9
    Windows 8


    Quote Originally Posted by JustATest View Post

    Well, I think you took a good step towards trying to resolve your issue but you also could have tried your own RAM (one module at a time) as previously suggested. There is still a slight possibility that one of those modules is defective and the only way you'll find out is to try them one at a time. Good luck and let us know how you make out.
    This is true and was the intended plan for after I return my friend's RAM in 4-5 days.

    Since my BSOD problems are random in nature and not repeatable through actionable steps, it faster in ruling out RAM itself as the source by using this set first, since it is known to be stable in my friend's machine and as said is intended as a dual channel set instead of my own pieces. Thus if this proves to not BSOD in the 4-5 days i'll have it, that means I can "safely" assume that 1 or more of my sticks is bad (or they're just not liking the dual channel) and run individual chip tests and/or just buy new sticks, thus saving the time determining the problem that I would otherwise spend wondering and waiting still while running 1 stick at a time waiting for another BSOD (naturally testing each of the 3).

    On top of that, it could simply be (like my assumptions) that because it was originally a 3 piece kit, perhaps it is them memory wanting to hand the next assignment off onto a stick not present, thus faulting in channel modes but not in solo. That statement isn't backed by actual knowledge of how memory works, merely a conjecture based on the possible ways/reasons for a kit to be different from solo sticks.
      My System SpecsSystem Spec

  9. #9


    Posts : 1,093
    Windows 8 Pro Windows 8.1 Preview


    I understand you logic and can't disagree with you plan based on the time (you think) it would take to determine if an individual module is defective. However, any of your three sticks should work perfectly in pairs. The only physical aspect that makes them more compatible in a tri-arrangement is the fact they came from the same manufacturing batch number and all three modules should have the same manufacturing date. These are sold and identified with these specifics because operational characteristics can change (very minimally) from manufacturing batch to batch so this would be your best chance for identical triplets; however, take one away, and you'll end up with identical twins, and your PC should never know that one has been orphaned. Good luck and let us know.
      My System SpecsSystem Spec

  10. #10


    Posts : 9
    Windows 8


    That's exactly what I always thought, and why I didn't want to comment on it in my initial post since I didn't know if it was actually that way or not, and wanted my dmp files to get looked through without the "oh look he's broken up a channel kit, thats the problem case solved" response.
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
Near Daily BSOD Since Hardware Upgrade
Related Threads
BSOD daily, System_Service_Exception in BSOD Crashes and Debugging
Hey All, thankyou for your time to look at this. I've been getting blue screens of death infrequently, attached to my PC randomly losing power and hard freezes. I used to ignore it (used to get it rarely in BF4 a while ago, and often in Star-Citizen), but with things like LoL or Diablo 3, it...
Daily BSOD While i'm playing Games in BSOD Crashes and Debugging
This is happening for like 5 months or more. I think that i've done every possible thing i could do. Here is the requirement file you want. Hope i ll fix that issue soon. BSOD Message: 0xa000001 thanks in advance
I found this article while browsing another forum. Very interesting and a very good read on the upgrade to 8.1 with hardware that's not that old. In particular the compatibility with CMPXCHG16b with CPU/s and MOBO's. New Windows 8.1 requirements strand some users on Windows 8 | PCWorld
More than one BSOD daily. in BSOD Crashes and Debugging
I keep having a few BSOD daily, I can't pin point what it is. My recent one was PAGE_FAULT_IN_NONPAGED_AREA. Here is the SF Diag: http://db.tt/6dbdS7jg EDIT: If you don't trust dropbox, I added a attachment! Any help would be appreciated. Thanks!
Daily Windows 8 BSOD's in BSOD Crashes and Debugging
Hey, I've all of a sudden been having random BSOD's starting from the 22nd of Feb. I don't remember changing much so i'm not sure what's causing them :confused: I almost always get one (or 2) when a first boot my computer, usually after a couple minutes it settles down and is good for the rest...
Daily BSOD in BSOD Crashes and Debugging
Hello, This never used to happen, but I've been getting frequent blue screens lately, at least daily. I don't know for sure, but it always seems to happen when I have MS Word 2007 open. It also seems random. Word and other progreams are running fine; the BSOD don't seem to be triggered by a...
Hardware Upgrade in Drivers & Hardware
Hey all, So basically i have just ordered a new CPU/Mobo combo, so i will be moving from my Q6600 Core2/P5G41T-M LX3 to the new i5 3570k/P8Z77-v LX. I hope this is a good setup to get, considering my GPU seems to be slightly bottlenecked and the CPU is only a few years old now. Anyway,...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook