Windows 10: windows10 0x00000139 topsecpf.sys parameter 1:00000000`00000003 parameter...

Discus and support windows10 0x00000139 topsecpf.sys parameter 1:00000000`00000003 parameter... in Windows 10 BSOD Crashes and Debugging to solve the problem; Loading Dump File [C:\Users\Administrator\Desktop\0x00000139故障蓝屏日志\081418-20171-01.dmp] Mini Kernel Dump File: Only registers and stack trace are... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by 李宝建, Oct 19, 2018.

  1. 李宝建
    李宝建 Win User

    windows10 0x00000139 topsecpf.sys parameter 1:00000000`00000003 parameter...


    Loading Dump File [C:\Users\Administrator\Desktop\0x00000139故障蓝屏日志\081418-20171-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 16299 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`a5a83000 PsLoadedModuleList = 0xfffff800`a5de9070
    Debug session time: Tue Aug 14 14:35:21.793 2018 (GMT+8)
    System Uptime: 6 days 18:03:29.234
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 139, {3, ffffad0d9434e9c0, ffffad0d9434e918, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : hardware_ram ( PAGE_NOT_ZERO )

    Followup: MachineOwner
    ---------

    *** Memory manager detected 50744 instance(s) of page corruption, target is likely to have memory corruption.

    :)
     
    李宝建, Oct 19, 2018
    #1
  2. WILLSTARNES
    WillStarnes Win User

    ntos kernel stop code - bug check 0x00000139

    My windows 10 box keeps BSOD'ng at various times. Windows update about 6 weeks ago seems to have triggered the event.

    Ran memory test. No errors or problems. Have the dump file.

    ntoskrnl.exe+175930

    Bug check: 0x00000139

    Parameter 1: 00000000`00000003

    Parameter 2: ffffa98b`78c353f0

    Parameter 3: ffffa98b`78c35348

    Parameter 4: 00000000`00000000

    10.0.16299.371 (WinBuild.160101.0800)

    x64
     
    WillStarnes, Oct 19, 2018
    #2
  3. RYANLY
    ryanly Win User
    GPU-Z what command line parameter ?

    Current /? (-?) or / help (-help) parameter is invalid
     
    ryanly, Oct 19, 2018
    #3
  4. JAMES ALLCOCK_992
    James Allcock_992 Win User

    windows10 0x00000139 topsecpf.sys parameter 1:00000000`00000003 parameter...

    KERNAL_SECURITY_CHECK_FAILURE 0x00000139

    Ive been trying for weeks to fix this BSOD issue but still haven't found a solution, I'm hoping you guys can help me out.

    The BSOD started after I installed a new AMD A10-7870k CPU replacing an older AMD A8-6600k CPU. IVe tried updating all my driver but this problem still persists. Ive also gotten other BSOD since relating to - IQL_DRIVER_NOT_LESS_OR_EQUAL and one other.

    The information pasted below is from Blue-screen which analysed dump file and represented this info : )

    ----------------------------------------------------------------------------------------------------------------------

    Bug Check Code: 0x00000139

    Parameter 1: 00000000`00000003

    Parameter 2: ffffd001`05425730

    Parameter 3: ffffd001`05425688

    Parameter 4: 00000000`00000000

    Caused by Driver: ntoskrnl.exe

    Caused by address: ntoskrnl.exe+141f80

    Proccessor: X64

    Id really appreaciate it if you guys could help me on this, ill value any help very respectfully.

    Specs:

    WINDOWS 10 64-bit

    AMD A10-7870K

    AMD R9 380X XFX

    8 GB DDR3

    GIGABYTE F2A88XM-DS2

    Corsair 600W

    Ill owe this site a lot if I can find my awnswer : )
     
    James Allcock_992, Oct 19, 2018
    #4
Thema:

