BSOD on Windows Startup


  1. LucasB
    Posts : 2
    Windows 7 Ultimate x64
       New #1

    BSOD on Windows Startup


    Hello i'm running Windows 7 Ultimate x64, I acquired the hardware 2 days ago so its brand new basically. Only my video card is old (XFX Nvidia Gefore 9500 gt).

    It was running well until I started experiencing the crashes on the startup after the "Welcome" , the BSOD pop up and my system restarts and it happens over and over again, but sometimes it runs just fine.

    Asus P7P55D Deluxe
    Intel Core i5 760 2.8ghz
    2x Corsair XMS3 2gb
    Geforce 9500 GT


    Debugging Tools log:

    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
    Debug session time: Thu Dec 30 16:49:55.756 2010 (UTC - 2:00)
    System Uptime: 0 days 0:00:36.176
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 4E, {7, 9b307, 10c4b2, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+16dc6 )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc). If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
    Arg2: 000000000009b307, page frame number
    Arg3: 000000000010c4b2, current share count
    Arg4: 0000000000000000, 0
    Debugging Details:
    ------------------

    BUGCHECK_STR: 0x4E_7
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    PROCESS_NAME: avguard.exe
    CURRENT_IRQL: 2
    LAST_CONTROL_TRANSFER: from fffff80002aebf09 to fffff80002a8b740
    STACK_TEXT:
    fffff880`06c5a5f8 fffff800`02aebf09 : 00000000`0000004e 00000000`00000007 00000000`0009b307 00000000`0010c4b2 : nt!KeBugCheckEx
    fffff880`06c5a600 fffff800`02a64ce0 : 00000b9c`0000425e 00000b99`0000425e 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x16dc6
    fffff880`06c5a640 fffff800`02a624e9 : fffff6fc`40005ce0 fffffa80`063bfe90 00000000`00000b9c 00000b99`0000425e : nt!MiRemoveLockedPageChargeAndDecRef+0xe0
    fffff880`06c5a670 fffff800`02a7c02f : fffffa80`00000b9c fffff8a0`02c1b278 fffffa80`063bfe90 fa8006bb`00000005 : nt!MiCopyDataPageToImagePage+0x8b9
    fffff880`06c5a7a0 fffff800`02ab1e3d : fa8006bb`a0c80460 ffffffff`000004e0 fffff8a0`02c1b278 00000000`00000001 : nt!MiResolveMappedFileFault+0xa2f
    fffff880`06c5a910 fffff800`02aa75be : 00000000`00000001 00000000`02d3600e fffff680`000169b0 fffffa80`06970ec8 : nt!MiResolveProtoPteFault+0x48d
    fffff880`06c5a9b0 fffff800`02aa5743 : ffffffff`ffffff00 00000000`02d3600e 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1de
    fffff880`06c5aac0 fffff800`02a8982e : 00000000`00000001 00000000`10000000 fffffa80`069a5b01 fffffa80`00008000 : nt!MmAccessFault+0x343
    fffff880`06c5ac20 00000000`775855d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`010fd748 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775855d3

    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+16dc6
    fffff800`02aebf09 cc int 3
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+16dc6
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
    FAILURE_BUCKET_ID: X64_0x4E_7_nt!_??_::FNODOBFM::_string_+16dc6
    BUCKET_ID: X64_0x4E_7_nt!_??_::FNODOBFM::_string_+16dc6
    Followup: MachineOwner
      My Computer
    Quote Quote

  3. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #2

    LucasB said:
    Hello i'm running Windows 7 Ultimate x64, I acquired the hardware 2 days ago so its brand new basically. Only my video card is old (XFX Nvidia Gefore 9500 gt).

    It was running well until I started experiencing the crashes on the startup after the "Welcome" , the BSOD pop up and my system restarts and it happens over and over again, but sometimes it runs just fine.

    Asus P7P55D Deluxe
    Intel Core i5 760 2.8ghz
    2x Corsair XMS3 2gb
    Geforce 9500 GT


    Debugging Tools log:
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
Debug session time: Thu Dec 30 16:49:55.756 2010 (UTC - 2:00)
System Uptime: 0 days 0:00:36.176
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {7, 9b307, 10c4b2, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+16dc6 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 000000000009b307, page frame number
Arg3: 000000000010c4b2, current share count
Arg4: 0000000000000000, 0
Debugging Details:
------------------
 
BUGCHECK_STR: 0x4E_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: avguard.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002aebf09 to fffff80002a8b740
STACK_TEXT: 
fffff880`06c5a5f8 fffff800`02aebf09 : 00000000`0000004e 00000000`00000007 00000000`0009b307 00000000`0010c4b2 : nt!KeBugCheckEx
fffff880`06c5a600 fffff800`02a64ce0 : 00000b9c`0000425e 00000b99`0000425e 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x16dc6
fffff880`06c5a640 fffff800`02a624e9 : fffff6fc`40005ce0 fffffa80`063bfe90 00000000`00000b9c 00000b99`0000425e : nt!MiRemoveLockedPageChargeAndDecRef+0xe0
fffff880`06c5a670 fffff800`02a7c02f : fffffa80`00000b9c fffff8a0`02c1b278 fffffa80`063bfe90 fa8006bb`00000005 : nt!MiCopyDataPageToImagePage+0x8b9
fffff880`06c5a7a0 fffff800`02ab1e3d : fa8006bb`a0c80460 ffffffff`000004e0 fffff8a0`02c1b278 00000000`00000001 : nt!MiResolveMappedFileFault+0xa2f
fffff880`06c5a910 fffff800`02aa75be : 00000000`00000001 00000000`02d3600e fffff680`000169b0 fffffa80`06970ec8 : nt!MiResolveProtoPteFault+0x48d
fffff880`06c5a9b0 fffff800`02aa5743 : ffffffff`ffffff00 00000000`02d3600e 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1de
fffff880`06c5aac0 fffff800`02a8982e : 00000000`00000001 00000000`10000000 fffffa80`069a5b01 fffffa80`00008000 : nt!MmAccessFault+0x343
fffff880`06c5ac20 00000000`775855d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`010fd748 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775855d3
 
STACK_COMMAND: kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+16dc6
fffff800`02aebf09 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+16dc6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x4E_7_nt!_??_::FNODOBFM::_string_+16dc6
BUCKET_ID: X64_0x4E_7_nt!_??_::FNODOBFM::_string_+16dc6
Followup: MachineOwner


    Memory corruption caused by your avira anti virus (avipbb.sys). remove it and replace with Microsoft Security essentials

    Avira AntiVir Removal Tool - Download

    http://www.microsoft.com/security_essentials/


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\123010-24882-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
Debug session time: Thu Dec 30 13:43:16.662 2010 (GMT-5)
System Uptime: 0 days 0:00:36.082
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 118a9, 0, 11929}

