BSOD still after format

Page 2 of 6 FirstFirst 1234 ... LastLast

  1. Posts : 28,845
    Win 8 Release candidate 8400
       #11

    Ok leave the drivers as is and we can take another tack. Since the crash is related to memory management lets do these two test.



    Please run these two tests to verify your memory and find which driver is causing the problem.


    * If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!

    * If you have raid update its Driver.




    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - 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 "Special Pool", "Force Pending I/O Requests" and "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.

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.


      My Computer


  2. Posts : 31
    Windows 7 Ultimate x64
    Thread Starter
       #12

    I tested memtest the other day, 10 passes 0 error, some computer guy said 10 passes were enought, but ye ill go for Driver verifier :Þ
      My Computer


  3. Posts : 6
    Windows 7 Ultimate 32-bit
       #13

    Here's what I got.

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000003452, The subtype of the bugcheck.
    Arg2: 0000000000fd1000
    Arg3: fffff700010bf278
    Arg4: dbe00001b488701a

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x1a_3452

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: firefox.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff80002cf4233 to fffff80002c84c40

    STACK_TEXT:
    fffff880`09fe4e78 fffff800`02cf4233 : 00000000`0000001a 00000000`00003452 00000000`00fd1000 fffff700`010bf278 : nt!KeBugCheckEx
    fffff880`09fe4e80 fffff800`02c56596 : fffffa80`07508b30 fffffa80`00000004 fffff8a0`000050de fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x36103
    fffff880`09fe5730 fffff800`02f5ab1a : fffff8a0`0afdf060 fffff880`09fe5ae0 00000000`00000000 fffffa80`09d87b60 : nt!MmCleanProcessAddressSpace+0x96
    fffff880`09fe5780 fffff800`02f3e09d : 00000000`00000001 00000000`00000001 00000000`fffa1000 fffffa80`070a6b60 : nt!PspExitThread+0x56a
    fffff880`09fe5880 fffff800`02c783fa : 00000000`00000001 00000000`00000003 fffffa80`09287420 fffff800`02f9faa7 : nt!PsExitSpecialApc+0x1d
    fffff880`09fe58b0 fffff800`02c78740 : 00000000`00000246 fffff880`09fe5930 fffff800`02f3e010 00000000`00000001 : nt!KiDeliverApc+0x2ca
    fffff880`09fe5930 fffff800`02c83f77 : 00000000`00000000 0000007f`ffffffff fffff880`09fe5b60 00000980`00000000 : nt!KiInitiateUserApc+0x70
    fffff880`09fe5a70 00000000`738d2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`0293ec98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x738d2e09


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+36103
    fffff800`02cf4233 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36103

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

    FAILURE_BUCKET_ID: X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+36103

    BUCKET_ID: X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+36103

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000003452, The subtype of the bugcheck.
    Arg2: 0000000000fd1000
    Arg3: fffff700010bf278
    Arg4: dbe00001b488701a

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x1a_3452

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: firefox.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff80002cf4233 to fffff80002c84c40

    STACK_TEXT:
    fffff880`09fe4e78 fffff800`02cf4233 : 00000000`0000001a 00000000`00003452 00000000`00fd1000 fffff700`010bf278 : nt!KeBugCheckEx
    fffff880`09fe4e80 fffff800`02c56596 : fffffa80`07508b30 fffffa80`00000004 fffff8a0`000050de fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x36103
    fffff880`09fe5730 fffff800`02f5ab1a : fffff8a0`0afdf060 fffff880`09fe5ae0 00000000`00000000 fffffa80`09d87b60 : nt!MmCleanProcessAddressSpace+0x96
    fffff880`09fe5780 fffff800`02f3e09d : 00000000`00000001 00000000`00000001 00000000`fffa1000 fffffa80`070a6b60 : nt!PspExitThread+0x56a
    fffff880`09fe5880 fffff800`02c783fa : 00000000`00000001 00000000`00000003 fffffa80`09287420 fffff800`02f9faa7 : nt!PsExitSpecialApc+0x1d
    fffff880`09fe58b0 fffff800`02c78740 : 00000000`00000246 fffff880`09fe5930 fffff800`02f3e010 00000000`00000001 : nt!KiDeliverApc+0x2ca
    fffff880`09fe5930 fffff800`02c83f77 : 00000000`00000000 0000007f`ffffffff fffff880`09fe5b60 00000980`00000000 : nt!KiInitiateUserApc+0x70
    fffff880`09fe5a70 00000000`738d2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`0293ec98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x738d2e09


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+36103
    fffff800`02cf4233 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36103

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

    FAILURE_BUCKET_ID: X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+36103

    BUCKET_ID: X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+36103

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    firefox.exe is the process with ntkrnlpa.exe as image. I'm an amateur at Dump reading so, try a firefox reinstall. run memtest if you have to later.
      My Computer


  4. Posts : 31
    Windows 7 Ultimate x64
    Thread Starter
       #14

    I have many times reinstall firefox, not only that, i have uninstall try for chrome some days but allways bluescreen, and both chome and firefox allways crashes, like randomly, doesnt matter what im doing in firefox or chrome, like sometimes i only have facebook just open for a while, go somewhere and when i come back "firefox has stopped working blabla" so ye thats weird, and every game is getting erorr and crashes, so ye im pretty pist that not only getting bluescreen but everything seems crashing :S, just name it.
      My Computer


  5. Posts : 6,668
    Windows 7 x64
       #15

    I hate to jump in on a thread already going like this, but has anyone considered ram as a possible issue here?
    Also it wouldn't hurt to run this scan, it shouldn't take to long and the results could tell a lot here.
    SFC /SCANNOW Command - System File Checker
      My Computer


  6. Posts : 31
    Windows 7 Ultimate x64
    Thread Starter
       #16

    ah ty, ye as i said i was thinking it could be ram, but i wasnt sure, i tried memtest, 0 erros so i tought it could be something else, but ill go for this scan and Driver verifier tomorrow :) but i want to say thanks to you all for trying to help me, im really gratefull and hope we will find whats wrong :)
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #17

    Yes, thats why I asked the OP to do memtest in post 11.
      My Computer


  8. Posts : 31
    Windows 7 Ultimate x64
    Thread Starter
       #18

    Ye you did, but as i said, already did 10 passes 0 errors, i can give memtes another try if it can help :)
      My Computer


  9. Posts : 31
    Windows 7 Ultimate x64
    Thread Starter
       #19

    Also it wouldn't hurt to run this scan, it shouldn't take to long and the results could tell a lot here.
    SFC /SCANNOW Command - System File Checker
    Code:
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    
    C:\Windows\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\Windows\system32>
    Ill go for Driver verifiertomorrow,
      My Computer


  10. Posts : 31
    Windows 7 Ultimate x64
    Thread Starter
       #20

    So i did Driver verifier, and after reboot i got bsod when windows was starting up, so just to be sure i did it twice again = 3 times bsod on windows startup, after that i disabled verifier in safe mode.

    Heres the dump files.

    Attachment 199501
      My Computer


 
Page 2 of 6 FirstFirst 1234 ... 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 16:43.
Find Us