TechSpot

Frequent BSOD after new processor

  1. I upgraded my processor from a AMD Phenom II X2 550 (80 watt) to a AMD Phenom II X6 1090T (125 watt) and all of a sudden started getting BSOD.
    Zalman 500w processor
    4gb ddr2
    2 dvd drives
    1 hd
    GTX 460

    Is it the extra 45 watts that the new processor demands causing the BSOD's?.

    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.


    On Tue 10/25/2011 2:02:20 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102411-20155-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1A (0x403, 0xFFFFF6800005C090, 0xF6A0000114467867, 0xFFFFF6000005C090)
    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 which cannot be identified at this time.


    On Tue 10/25/2011 1:59:52 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102411-15896-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0xFFFFFA0005C9EA40, 0x7, 0x1, 0xFFFFF80003890BF3)
    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 which cannot be identified at this time.


    On Mon 10/24/2011 11:02:56 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102411-16489-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x34 (0x50853, 0xFFFFF88003376528, 0xFFFFF88003375D80, 0xFFFFF8000391A690)
    Error: CACHE_MANAGER
    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 problem occurred in the file system's cache manager.
    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 which cannot be identified at this time.


    On Mon 10/24/2011 10:42:30 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102411-16645-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFF89E041E9978, 0x0, 0xFFFFF88013223D78, 0x5)
    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 which cannot be identified at this time.


    On Mon 10/24/2011 3:28:17 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102411-17206-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x49CAC)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8801326BCAC, 0xFFFFF88008B401B0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 285.27
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 285.27
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.27 , NVIDIA Corporation).
    Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION




    On Mon 10/24/2011 2:10:35 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102311-20592-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFF8000BC4C9C0, 0x0, 0xFFFFF88004A2FD98, 0x2)
    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 which cannot be identified at this time.


    On Sun 10/23/2011 5:46:09 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102311-21590-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFFC1, 0xD, 0x0, 0xFFFFF80003896C8B)
    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 which cannot be identified at this time.
     
  2. cookiedude

    cookiedude TS Booster Posts: 157

    Best guess would be either an issue of compatibility between your RAM and new CPU or possibly a driver issue with the new CPU. Did you flash the latest BIOS to your motherboard before installing the new processor?
     
  3. maxamillion125

    maxamillion125 TS Rookie Topic Starter

    I installed the new cpu and it wouldn't boot so I did some research and then flashed the to the latest BIOS. So should I try different ram?
    Thanks
     
  4. cookiedude

    cookiedude TS Booster Posts: 157

    Going by the crash dumps you posted there does seem to be a number of instances were Memory is referenced. However, before you go out buying new RAM, try booting with 1 stick of RAM, if that doesn't work try the other. If you still have no joy then you may have to buy new RAM, but it could also be a faulty CPU as the Phenoms have the memory controller built in... sorry if this is a little vague, but it's difficult to diagnose without working on the machine directly!

    Have you tried googling the problem? What motherboard do you have?
     
  5. maxamillion125

    maxamillion125 TS Rookie Topic Starter

  6. maxamillion125

    maxamillion125 TS Rookie Topic Starter

    Well, I think I figured it out. When I flashed my board it set my ram to 5- 5- 5- 15. It is supposed to be 4- 4- 4- 12. I made the changes and it hasn't BSOD yet......
     
  7. cookiedude

    cookiedude TS Booster Posts: 157

    Glad to hear, hope that sorted it out for you.
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...