Windows Client TechCenter > Windows 7 Forums > Windows 7 Miscellaneous > Several bluescreens, right after boot or logon
Ask a questionAsk a question
 

AnswerSeveral bluescreens, right after boot or logon

  • Saturday, November 07, 2009 9:21 AMmaingear Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Since I've installed Windows 7 on my PC I've been getting several bluescreens with different messages on boot or right after logon. I've been trying to find solutions to them on the web, but I can't find solutions that seem to be related to my problem(s). Below is an excerpt from WinDbg, I can provide them in full if there might be anything more that is relevant in them, but I don't want to flood this forum unnecessarily. Is there somebody on here that might be able to point me in the right direction to finding solutions to my problem(s)?


    (1)
    BAD_POOL_CALLER (c2)
    Arguments:
    Arg1: 0000000d, type of pool violation the caller is guilty of.
    Arg2: 848053d8
    Arg3: 7246704e
    Arg4: 856de878
    BUGCHECK_STR:  0xc2_d
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    MODULE_NAME: Npfs
    IMAGE_NAME:  Npfs.SYS

    (2)
    KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 82d2d4a3, The address that the exception occurred at
    Arg3: 8cbd9bd4, Trap Frame
    Arg4: 00000000
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x8E
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe

    (3)
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Arguments:
    Arg1: 873f0df5, memory referenced.
    Arg2: 00000001, value 0 = read operation, 1 = write operation.
    Arg3: 8574ae82, If non-zero, the instruction address which referenced the bad memory address.
    Arg4: 00000000, (reserved)
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe

Answers

  • Monday, November 09, 2009 5:29 PMauggyMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    You're welcome for the help.

    Even though the memory tested OK there may still be problems with the memory or slots.

    Can you take the memory down to or close to 1 GB and see if there is any improvement?

    If BSODs continue to occur can you alternate the RAM slots?


  • Tuesday, November 10, 2009 9:52 PMmaingear Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    I have switched places on the memory sticks now, and then rebooted a couple of times with no BSOD (yet). I will keep this thread hanging around for a while, and if it seems to work long-term, I will mark this problem solved. =)

    Thank you very much for all your help! =)

All Replies

  • Saturday, November 07, 2009 1:13 PMauggyMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    If you get a bluescreen without fail after boot or login it is possible the problem may be a third party driver that loads at startup.

    Does the same bluescreen occur after boot or login if you restart the computer in Safe Mode?

  • Saturday, November 07, 2009 6:08 PMjdeatsch Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Auggy,

    My ears are wide open here as I get exactly the same thing that 'maingear' is getting.

    I do not, however, have the issues when in safemode.
  • Saturday, November 07, 2009 7:33 PMmaingear Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    If there is a third-party driver backfiring somewhere on my system, I wonder if there isn't a way to figure out which one then...? Also - since this doesn't always happen, I wonder what the drivers do differently in those cases that Windows doesn't crash. I don't believe in moody driver's except in traffic. =P

    I haven't tried booting in safe mode. The bluescreens don't happen all the time, rebooting a couple of times (=crashing with BSOD resulting in a reboot) usually gets me to my desktop and let me stay around to use my computer. =) I wonder how many times I need to reboot into safe mode to determine that it actually works in safe mode (that is, if it does work)?
  • Sunday, November 08, 2009 2:33 PMauggyMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Can you zip up the minidump files and make available via Windows Live SkyDrive or similar site?

    Did the start of the problem coincide with installing Windows 7? If so, then the problem could be an incompatible third party driver.

    Did you run the Windows 7 Upgrade Advisor prior to installing Windows 7?

  • Monday, November 09, 2009 9:23 AMmaingear Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    My latest minidumps:
    http://people.dsv.su.se/~nich-gro/minidump/minidumps.zip

    I ran the upgrade advisor, and I've disabled those two drivers that weren't compatible or recognized: "PCI Input Device" (???) and one related to my gfx card ATI Radeon X800. Everything else checks out.

    I booted to safe mode today, and after five minutes or so I got a "Bad_Pool_Header" BSOD, it should be in the dumps. The second time around now I haven't got a BSOD (yet - wait for it...).

    Thanks for helping me =)
  • Monday, November 09, 2009 9:23 AMmaingear Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    My latest minidumps:
    http://people.dsv.su.se/~nich-gro/minidump/minidumps.zip

    I ran the upgrade advisor, and I've disabled those two drivers that weren't compatible or recognized: "PCI Input Device" (???) and one related to my gfx card ATI Radeon X800. Everything else checks out.

    I booted to safe mode today, and after five minutes or so I got a "Bad_Pool_Header" BSOD, it should be in the dumps. The second time around now I haven't got a BSOD (yet - wait for it...).

    Thanks for helping me =)
  • Monday, November 09, 2009 2:22 PMauggyMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    That you got a BSOD in Safe Mode tends to indicate the problem is hardware rather than software.

    The Stop Errors you are receiving, MEMORY_MANAGEMENT, BAD_POOL_HEADER, etc. would suggest the problem may be memory.

    Have you tested the RAM with a memory tester such as Memtest86 or Windows Memory Diagnostics?


  • Monday, November 09, 2009 2:46 PMmaingear Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I've tested with the diagnostic that I can initiate from Windows, I guess that is "Windows Memory Diagnostics", it reports no problems at all. I'll have a go for memtest too just to be sure... I'll report back if something comes up or not. I don't like where this is going... neither does my wallet.
  • Monday, November 09, 2009 4:51 PMmaingear Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    After several passes without errors I think that I can conclude that my memory is still healthy... Any other ideas?

    Thanks so far =)
  • Monday, November 09, 2009 5:29 PMauggyMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    You're welcome for the help.

    Even though the memory tested OK there may still be problems with the memory or slots.

    Can you take the memory down to or close to 1 GB and see if there is any improvement?

    If BSODs continue to occur can you alternate the RAM slots?


  • Monday, November 09, 2009 6:04 PMmaingear Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Yeah, that's easy! There is only 1 GB to begin with (512 x 2). =)

    I can swap some memory around to try tomorrow. I'll report back as usual.

    Thanks again!
  • Tuesday, November 10, 2009 5:01 AMjjjjbbbb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Had the same error sometime ago after making some changes with speed.  Running 64bit and 6 gigs of memory.  I had to increase the voltage 0.02 volts. 

    A page file may also help since you amount of memory is 1 gig

    JB
  • Tuesday, November 10, 2009 7:58 AMmaingear Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I haven't made any modifications to the system between running Windows XP and Windows 7. I've also tried out Windows Vista a half a year ago with no problems. As for the page file, as far as I remember Windows handles that on its own, right?

    I'll be swapping memorysticks around today as I promised to try before, any more suggestions while I have the box open? =)
  • Tuesday, November 10, 2009 9:52 PMmaingear Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    I have switched places on the memory sticks now, and then rebooted a couple of times with no BSOD (yet). I will keep this thread hanging around for a while, and if it seems to work long-term, I will mark this problem solved. =)

    Thank you very much for all your help! =)