BSOD on boot after upgrade from Windows 7

Page 1 of 2 12 LastLast

  1. verleihnixx
    Posts : 6
    Windows 10
       New #1

    BSOD on boot after upgrade from Windows 7


    After upgrading to Windows 10 Pro i get various BSOD on boot. usually i need 2-4 attempts to boot into login mask. very rarely i have a BSOD some seconds after login. power on after sleep or hibernate works well, so this problem occurs after windows updates. within windows 7 i never saw any blue screens, so i expect hardware is fine.

    the system is a desktop pc with an intel DH67BL board and an i5-2500 cpu (2nd gen), a few years old. as intel has left the mainboard business and the board is out of warranty, driver support is bad.

    can anybody help?
      My Computer
    Quote Quote

  3. axe0
    Posts : 14,903
    Windows 10 Pro
       New #2

    Hi verleihnixx,

    Welcome to the 10forums.

    As this is an upgrade, it is highly recommended to backup your files and clean install windows 10.
    With an upgrade several problems are coming to your way, with a clean install you avoid them.
      My Computers
    Quote Quote

  4. verleihnixx
    Posts : 6
    Windows 10
    Thread Starter
       New #3

    axe0 said:
    Hi verleihnixx,
    As this is an upgrade, it is highly recommended to backup your files and clean install windows 10.
    With an upgrade several problems are coming to your way, with a clean install you avoid them.
    axe0,

    yes, this can be a solution. but this system was used productive for years, so it means a lot of installing and customizing for me. so a solution, that saves two days of work, would be highly appreciated.
      My Computer
    Quote Quote

  6. axe0
    Posts : 14,903
    Windows 10 Pro
       New #4

    I have looked a little at the crash dumps and there are multiple causes.
    It would take a while, if it is possible, to solve the crashes.

    The first step, if you haven't, is backup your data.
      My Computers
    Quote Quote

  7. verleihnixx
    Posts : 6
    Windows 10
    Thread Starter
       New #5

    axe0 said:
    The first step, if you haven't, is backup your data.
    backup is available. any attempts can take place!

    best regards
    v.
      My Computer
    Quote Quote

  8. axe0
    Posts : 14,903
    Windows 10 Pro
       New #6

    Please keep in mind that hardware may fail slowly after years of use.
    Please test your memory using MemTest86+
    Please test your hard drives, you can skip SeaTools with SSD's.




    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.





    Diagnostics Test

     HDD & SSD TEST


    Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums

    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.


    Run chkdsk Disk Check - Windows 7 Help Forums


    Code:
    Probably caused by : memory_corruption
    NTFS is the file system, the hard drive.
    Code:
    STACK_TEXT:  
ffffd000`b781bce8 fffff802`75e06908 : 00000000`0000001e ffffffff`c0000005 fffff802`75cb5403 00000000`00000000 : nt!KeBugCheckEx
ffffd000`b781bcf0 fffff802`75dd7c82 : fffffa80`0304e1e0 00000000`00000000 00000000`00000000 fffff6d8`00ae29a8 : nt! ?? ::FNODOBFM::`string'+0x2ab08
ffffd000`b781c3d0 fffff802`75dd617e : 00000000`00000000 ffffd000`b781c800 fffff6d8`00ae29a8 ffffe000`4764b840 : nt!KiExceptionDispatch+0xc2
ffffd000`b781c5b0 fffff802`75cb5403 : ffff7629`3a3ae9ff fffff802`75f10660 00000000`ffffffff fffff800`9c01c601 : nt!KiGeneralProtectionFault+0xfe
ffffd000`b781c740 fffff802`760927c8 : ffffd000`00000001 00000000`0f0f6400 ffffd000`b781c860 ffffd000`b781c878 : nt!CcGetVirtualAddress+0x1e3
ffffd000`b781c7f0 fffff800`9c01bf35 : ffffe000`45b12b08 ffffe000`45b12b08 ffffe000`45a27180 00000000`092b5400 : nt!CcMapData+0x78
ffffd000`b781c860 fffff800`9c01bd4b : ffffe000`45a16102 fffff802`000000b6 00000000`00000000 00000000`00000000 : NTFS!NtfsReadMftRecord+0xe5
ffffd000`b781c970 fffff800`9c01b7c0 : ffffe000`45a16140 fffff802`00000003 ffffc001`6875b830 ffffd000`b781cbb8 : NTFS!NtfsReadFileRecord+0x9b
ffffd000`b781ca80 fffff800`9c019959 : ffffc001`6875b010 ffffe000`4764b840 ffffe000`45b12b08 00000000`00000000 : NTFS!NtfsLookupInFileRecord+0x70
ffffd000`b781cb30 fffff800`9c00bb55 : ffffe000`45b12b08 ffffe000`00000000 ffffc001`00000000 ffffc001`6875b010 : NTFS!NtfsUpdateFcbInfoFromDisk+0xe9
ffffd000`b781cca0 fffff800`9c012338 : ffffe000`45b12b08 ffffc001`6875bb40 ffffc001`68758ed0 ffffd000`b781ce18 : NTFS!NtfsOpenSubdirectory+0x1a5
ffffd000`b781cd40 fffff800`9c01182d : ffffe000`45b12b08 ffffe000`47520010 ffffd000`b7fb6100 ffffe000`47512201 : NTFS!NtfsCommonCreate+0xad8
ffffd000`b781cf50 fffff802`75dcfda7 : ffffd000`b7fb60b0 13e5b4e9`e9428063 1988d122`d6424c0e 61000933`61342416 : NTFS!NtfsCommonCreateCallout+0x1d
ffffd000`b781cf80 fffff802`75dcfd6d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
ffffd000`b7fb5ef0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
    Code:
    STACK_TEXT:  
