1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows 7 BSOD after 1st boot, fine on second boot

Discussion in 'Windows 7' started by mike22, 2010/12/04.

  1. 2010/12/04
    mike22

    mike22 Inactive Thread Starter

    Joined:
    2010/12/04
    Messages:
    5
    Likes Received:
    0
    Hi there, 1st time poster

    I doubt this is a windows 7 issue (its probably hardware related). I was playing a game [Witcher] (sad I know) and it kept freezing on me.

    I thought the issue may have been my graphics card, so I changed my graphics card, and then started getting BSOD only after the first boot. After rebooting it seems to work for many hours, but the next day, on the first boot I always get a BSOD after about 2 - 3 minutes.

    I've since reverted back to my old graphics card and cleaned all of the fans and I still get BSOD of many types:


    IRQL_NOT_LESS_OR_EQUAL
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    BAD_POOL_HEADER (19)
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )

    IRQL_NOT_LESS_OR_EQUAL (a)
    Probably caused by : ntkrnlmp.exe ( nt!CcUnmapVacbArray+26c )

    IRQL_NOT_LESS_OR_EQUAL (a)
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.

    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.

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    PAGE_FAULT_IN_NONPAGED_AREA (50)


    Note* to confirm this wast a 'bad' driver issue, I have installed a fresh version of windows 7, reset my bios, unplugged all my other drivers and still found the BSOD

    I've tried a new graphics card, and found the BSOD (so it doesn't sound like a graphics card issue)

    I've run MdSched.exe with all three sticks of memory in (6 gig) and Windows Memory Diagnostic doesn't find any errors with the memory (So I don't think it s sounds like corrupt memory)

    I've started taking one memory stick out at a time, and testing to see if I still get a BSOD. I've taken one out so far, and still get the BSOD.. <it might take several days to know for definate for the rest> But since mdSched hasn't picked up corrupt memory, is it worth continuing to check this?

    What other checks can I do?
    [edit: hmm I dont seem to be able to add the dmp files to the post]
     
    Last edited: 2010/12/04
    mike22,
    #1
  2. 2010/12/04
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    PeteC,
    #2


  3. to hide this advert.

  4. 2010/12/04
    mike22

    mike22 Inactive Thread Starter

    Joined:
    2010/12/04
    Messages:
    5
    Likes Received:
    0
    ok, no problem (its not disk related since I've tried on a fresh version of windows 7, and this was on a different HD)

    I've been reading through the dumps, and cant find any correlating factors. I've added the probable causes to the 1st post
     
    mike22,
    #3
  5. 2010/12/04
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    A fuller explanation of the Error Codes from here ....

    0x0000000A: IRQL_NOT_LESS_OR_EQUAL(Click to consult the online MSDN article.)
    Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)

    0x00000050: PAGE_FAULT_IN_NONPAGED_AREA(Click to consult the online MSDN article.)
    Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). Use the General Troubleshooting of STOP Messages checklist above.


    0x00000019: BAD_POOL_HEADER(Click to consult the online MSDN article.)
    A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the msot common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers. (By theory, RAM problems would be suspect for memory pool issues, but I haven’t been able to confirm this as a cause.)
    I would say - Yes .....

    Although MS put out their on memory testing tools it is worth noting ....
    When you reloaded Windows did you install the chipset drivers and were they installed originally?

    BTW ....

    We encourage all members to complete their System Specifications which help us to help you :)
     
    PeteC,
    #4
  6. 2010/12/05
    mike22

    mike22 Inactive Thread Starter

    Joined:
    2010/12/04
    Messages:
    5
    Likes Received:
    0
    Yes, I installed the chipset drivers (from the CD that came with the gigabyte board) on both the new and the current Hard Drives

    I've continued to check the memory, and I've now run the carrona.org/memdiag.html memory tests:

    I've found running the test for 3 passes with each test:
    1 <2 meg card A> in slot 1 = Does not pick up any errors (3 Passes)
    1 <2 meg card B> in slot 2 = Does not pick up any errors (3 Passes)
    1 <2 meg card C> in slot 3 = Does not pick up any errors (3 Passes)

    All 3 cards A, B, C in slot 1,2,3 DOES PICK UP ERRORS (but I dont know what this tells me yet)

    What am I to deduce from this, and what information from the memory tests should I record/write down?

    The fact that the memory tested picked up errors strongly points the finger to an issue with the memory(?), but I dont understand why on testing each individaul memory card, no errors are detected
    my specs (from dxdiag)
     
    Last edited: 2010/12/05
    mike22,
    #5
  7. 2010/12/05
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    The i7 920 will run memory in triple channel which is what I guess you are doing as indeed I do - see My System.

    Is the memory installed a matched set of 3 modules.

    I have no idea if the error indicated relates to the memory modules themselves given that they are a matched set or the memory controller which is on the CPU. If the modules are not a matched set you could expect some problems.

    Equally I am not familiar with the memory tester you used so cannot comment on any report it may give.

    Have you checked on the Gigabyte site for any updates to the chipset drivers that may be relevant?
     
    PeteC,
    #6
  8. 2010/12/05
    mike22

    mike22 Inactive Thread Starter

    Joined:
    2010/12/04
    Messages:
    5
    Likes Received:
    0
    Ah, you have a i7 too ;)
    Yes, they're a matched set (Corsair DDR3, all with the same ID on them.. bought as a set 3x 2gig)

    No, but then machine has been working fine for about a year with no issues, so I highly suspect hardware (especially since this occurs on a clean install)

    What memory tests do you recomend?
     
    mike22,
    #7
  9. 2010/12/05
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    PeteC,
    #8
  10. 2010/12/05
    mike22

    mike22 Inactive Thread Starter

    Joined:
    2010/12/04
    Messages:
    5
    Likes Received:
    0
    Okay, I've already run it (as mentioned) but it seems to only allow you to do one pass. I've tried each on their own, and as a full set. MdSched.exe didnt pick up anything with one pass (the other memory test did after a few passes, but only when using all 3 memory slots)
    With this in mind, I'm not sure even if I replace all of my memory, the issue will be solved. Since I havent been able to identify one stick, and it seems that using all 3 sticks causes the issue (found with other memory tests)... so what does this point to?

    <wow this post is doing well in the serps: BSOD win7 1st boot>
     
    Last edited: 2010/12/05
    mike22,
    #9
  11. 2010/12/05
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    To be honest I have no real guidance to offer - the true cause may only be determined by hardware substitution. However ....
    From what you posted ....
    As I understand it you have only checked each module in one slot. You have not checked out the relationship between a module and the slot in which it is installed.
     
    PeteC,
    #10
  12. 2010/12/06
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    As Pete posted before: Follow these instructions to post a Dump Data Log.

    If you do not have a dump, ensure that your machine is configured to write out a dump by following the directions from microsoft
     
    Arie,
    #11

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...