0x4F, 0x7A - ntoskrnl BSOD

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Morten Kristensen, Nov 5, 2013.

  1. Morten Kristensen

    Joined:
    Nov 5, 2013
    Messages:
    2
    Likes Received:
    0
    Hi there - "WindowsForum".
    I've had an issue with my computer for LOOOONG time, first it all started out giving me "0x4f" errors, but the whole 0x4f ended when I changed my keyboard, and it stopped happening the BSOD but then suddenly 6 days after. I recieved the 0x7A, and now its called ntoskrnl.exe.

    This have happend every day and around 1-2 times a day.

    What I've done:

    * I've ran memtest = no errors
    * HDD checked the disk = No errors
    * Checked drivers
    * Reinstalled windows 7 - and new drivers from motherboard disk.
    * AND I've had it in my local store 3 times to check for hardware mistakes. And they found none.

    Ill uploads some errors from BluescreenView if that is needed, hope you can help me :(
     
  2. BIGBEARJEDI

    BIGBEARJEDI Honorable Member
    Premium Supporter

    Joined:
    Jan 28, 2013
    Messages:
    1,785
    Likes Received:
    214
    Hi Morten:
    Just read your post. sorry you are having difficulties. It would be helpful if we could get a Crash Dump or Mini Dump which is a log file generated by Windows when it goes to the Blue Screen (BSOD). Post back here and the guys who do dump analysis can review and see what could be causing it.

    It would also be helpful to us if we could get full specs on your computer. Is it a Desktop or Laptop? Brand/Model?
    And component specs. If it's a Custom-built desktop; you will probably have those memorized or handy somewhere in the notes you kept when you built your rig. If it's an OEM or name brand computer such as Dell, HP, Acer, Toshiba, etc. we need that info as well. If it's a name brand computer; also and you don't know the specs, or you bought it used or inherited it with no information; google the SPECCY program, download and run and post the results here for us to look over.

    You still haven't provided us nearly enough information about your computer for us to figure anything out. Those error codes you mentioned are very general and they could be happening from hardware or software or a combination of both.

    While you are working on getting us that? Do you have factory RECOVERY DISCS that came with your computer? If you built it yourself, do you have the original Microsoft Windows7 disc you used to install your Windows? You'll need to look for those. In the meantime, I strongly urge you to do a complete DATA BACKUP OF ALL YOUR CRITICAL DATA ON THAT HARD DRIVE TO AN EXTERNAL HARD DRIVE, FLASH DRIVE, OR CD/DVD DISCS BEFORE YOU GO ANY FURTHER TRYING TO REMEDY THE PROBLEM!!!

    BSODs are very tricky, and if their source is a failing hardware component such as a hard drive, and you continue to mess with it without backing your stuff up, you are just asking for trouble!

    We'll look forward to your Post back and try to assist you further.

    BIGBEARJEDI
     
  3. Morten Kristensen

    Joined:
    Nov 5, 2013
    Messages:
    2
    Likes Received:
    0
    Hi there thank you so much for your fast responce!
    My PC is a desktop which is custom made for GAMING only.

    I have the windows 7 and motherboard disks with it, and the specs are the following:

    Intel core I5-4430 4th gen
    Gigabyte GA-H87M-D3H
    Samsung MZ-7TD 120GB SSD
    Seagate 2TB SATA3 7200 rpm ST2000DM001
    Cooler Master B 700 Serie PSU 700 WATT
    Inno3D Geforce GTX760 2GB GDDR5
    Windows 7
    8GB DDR3 PC1600 1600Mhz


    Ill go make the backup of my system on another external harddrive. :)

    Here is the BUGcodes: from "WhoCrashed"

    On Mon 04-11-2013 20:48:24 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: msrpc.sys (msrpc!NdrMesProcEncodeDecode2+0x20D0)
    Bugcheck code: 0x7A (0xFFFFF6FC40008B28, 0xFFFFFFFFC000000E, 0x76BDF860, 0xFFFFF88001165CD0)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\msrpc.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Kernel Remote Procedure Call Provider

    On Mon 04-11-2013 14:42:53 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110413-5116-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xC2 (0x7, 0x109B, 0x91B8, 0xFFFFF8A0000091D0)
    Error: BAD_POOL_CALLER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System


    On Fri 01-11-2013 23:57:35 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110213-9750-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA80082EB6F0, 0xFFFFFA80082EB9D0, 0xFFFFF8000377C7B0)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System

    On Mon 28-10-2013 13:39:12 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102813-8392-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x153034)
    Bugcheck code: 0x116 (0xFFFFFA800A5104E0, 0xFFFFF8800D5A8034, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 331.65
    company: NVIDIA Corporation


    Hope this is enough information :) - And thank you so much again.
     

Share This Page

Loading...