windows10 0x00000139 topsecpf.sys parameter 1:00000000`00000003 parameter...

Loading...

  1. windows10 0x00000139 topsecpf.sys parameter 1:00000000`00000003 parameter... - Similar Threads - windows10 0x00000139 topsecpf

  2. Parameter is Incorrect

    in Microsoft Windows 10 Store
    Parameter is Incorrect: Yesterday microsoft store applications and microsoft store itself werent opening. Instead they showed this error message and now I cant use these applciations. Can someone help me please? I was messing with security permissions last night and now I regret it...

  3. The Parameter is incorrect

    in Windows 10 Software and Apps
    The Parameter is incorrect: I am getting this notification on startup.How can i fix this ? https://answers.microsoft.com/en-us/windows/forum/all/the-parameter-is-incorrect/cce72a1f-2c33-418e-94e7-129f818c9b02

  4. Parameter incorrect

    in AntiVirus, Firewalls and System Security
    Parameter incorrect: Hai ... I am pravinI have a 2tb external harddrive Yesterday I copying my files from my pc.between copying file system is shown" copying error". I click try again button. Then system will getting hang.after plug out my harddrive the system is coming to normalAgain I plugin my...

  5. Parameter incorrect

    in Windows 10 BSOD Crashes and Debugging
    Parameter incorrect: Every few months my laptop has an issue where certain apps will stop working, with a "parameter incorrect" error message. This always seems to happen for the same apps every time regardless of whether they're from the internet, or microsoft store etc, and this issue currently...

  6. "The parameter is incorrect"

    in Windows 10 Network and Sharing
    "The parameter is incorrect": I'm keep getting this error, "the paraeter is incorrect" whenever i try to open a PDF file either from the web or a downloaded file, i just can't open it! It's causing a problem because i cannot print anything that's PDF!...

  7. parameter is incorrect

    in Windows 10 Network and Sharing
    parameter is incorrect: On Windows 10 when I try to create a list of all files of a particular type, I get this message during the search: "The parameter is incorrect." I have run chkdsk and sfc and find no problems. It happens more frequently when the drive being searched is an external USB drive,...

  8. Parameter is invalid

    in AntiVirus, Firewalls and System Security
    Parameter is invalid: Ok since every discussion on this has been closed or locked guess I have to start a new one. This started 3 days ago and it started with the calculator app I'm guessing because I noticed it there first. But now every app including micro store and others now come up with...

  9. parameter

    in Windows 10 Software and Apps
    parameter: why does it say parameter incorrect when i hit print? https://answers.microsoft.com/en-us/windows/forum/all/parameter/1b2e6b2c-6b11-46ef-a22b-ce015fe41dc3

  10. the parameter is incorrect

    in Windows 10 Software and Apps
    the parameter is incorrect: While trying to print I am getting a message saying "The Parameter is incorrect. https://answers.microsoft.com/en-us/windows/forum/apps_windows_10-win_print3d-win_start3d/the-parameter-is-incorrect/2fcb3c04-b14b-4d52-b8a5-96d0162ed6fd
  1. JOSETERAN3
    Thread

    Occasional crash on pc with error 0x00000139

    Hello, I wanted to get help from you guys. In my pc i have been having some crashes every now and then approximately once a month and it seems...
    Thread by: JoseTeran3, Feb 13, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  2. JOSETERAN3
    Thread

    Crash on a pc 0x00000139

    Hello, i have been having occasional reboots in my PC. It seems its a driver given i have tested the hardware sdd, ram, gpu, cpu. I would like to...
    Thread by: JoseTeran3, Feb 11, 2021, 3 replies, in forum: Windows 10 Drivers and Hardware
  3. RONANKGH
    Thread

    Persistant BSOD's on 64bit Windows 10 0x00000139 0x0000000000000003, 0xfffffb8d048f77a0,...

    Hello, I'm struggling with continuous BSOD's. I have disconnected all external hard drives and have performed a Windows reset and the same...
    Thread by: RonanKGH, Feb 9, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  4. ETRA661
    Thread

    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139...

    5/2 The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be 0xffff800600fc1278, 0x8a00000003c00021, 0xfffff18ec9419ab0,...
    Thread by: etra661, Feb 7, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  5. SDOPFIU093R
    Thread

    Computer keeps crashing 0x00000139

    I dont know whats causing these BSOD, I have attached the dumps. Thank you in advance!...
    Thread by: sdopfiu093r, Jan 2, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
Tags:

Users found this page by searching for:

  1. 0x00000139 00000000`00000003

    ,

  2. parameter 1 : 00000000`00000000