BSOD in windows 7 32-bits


  1. Pixelmed
    Posts : 7
    windows 7 32-bits
       New #1

    BSOD in windows 7 32-bits [SOLVED]


    Hi,
    i have an msi MS-171F laptop and windows 7 crashes a lot first it was every ~10minutes. so i tried with a customized driver for the graphic card wich decreased the crashes but i still have the same probleme
    - the 1st attached file include the dump files.
    -the seconde include my laptop configuration and all its information and there's also a cbs log file generated with the command "SFC /SCANNOW"
    thanks for your help ....
    Last edited by Pixelmed; 20 Mar 2010 at 06:10.
      My Computer
    Quote Quote

  3. ickymay
    Posts : 1,360
    win7 ultimate / virtual box
       New #2

    Pixelmed said:
    Hi,
    i have an msi MS-171F laptop and windows 7 crashes a lot first it was every ~10minutes. so i tried with a customized driver for the graphic card wich decreased the crashes but i still have the same probleme
    - the 1st attached file include the dump files.
    -the seconde include my laptop configuration and all its information and there's also a cbs log file generated with the command "SFC /SCANNOW"
    thanks for your help ....
    your bios version
    Vendor American Megatrends Inc.
    Version A171FIMS V1.10
    Release Date 03/03/2009
    looks old and needs updating ?

    when i did a search on the MSI site it came up with your laptop as a VR705 , does that sound right according to your stickers ?

    your dmp file won't run as the symbols won't load probably because you have a .gdr patch on the NT kernel applied by microsoft ............
    [url=http://www.mydigitallife.info/2009/08/01/windows-7-rtm-updates-upgrade-os-kernel-build-version-to-7600-16399-at-win7_gdr-branch/]My Digital Life[/url] said:
    GDR is normally distributed via Windows Update and Microsoft Download Center to improve user experience, and contains software updates that address widespread critical issues, such as security vulnerabilities, and that are broadly released. The fact that Microsoft adds GDR into build string of OS kerner (ntoskrnl.exe) of Windows 7 RTM may signifies that the reliability and stability can still be improved considerably.
      My Computer
    Quote Quote

  4. Pixelmed
    Posts : 7
    windows 7 32-bits
    Thread Starter
       New #3

    yes it's from vr705 series.
    link
    for the GDR thing how do i get rid of it to upload dump files ?
    BTW I did a Memtest86 test and the result was "no errors" also another thing is that Windows XP SP2/3 crashes but without Bluescreen ..
    Ubuntu does not crash at all with all devices installed ...
    thanks
    PS:do i need to update the Bios version ?
      My Computer
    Quote Quote

  6. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #4

    Pixelmed said:
    yes it's from vr705 series.
    link
    for the GDR thing how do i get rid of it to upload dump files ?
    BTW I did a Memtest86 test and the result was "no errors" also another thing is that Windows XP SP2/3 crashes but without Bluescreen ..
    Ubuntu does not crash at all with all devices installed ...
    thanks
    PS:do i need to update the Bios version ?
    PM

    The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

    Please do the following:
    - activate/validate the Windows installation at http://www.microsoft.com/genuine
    - run sfc.exe /scannow to replace any problem files
    - open a support incident with Microsoft to see if they can fix the missing symbols issue ( http://support.microsoft.com/ph/14019 )
    - If that doesn't fix it, then wipe the hard drive and reinstall Windows
    - don't use "leaked"/torrent builds

    ken

    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\New folder (3)\031710-16224-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16399.x86fre.win7_gdr.090722-1835
Machine Name:
Kernel base = 0x82a3c000 PsLoadedModuleList = 0x82b84810
Debug session time: Wed Mar 17 03:34:38.651 2010 (GMT-4)
System Uptime: 0 days 0:07:48.726
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
    using a physical memory address that was not allocated by
    the USBport driver.
Arg2: 8a6ed0e0, Device extension pointer of the host controller
Arg3: 10de0aa5, PCI Vendor,Product id for the controller
Arg4: 96bae7d8, Pointer to Endpoint data structure

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
      My Computer
    Quote Quote

  7. Pixelmed
    Posts : 7
    windows 7 32-bits
    Thread Starter
       New #5

    ok how about now ?
      My Computer
    Quote Quote

  8. ickymay
    Posts : 1,360
    win7 ultimate / virtual box
       New #6

    Pixelmed said:
    ok how about now ?
    nope

    as ken says your NT kernels are unrecognizable and there are no symbols available from MSDN to use debugger , your best bet is open a support case with Microsoft as Ken said
      My Computer
    Quote Quote

  10. Pixelmed
    Posts : 7
    windows 7 32-bits
    Thread Starter
       New #7

    apparently it was only the old version of my bios causing the bsod now that i've updated the bios version i don't have any problemes (until now) thanks for the reply and for your help guys ...
      My Computer
    Quote Quote

 

  Related Discussions
my desktop is Dell XPS 730. it currently using Vista 32 bits. Everything runs very slow and none of games are runnable due frames dropping, skipping, and freezing even after I installed new Hard Drive. I decided upgrade to Windows 7 64 bits would help with running minecraft game without issue. ...
BSOD windows 7 64 bits
in BSOD Help and Support

hello , my laptop crash abrupt sometimes to Blue screen. I have here my notes : Probleemhandtekening: Gebeurtenisnaam van probleem: BlueScreen Versie van besturingssysteem: 6.1.7600.2.0.0.768.3 Landinstelling-id: 1043 Aanvullende informatie over dit probleem: BCCode: ...
My machine keep go in BSOD unxepextedly. i am using windows 7 ultimate 64 bits. anyone of you have any idea how to fix it? Here i attached the details dmp files and some images.
BSOD on Windows 7 64 bits
in BSOD Help and Support

Hello, Can someone please take a look at my minidump? Thanks,
BSOD Windows 7 32 bits Plz Help
in BSOD Help and Support

I just upgraded the computer from windows xp 32 bits to windows 7 32 bits.. and while playing Counter Strike: Source, Left 4 Dead or even while on firefox i get BSOD and the following error. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1 ...
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 04:13.
Find Us