Windows 7 Problems

Page 1 of 2 12 LastLast

  1. Posts : 12
    Windows 7 Home
       #1

    Windows 7 Problems


    Hi, i have been having problems with my new windows 7 home . Just like many other members on here infact all sound like we have mostly the same problems.

    The problem pretty much is starting up windows7 its either :

    a:gets stuck on the windows 7 loading screen (so i just restart)
    b:the compuet just restarts it self automatically before the windows 7 loading screen comes up.

    After a few restarts it works just fine with no problems what so ever.

    I use the start up repair program which it suggests (or whatever its called) and it comes up with no problems at all. Also ocassionally (2 times) have the bsod come up at start up with some messages which i havent quite caught yet something to do with .sys file or something.

    I have tried a few guides on here for replacing missing fileswith the windows 7 disk which didnt work . I just cant stand keep on restating the compuet about 3 times for it to work fine lol


    If any one can help i would be so grateful :) Thanks
      My Computer


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

    andrew89 said:
    Hi, i have been having problems with my new windows 7 home . Just like many other members on here infact all sound like we have mostly the same problems.

    The problem pretty much is starting up windows7 its either :

    a:gets stuck on the windows 7 loading screen (so i just restart)
    b:the compuet just restarts it self automatically before the windows 7 loading screen comes up.

    After a few restarts it works just fine with no problems what so ever.

    I use the start up repair program which it suggests (or whatever its called) and it comes up with no problems at all. Also ocassionally (2 times) have the bsod come up at start up with some messages which i havent quite caught yet something to do with .sys file or something.

    I have tried a few guides on here for replacing missing fileswith the windows 7 disk which didnt work . I just cant stand keep on restating the compuet about 3 times for it to work fine lol


    If any one can help i would be so grateful :) Thanks

    Hi and welcome

    I would run a system file check to verify and repair your system files to do that
    type cmd in search>right click and run as admin>sfc /scannow

    Let us know the results as it may need to be run more than once


    Ken J+
      My Computer


  3. Posts : 12
    Windows 7 Home
    Thread Starter
       #3

    scanning now :) will report back with results.


    I have just updated my bios as someone suggested that on here in a differnt topic with simular problems. And shutdown fine loaded windows fine. So hopefully thats that. (fingers crossed) haha
      My Computer


  4. Posts : 12
    Windows 7 Home
    Thread Starter
       #4

    there were no problems with the scan at all.

    but windows 7 loading screen still stuck on first turn on of the day.
      My Computer


  5. Posts : 12
    Windows 7 Home
    Thread Starter
       #5

    just read on other topics of the minidump will attach to this and hope it helps more.
      My Computer


  6. Posts : 12
    Windows 7 Home
    Thread Starter
       #6

    Had a bit problem when booting up this morning it just kept restarting about 5 times getting no where. But finally worked. This problem came about when some updates where downloaded about a week ago.

    god its so annoying
      My Computer


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

    andrew89 said:
    just read on other topics of the minidump will attach to this and hope it helps more.



    Andrew Hi and welcome

    This DMP does provide some help. There are several things in it that will help.
    First it was probably caused by memory. The page fault is a dead giveaway. In looking through it I also found you have at least a dozen "unknown modules" loaded in memory. They have no creation date and time and that troubles me. If it were my system I would

    1-download and run memtestx86 overnight. You really do need to run it overnight to test the memory to the fullest and to see if there is a heat issue

    2-run a system file check to verify and repair your system files. to do that
    type cmd in search>right click and run as admin>sfc /scannow
    LET US KNOW THE RESULTS AS YOU WILL HAVE TO RUN IT MORE THAN ONCE

    3-run a complete anti virus sweep. those unknown modules may be a nasty

    If it were mine I would have already formatted and re-installed win 7

    if you are overclocking stop
    if you have a raid update its driver

    Hope this helps

    Ken J+




    Unknown modules
    Code:
    PSHED.dll        fffff880`00cdc000    fffff880`00cf0000    0x00014000    0x00000000                            
    CLFS.SYS        fffff880`00cf0000    fffff880`00d4e000    0x0005e000    0x00000000                            
    CI.dll        fffff880`00eb7000    fffff880`00f77000    0x000c0000    0x00000000                            
    Wdf01000.sys        fffff880`00e00000    fffff880`00ea4000    0x000a4000    0x00000000                            
    WDFLDR.SYS        fffff880`00ea4000    fffff880`00eb3000    0x0000f000    0x00000000                            
    pci.sys        fffff880`00f77000    fffff880`00faa000    0x00033000    0x00000000                            
    WMILIB.SYS        fffff880`0115c000    fffff880`01165000    0x00009000    0x00000000                            
    SCSIPORT.SYS        fffff880`01165000    fffff880`01194000    0x0002f000    0x00000000                            
    ACPI.sys        fffff880`01194000    fffff880`011eb000    0x00057000    0x00000000                            
    vdrvroot.sys        fffff880`011eb000    fffff880`011f8000    0x0000d000    0x00000000                            
    msisadrv.sys        fffff880`01000000    fffff880`0100a000    0x0000a000    0x00000000                            
    partmgr.sys        fffff880`0100a000    fffff880`0101f000    0x00015000    0x00000000                            
    volmgr.sys        fffff880`00faa000    fffff880`00fbf000    0x00015000    0x00000000                            
    volmgrx.sys        fffff880`00d4e000    fffff880`00daa000    0x0005c000    0x00000000                            
    pciide.sys        fffff880`0101f000    fffff880`01026000    0x00007000    0x00000000                            
    PCIIDEX.SYS        fffff880`00fbf000    fffff880`00fcf000    0x00010000    0x00000000                            
    mountmgr.sys        fffff880`00fcf000    fffff880`00fe9000    0x0001a000    0x00000000                            
    atapi.sys        fffff880`00fe9000    fffff880`00ff2000    0x00009000    0x00000000                            
    ataport.SYS        fffff880`00daa000    fffff880`00dd4000    0x0002a000    0x00000000                            
    amdxata.sys        fffff880`00ff2000    fffff880`00ffd000    0x0000b000    0x00000000                            
    fltmgr.sys        fffff880`00c00000    fffff880`00c4c000    0x0004c000    0x00000000                            
    fileinfo.sys        fffff880`00c4c000    fffff880`00c60000    0x00014000    0x00000000                            
    Ntfs.sys        fffff880`01204000    fffff880`013a7000    0x001a3000    0x00000000                            
    msrpc.sys        fffff880`01482000    fffff880`014e0000    0x0005e000    0x00000000                            
    ksecdd.sys        fffff880`014e0000    fffff880`014fa000    0x0001a000    0x00000000                            
    cng.sys        fffff880`014fa000    fffff880`0156d000    0x00073000    0x00000000                            
    pcw.sys        fffff880`0156d000    fffff880`0157e000    0x00011000    0x00000000                            
    Unknown_Module_fffff880`0157e000        fffff880`0157e000    fffff880`01588000    0x0000a000    0x00000000                            
    Unknown_Module_fffff880`016f4000        fffff880`016f4000    fffff880`017e6000    0x000f2000    0x00000000                            
    Unknown_Module_fffff880`01600000        fffff880`01600000    fffff880`01660000    0x00060000    0x00000000                            
    Unknown_Module_fffff880`01660000        fffff880`01660000    fffff880`0168b000    0x0002b000    0x00000000                            
    Unknown_Module_fffff880`01803000        fffff880`01803000    fffff880`01a00000    0x001fd000    0x00000000                            
    Unknown_Module_fffff880`0168b000        fffff880`0168b000    fffff880`016d5000    0x0004a000    0x00000000                            
    Unknown_Module_fffff880`01588000        fffff880`01588000    fffff880`015d4000    0x0004c000    0x00000000                            
    Unknown_Module_fffff880`016d5000        fffff880`016d5000    fffff880`016dd000    0x00008000    0x00000000                            
    Unknown_Module_fffff880`01400000        fffff880`01400000    fffff880`0143a000    0x0003a000    0x00000000                            
    Unknown_Module_fffff880`016dd000        fffff880`016dd000    fffff880`016ef000    0x00012000    0x00000000                            
    Unknown_Module_fffff880`017e6000        fffff880`017e6000    fffff880`017ef000    0x00009000    0x00000000                            
    Unknown_Module_fffff880`0143a000        fffff880`0143a000    fffff880`01474000    0x0003a000    0x00000000                            
    Unknown_Module_fffff880`015d4000        fffff880`015d4000    fffff880`015ea000    0x00016000    0x00000000                            
    Unknown_Module_fffff880`013a7000        fffff880`013a7000    fffff880`013d7000    0x00030000    0x00000000                            
    Unknown_Module_00000000`00000000        00000000`00000000    00000000`00000000    0x00000000    0x00000000                            
    ntoskrnl.exe    ntoskrnl.exe+7fa3a    fffff800`0300a000    fffff800`035e7000    0x005dd000    0x4a5bc600    7/13/2009 6:40:48 PM
    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\122209-16816-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\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 Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`03247e50
    Debug session time: Tue Dec 22 14:19:32.195 2009 (GMT-5)
    System Uptime: 0 days 0:00:15.631
    Loading Kernel Symbols
    .............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Unable to add module at 00000000`00000000
    
    Loading User Symbols
    Loading unloaded module list
    .
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffffa7f861d9fc8, 0, fffff88006145026, 7}
    
    
    Could not read faulting driver name
    Probably caused by : sptd.sys ( sptd+f8c61 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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.
    Arguments:
    Arg1: fffffa7f861d9fc8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88006145026, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000007, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b20e0
     fffffa7f861d9fc8 
    
    FAULTING_IP: 
    +5597952f040cd944
    fffff880`06145026 0000            add     byte ptr [rax],al
    
    MM_INTERNAL_CODE:  7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    IP_MODULE_UNLOADED: 
    sptd+f8c61
    fffff880`01120c61 ??              ???
    
    LAST_CONTROL_TRANSFER:  from fffff80003089a3a to fffff88001120c61
    
    STACK_TEXT:  
    fffff800`0452cc98 fffff800`03089a3a : 00000000`0027b55d fffffa80`04b21a88 00000be3`00000047 00000000`00200001 : <Unloaded_sptd.sys>+0xf8c61
    fffff800`0452cca0 fffff800`030846cc : fffff800`031f4e80 fffff800`00000002 00000000`00000002 fffff880`00000000 : nt!PoIdle+0x53a
    fffff800`0452cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    sptd+f8c61
    fffff880`01120c61 ??              ???
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  sptd+f8c61
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: sptd
    
    IMAGE_NAME:  sptd.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x50_sptd+f8c61
    
    BUCKET_ID:  X64_0x50_sptd+f8c61
    
    Followup: MachineOwner
    ---------
      My Computer


  8. Posts : 12
    Windows 7 Home
    Thread Starter
       #8

    ok thanks. ill try memtest tonight probably if not sometime in the next year days because of xmas. will let you know how it goes in next few days hopefully.

    Or i may just reinstall windows 7 as i havent got much on mh hd anyway. Would that be easier or not ??

    thanks again
    Last edited by andrew89; 24 Dec 2009 at 12:53.
      My Computer


  9. Posts : 8,870
    Windows 7 Ult, Windows 8.1 Pro,
       #9

    If Windows update caused this problem there are plenty of ways to uninstall those updates from a week ago. Either that or you can restore your system to a time before the updates.

    The one update causing the most problems for people seems to be the kb971961. You might want to try and uninstall that one.
      My Computer


  10. Posts : 12
    Windows 7 Home
    Thread Starter
       #10

    ok thanks going to reinstall it later and uninstall update when it comes up thanks alot will let you know if everything is ok
      My Computer


 
Page 1 of 2 12 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 20:49.
Find Us