Windows 8 and 8.1 Forums


BSOD after upgrading to Windows 8.1

  1. #11


    Posts : 660
    windows 8.1


    The dumpfile made by Driver verifier sadly does not point directly to a third party driver.

    Did you already test your memory, because your latest dumpfile again said memory management

    You said that you upgraded from windows 7 to windows 8.1. Did you made a clean install or did you upgrade to windows 8.1.

    HP recommends that business desktop computers perform a Clean (custom) installation of Windows 8.1 to obtain the best possible Windows 8.1 experience. HP does not recommend performing an In-place update using the Microsoft Store for business desktop computers.
    And it recommends using UEfi.

    See here Most viewed solutions for HP ProDesk 600 G1 Tower PC - HP Support Center

      My System SpecsSystem Spec

  2. #12


    Posts : 17
    Windows 8.1


    Yes, I actually had ran a memtest with the help of my friend who gave me a memtest dvd, I ran it for more then two days without any errors.

    This was an upgrade but I chose custom install from within where there was an option of deleting everything before install and I chose that option, don't know it that constitutes as a clean install.

    What is UEFi? How to use it while install?

    Thanks for taking time to help me troubleshoot.

    Charotarguy
      My System SpecsSystem Spec

  3. #13


    Posts : 17
    Windows 8.1


    Seems like the system bsod once or twice per day on average, there is nothing on it, no other software except a few software to troubleshoot this issue. I downloaded whocrashed and following are the outputs based on its analysis. I am really frustrated with this, this host was my work horse and now it has become just unusable, and I have no funds to get another hardware, any help in troubleshooting this will be helpful. Thanks in advance.

    System Information (local)

    computer name: HP-Z600
    windows version: Windows 8.1 , 6.2, build: 9200
    windows dir: C:\WINDOWS
    Hardware: HP Z600 Workstation, Hewlett-Packard, 0B54h
    CPU: GenuineIntel Intel(R) Xeon(R) CPU X5650 @ 2.67GHz Intel586, level: 6
    12 logical processors, active mask: 4095
    RAM: 25752248320 total
    VM: 2147352576, free: 1912672256




    Crash Dump Analysis


    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Mon 6/23/2014 10:08:42 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062314-49421-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFF9F, 0x0, 0x1, 0xFFFFF800174C5176)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 6/23/2014 10:08:42 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x11A4FF)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFF9F, 0x0, 0x1, 0xFFFFF800174C5176)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sun 6/22/2014 7:47:11 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062214-20171-01.dmp
    This was probably caused by the following module: hal.dll (0xFFFFF80049594520)
    Bugcheck code: 0xA (0x5FFD01360, 0x2, 0x0, 0xFFFFF80049594520)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sun 6/22/2014 7:39:54 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062214-22625-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0xC4 (0x1011, 0x0, 0xFFFFCF818B01EBD0, 0xFFFFD00023226000)
    Error: DRIVER_VERIFIER_DETECTED_VIOLATION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 6/22/2014 7:31:45 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062214-24015-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0x1A (0x411, 0xFFFFF6E0009B8BA0, 0x84F0000193BBB882, 0x81)
    Error: MEMORY_MANAGEMENT
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 6/22/2014 4:15:25 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062214-22296-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0x1A (0x411, 0xFFFFF6E000253BE0, 0xC7A000016F62F882, 0x1)
    Error: MEMORY_MANAGEMENT
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 6/22/2014 4:07:51 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062214-31671-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802C3A671CC, 0xFFFFD00023FCD430, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 6/22/2014 3:16:49 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062214-48015-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0xA (0x20, 0xF, 0x0, 0xFFFFF801F10D78DF)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 6/21/2014 2:20:43 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062114-31906-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0x50 (0xFFFFF6FB40000000, 0x0, 0x0, 0x6)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 6/21/2014 3:01:48 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062014-36468-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801398BD4C5, 0xFFFFD0012D5EA9D0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




    Conclusion


    14 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


      My System SpecsSystem Spec

  4. #14


    Posts : 17
    Windows 8.1


    Attaching the latest dignostic tool report, dont know how much helpful it would be,
      My System SpecsSystem Spec

  5. #15


    Posts : 19
    Windows 8.1 64bit


    Charotarguy,

    I am new here and having BSOD issues myself, i do have several 1000s of servers though including the server series you are running.

    Intel(R) Xeon(R) CPU X5650 @ 2.67GHz (12 CPUs), ~2.7GHz

    However my servers are both DUAL and SINGLE cpu related RACK servers not workstation.

    I can tell you that over the past year we have been constantly replacing CPU or RAM due to the age of the generation it's self.

    I can point you in a direction however of what we do to diagnose CPU or RAM related issues.

    LinX, is a stress testing tool similar to PRIME95 however with LinX it's alot more versatile on how and what your testing.

    https://obsproject.com/downloads/LinX.zip

    Can you run this test? With some settings such as 24GB of ram etc...

    Normally if there is an issue with in the first 1 - 5 loops your system will fail.

    Then we can work from that point onwards to further diagnose the exact component which is causing the issue.

    Cheers!
      My System SpecsSystem Spec

  6. #16


    Posts : 17
    Windows 8.1


    Hi I ran the LinX test multiple time and it finishes without any errors.

    Charotarguy
      My System SpecsSystem Spec

  7. #17


    Posts : 660
    windows 8.1


    One dumpfiles blames to Probably caused by Netio.sys.
    This could point to a networkrelated problem.
    In the stacktext are nsiproxy and ndis (also networkrelated).

    NDIs is Driver Description: NDIS 6.20 driver

    This could point to your ethernetcard Broadcom NetXtreme Gigabit Ethernet .

    Because you have a workstation HP z600, what is your model and which driver did you install.
    On the supportpage of Broadcom i see there are drivers for desktop and for servers.

    On the supportpage of your HP z600 there are only drivers for Intel ethernet card.
    Did you switched to broadcom?

    According to Uefi.
    You can only use/switch to UEfi if you make a new clean install. See the link in my prevoius post.
      My System SpecsSystem Spec

  8. #18


    Posts : 19
    Windows 8.1 64bit


    Hey Charotarguy,

    Can you please install the following driver and see if the bluescreen happens again.

    http://ftp.hp.com/pub/softpaq/sp63501-64000/sp63627.exe

    Hopefully this should resolve your issue.

    Cheers!
      My System SpecsSystem Spec

  9. #19


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi charotarguy,

    Sorry to jump in, but could you please remove MalwareBytes using this **LINK** and make sure that it is not the main culprit?

    Furthermore, I see that there is presence of a Qualcomm Atheros Wireless Device on your workstation but according to the HP Support site, you are only provided with Broadcom Ethernet. So did you install this wireless NIC as an aftermarket part?

    I see that there is presence of both the Qualcomm and Broadcom Wireless drivers. Even though only the Qualcomm Wireless one has been assigned with a MAC Address and not the Broadcom one. Could you please make sure that your Qualcomm Wireless Drivers are updated? Use this site to see from where you could update those :-

    Driver Reference Table - athwbx.sys
      My System SpecsSystem Spec

  10. #20


    Posts : 17
    Windows 8.1


    Thanks all for taking time to help me troubleshoot,

    blueelvis

    yes I have installed an off market wireless card for network connectivity, it did not come with the workstation. The Qualcomm Atheros Wireless drivers were suggested over here and it took me to the same site that you have referenced.

    lifetec

    For windows 8 the Intel driver which are shown on the HP site I downloaded them and tried to install it but it said that it did not find any Intel Network Card, the broadcom drivers you are seeing are listed on the windows 7 side, these are present as this host was on windows 7 before and I upgraded to windows 8.1.
      My System SpecsSystem Spec