Unable to load image \SystemRoot\system32\DRIVERS\avipbb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000118a9, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000011929, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b5538c to fffff80002ac5740

STACK_TEXT:  
fffff880`02e98538 fffff800`02b5538c : 00000000`0000004e 00000000`00000099 00000000`000118a9 00000000`00000000 : nt!KeBugCheckEx
fffff880`02e98540 fffff800`02a5e373 : 00000000`00000000 ffffffff`ffffffff 00000000`00000000 fffff8a0`02d05000 : nt!MiBadShareCount+0x4c
fffff880`02e98580 fffff800`02abad49 : 00000000`00000000 00000000`00000061 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4784e
fffff880`02e986e0 fffff800`02bf634f : 00000000`000a1000 fffff800`02ad8000 fffff880`00001f80 00000000`00000000 : nt!MiFreePagedPoolPages+0x129
fffff880`02e98830 fffff800`02bfa87c : 00000000`00000000 fffff880`02e98a00 fffff880`02e98970 00000000`00000001 : nt!MiFreePoolPages+0x343
fffff880`02e98940 fffff880`03f5da17 : 00000000`7a305641 fffff880`03f5cbe3 00000000`7a305641 00000000`00000001 : nt!ExFreePoolWithTag+0x7cc
fffff880`02e989f0 00000000`7a305641 : fffff880`03f5cbe3 00000000`7a305641 00000000`00000001 00000000`00000000 : avipbb+0xfa17
fffff880`02e989f8 fffff880`03f5cbe3 : 00000000`7a305641 00000000`00000001 00000000`00000000 fffff880`03f5cb40 : 0x7a305641
fffff880`02e98a00 00000000`7a305641 : 00000000`00000001 00000000`00000000 fffff880`03f5cb40 00000000`ffffffff : avipbb+0xebe3
fffff880`02e98a08 00000000`00000001 : 00000000`00000000 fffff880`03f5cb40 00000000`ffffffff ffffffff`80000748 : 0x7a305641
fffff880`02e98a10 00000000`00000000 : fffff880`03f5cb40 00000000`ffffffff ffffffff`80000748 00000000`000a0498 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02b5538c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------
      My Computer
    Quote Quote

  4. LucasB
    Posts : 2
    Windows 7 Ultimate x64
    Thread Starter
       New #3

    Tyvm!!!!!! i ll try that then i ll post the results.....


    Edit:
    Ty again, im not sure how to rep u but i ll find out
    Last edited by LucasB; 31 Dec 2010 at 02:43. Reason: Solved
      My Computer
    Quote Quote

 

  Related Discussions
First off, this is a friends computer that I'm working on so I only have the information she has given me. Essentially the computer will BSOD either during startup, or after a few minutes of using the computer. If it doesn't BSOD within a few minutes, the computer will run just fine until you turn...
Consistent BSOD during Windows startup for both normal mode and safe mode. BSOD problem started shortly after buggy installations of Microsoft Visual C++ 2005 x64, Microsoft .Net Framework 1.1, and AMD Catalyst Drivers 13.9; and turning off Microsoft .Net Framework 3.5.1. Startup Repair is...
As the title suggests, my Acer Aspire has been running startup repair for over 20 hours following a BSOD yesterday. I'm not sure if it's worth the wait so maybe you all can shed some light. Yesterday I was stressfully trying to search for something (using Chrome) and the website I was on froze;...
BSOD on windows startup
in BSOD Help and Support

My friend has a Toshiba notebook that is getting a BSOD when starting up (right as windows starts to load). It happens every time and always shuts the notebook off. I haven't been able to get Windows to load Successfully. The version of Windows is Media Center Edition 2005. I've attached a pic...
so everything was fine when my laptop started to become very slow and i used to get the BSOD very often so i decided to recover the system to the initial state . i did that and everything was fine , then i updated the windows 7 service pack 1 and finished the installation and rebooted my computer ,...
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 13:12.
Find Us