ffffd000`205dc120 fffff801`eeae6a96 : 00000000`00000000 fffff801`eea25fc0 ffffd000`205dc900 ffffd000`205dc328 : nt!CcGetDirtyPages+0x10d
ffffd000`205dc1f0 fffff801`eeac321b : 01d1019d`3db516e6 01d1019d`00000000 ffffd000`205dc900 ffffe001`1ec27100 : NTFS!NtfsCheckpointVolume+0x56e
ffffd000`205dc750 fffff801`eeafce8b : ffffd000`205dc900 ffffe001`1ec27180 ffffd000`205dc8b0 01d1019d`3db51621 : NTFS!NtfsCheckpointAllVolumesWorker+0xbb
ffffd000`205dc7b0 fffff801`eeafc99b : ffffd000`205dc900 00000000`00000000 00000000`00000000 fffff801`eeac3160 : NTFS!NtfsForEachVcb+0x22f
ffffd000`205dc870 fffff801`9e0936a9 : fffff801`9e3f4340 ffffe001`213ec040 fffff801`eea80eb0 fffff801`9e3f4340 : NTFS!NtfsCheckpointAllVolumes+0x17b
ffffd000`205dcb70 fffff801`9e101e88 : ffffe001`1ec55280 00000000`00000080 fffff801`9e3f4340 ffffe001`213ec040 : nt!ExpWorkerThread+0xe9
ffffd000`205dcc00 fffff801`9e16e326 : ffffd001`3b5a5180 ffffe001`213ec040 ffffe001`211e75c0 fffff6fb`7dbed7f8 : nt!PspSystemThreadStartup+0x58
ffffd000`205dcc60 00000000`00000000 : ffffd000`205dd000 ffffd000`205d7000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
      My Computers
    Quote Quote

  9. verleihnixx
    Posts : 6
    Windows 10
    Thread Starter
       New #7

    axe0 said:
    Please keep in mind that hardware may fail slowly after years of use.
    Please test your memory using MemTest86+
    Please test your hard drives, you can skip SeaTools with SSD's.
    axe,

    thank you for your assistance!

    testing the harddisk gave no results but testing the memory brought up errors. see attachment. a repeated test gave errors at the same position. so i expected memory to be the cause.

    so i bought new memory but unfortunately the problem persist. with new memory on bank 0 or 1 i see the same bluescreens. any idea how to solve this? my last idea would be to replace the mainboard. any other possible reasons?

    best regards
    v.
      My Computer
    Quote Quote

  10. axe0
    Posts : 14,903
    Windows 10 Pro
       New #8

    If you have tested each stick in each slot separately from the other sticks and noted the results you know if a slot is faulty or a stick.
      My Computers
    Quote Quote

  12. verleihnixx
    Posts : 6
    Windows 10
    Thread Starter
       New #9

    axe0 said:
    Test each stick in each used slot separately from the other sticks to find out what stick/slot is causing the errors.
    This is explained in the tutorial.

    axe0,
    there isn't a problem witth the sticks. completely new memory brings up the same bluescreens at boot.
      My Computer
    Quote Quote

  13. axe0
    Posts : 14,903
    Windows 10 Pro
       New #10

    verleihnixx said:
    axe0,
    there isn't a problem witth the sticks. completely new memory brings up the same bluescreens at boot.
    Please read the post again, I edited it
      My Computers
    Quote Quote

 

  Related Discussions
I just finished the upgrade from Windows 7 SP1 Pro to Windows 10 Pro and immediately after the computer fires up, I receive the error code 0xc000007b and the blue screen. I was able to get the computer up and running again via the "remove last...
Hello, I am finally ending here after having spent quite a lot of time stripping down software, drivers, and possible causes of my issue. I have a Windows 10 Pro 1809 rig that needs an upgrade to 1909. It has successfully upgraded from...
is it possible upgrade windows from boot?
in Installation and Upgrade

I click upgrade and receive this message: 72326 Apparently it is not possible upgrade when system boot from DVD or USB but I am not sure. please tell me that is possible or certainly should run setup.exe in other to upgrade. because current...
I cannot start Windows my laptop. I can get into safe mode. I've tried to system restore and clean boot. I have tried verifier which gives the error iastor.sys Attached are the zip files. Please help. Thanks. 36303
This is on an old eMachines M6805 laptop that originally came with XP 32-bit. I put a fresh install of Windows 7 32-bit on it which ran fine. I then upgraded that to Windows 10 32-bit. The first time it booted up I was able to log in but got a...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 00:55.
Find Us




Windows 10 Forums