Page 2 of 3 FirstFirst 123 LastLast
BSOD after upgrading to Windows 8.1
Related Threads
Hi I have two desktop PCs and one notebook all running Windows 8.1 Pro and all showing the BSOD after I connect to the Internet. After connecting to the Internet it can take from a few seconds to a few minutes before the BSOD appears. It would report something slightly different:...
Help Please..... Lonovo ideacentre A520 all-in-one three days old, came with Windows 8. Updated to Windows 8.1 and after that get BSOD sometimes 5-10 times a day. I updated all drivers, installed all updates from Microsoft, Lonovo and ran sfc/scannow with no errors found. See attached...
I have upgraded from Windows 7 to Windows 8 about a year ago or so. When Windows 8.1 was released I upgraded again. But ever since I upgraded to W8 I sometimes get BSODs, and after to uprading to 8.1, I get BSODs several times. My computer boots, everything is going okay until I log into Windows.....
Hello all, Laptop came with Windows 8.0 and I received the upgrade to 8.1 last November. I also installed a Samsung SSD 256GB instead of the original HD and used Samsung Migration (which installed some unwanted drivers) to migrate the OS to that new drive. Since then, I get very frequent...
Solved BSOD after upgrading to Windows 8.1 from 8.0 in BSOD Crashes and Debugging
Hi all, Since I upgraded to Windows 8.1 (from 8.0) I'm experiencing BSOD a while after Windows has started (about 30 seconds). I updated all my drivers by different means to be sure all is up to date. But the problem is always here... Help should be very appreciate to help me fix this...
Hello guys, I thought I would ask here about my issues regarding BSOD's. I was running Windows 8 with no issues at all, however, after upgrading to Windows 8.1 i have had many issues. The first BSOD's I had which where related to virtual box was the "CRITICAL_STRUCTOR_CORRUPTION" which have been...
Hello, I recently upgraded to windows 8 on my gaming desktop. As such, started the blue screens. Attached are the dump logs. The blue screens happens randomly either under load or just idle.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook