TechSpot

Frequent BSOD on new PC

By Red_Sparowe
Mar 6, 2013
Post New Reply
  1. Hey,

    I'm looking for some help.
    I just got a new pc. Since day 1 I get BSOD on frequent times. Mostly while I'm just on the web or just doing not much. I haven't had any BSODs while gaming.
    I did harddrive check: OK
    Reinstalled videocard drivers: still BSOD
    Diagnosed memory problems uses windows tool: ok

    Specs:
    Windows 8
    CPU: i5 3570K
    GPU: Gigabyte Nvidea GeForce 670 OC
    MB: Gigabyte GA-Z77-D3H
    SSD: Corsair 180gb
    PSU: Corsair HX650


    I analysed the minidumps using WhoCrashed:

    On Wed 6/03/2013 20:29:29 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\030613-5484-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
    Bugcheck code: 0x1A (0x3452, 0x674A9000, 0xFFFFF700010832C0, 0x5B2000019294101E)
    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.


    The errors I get on the BSODs change but the file path in the minidump seems to be mostly the same.Other errors:
    Error: DPC_WATCHDOG_VIOLATIONError: KERNEL_SECURITY_CHECK_FAILURE
    Error: IRQL_NOT_LESS_OR_EQUALError: STATUS_SYSTEM_PROCESS_TERMINATEDError: SYSTEM_SERVICE_EXCEPTIONError: DRIVER_OVERRAN_STACK_BUFFER

    On Thu 28/02/2013 22:00:01 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022813-5625-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0x28D3E0)
    Bugcheck code: 0x19 (0x3, 0xFFFFF9010070F280, 0xFFFFF960002C73E0, 0xFFFFF9010070F280)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\win32k.sys
    product: Besturingssysteem Microsoft® Windows®
    company: Microsoft Corporation
    description: Multi-User Win32-stuurprogramma
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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.


    This one occured once.

    Any help would be very welcome.
     
  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Have you applied all the Windows 8 updates, including any optional updates?
     
  3. Red_Sparowe

    Red_Sparowe TS Rookie Topic Starter

    Yes, everything is up to date
     
  4. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Are there any yellow exclamation points in the device manager?
     
  5. Red_Sparowe

    Red_Sparowe TS Rookie Topic Starter

    My apologies for the late reply but havent had much time lately.

    I have no exclamation points in the device manager, all devices work correctly.

    I have noticed that the crashes occur mostly within a couple of minutes after booting the system. When Windiws rebooted after a BDOD I can use the pc without any problems (this is in most cases).

    This weekend I got another error while opening firefox:
    WerFault.exe
    de instructie op 0xdb6438a8 verwijst naar geheugen op 0x13bdc3bc.
    Een lees- of schrijfbewerking op het geheugen is mislukt: written.

    Will try to translate :)
    the instruction on 0x... refers to memory on 0x13.....
    A read- or writeprocess on the memory failed: written.

    I also had some more BSODs, all refering to that same file path:
    file path: C:\Windows\system32\ntoskrnl.exe
    I still havent got a clue what could be wrong or even where to start searching.
     
  6. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    This still looks like a hard drive issue... Is the SSD on a SATA 3 port and is the bios set for AHCI or RAID and not IDE?
     
  7. Red_Sparowe

    Red_Sparowe TS Rookie Topic Starter

    How do I know wheter it is on a sata 3 port?
    I will check bios settings.
     
  8. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Try disabling C3/C6 State Support and the CPU Thermal Monitor under Advanced Frequency Settings and Advanced CPU Core Features in the bios
     

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...