BSOD randomly strikes when gaming, "ntoskrnl.exe"?

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #11

    Uplooad the minidumpsettings.txt file that the script puts on your desktop.

    # **********************INSTRUCTIONS**************************
    # STEP 1 ** RUN POWERSHELL AS ADMINISTRATOR ******************
    # ************************************************************
    #
    # WIN key | type POWERSHELL | do NOT hit ENTER |
    # in the PROGRAMS list, right-click on WINDOWS POWERSHELL |
    # choose "Run as administrator" |
    # Click on the YES button (if such appears)
    #
    # WIN key = key with Microsoft log on top
    #
    # for the guru:
    # WIN | type POWERSHELL | CTRL+SHIFT+ENTER key combo | ALT+Y keycombo
    # ************************************************************
    # STEP 2 ** COPY AND PASTE ***********************************
    # ************************************************************
    #
    # COPY the script using CTRL+C,
    # COPY every line of script down thru both EXIT statements
    #
    # PASTE into Powershell
    #----Right-Click at the PowerShell Prompt
    #----(Ctrl+V does not work)
    #
    # Start copying with first script line without a # at start of the line
    # Note: Actually, you can paste the entire file if you rather
    #-------Lines starting with a # are ignored by PowerShell
    # ************************************************************
    # STEP 3 ** SCRIPT OUTPUT & SCRIPT PURPOSE *******************
    # ************************************************************
    # --The script output and purpose is given at the very front of the script
    #
    # --The script output and purpose is given at the very front of the script
    #
    # ************************************************************
    # ***************** NOTE - POWERSHELL VERSION*****************
    # if you receive this error msg:
    #--The system can not find the path specified
    # you may need to update your PowerShell
    # you must be using Powershell 2.0 or later.
    #
    # To determine your Powershell version:
    #---Run PowerShell
    #---enter $host.version
    #---you should see at least:
    # Major Minor Build Revision
    # ----- ----- ----- --------
    # 2......0......-1.....-1
    #
    # If you do not see the above, update your Vista/Win 7.
    # ************************************************************
    # *************** NOTE - EXECUTION POLICY*********************
    # If you haven't set the execution policy, you may need to:
    #---Run PowerShell
    #---enter SET-EXECUTIONPOLICY -EXECUTIONPOLICY REMOTESIGNED
    # ************************************************************




    Script:
    # **************************************************************
    # Puts MiniDumpSettings.TXT in your user profile folder
    # WIN | type %userprofile%\ then click on MiniDumpSettings.TXT
    # to view the important minidump settings
    # WIN = key with Microsoft logo on top
    # **************************************************************
    gwmi Win32_OSRecoveryConfiguration 
    select minidumpdirectoryexpandedminidumpdirectory,overwriteexistingdebugfile,kerneldumponly,`
    debuginfotype,autoreboot,writedebuginfo,writetosystemlog > 
    $env:userprofile\minidumpsettings.txt

    EXIT
    EXIT 
      My Computer


  2. Posts : 17
    Microsoft Windows 7 Home Premium x64
    Thread Starter
       #12

    Code:
    minidumpdirectory          : %SystemRoot%\Minidump
    expandedminidumpdirectory  : C:\Windows\Minidump
    overwriteexistingdebugfile : True
    kerneldumponly             : False
    debuginfotype              : 2
    autoreboot                 : False
    writedebuginfo             : True
    writetosystemlog           : True
    It wasnt a huge file so i hope its okay if i just put it here.

    edit: also just a note the minidump folder icon has a "lock" symbol on it, suggesting it has some form of permissions on it, wild guess here but could it be something to do with my pc not having the permission to put one in, strange i know but my reason is i get some in there, but the last two crashes i have had nothing.

    Very.. random.
      My Computer


  3. Posts : 17
    Microsoft Windows 7 Home Premium x64
    Thread Starter
       #13

    Please accept my apologises in multiple posts but i am trying to get a grip on it

    I discovered where the dumps were being saved, it appears it would go to one file "memory.dmp" in windows folder and overwrite on each event, it stated the same "problem"
    Probably caused by : ataport.SYS ( ataport+51e8 )
    This has been saved at 01:45 UTC +1 which is strange as my PC operates in a GMT timezone?

    But i cannot upload it as the file is huge, 374MB?? that cannot be right?
      My Computer


  4. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #14

    toasty,
    I want you to go back over that procedure I gave regarding minidump settings and this time, don't think, just follow the instructions given there.

    After doing that and after rebooting, run that script again. Let's see if this time its correct.

    Your "lock" symbol I don't understand, but we will get to that.
      My Computer


  5. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #15

    toastygstar said:
    Please accept my apologises in multiple posts but i am trying to get a grip on it

    I discovered where the dumps were being saved, it appears it would go to one file "memory.dmp" in windows folder and overwrite on each event, it stated the same "problem"
    Probably caused by : ataport.SYS ( ataport+51e8 )
    This has been saved at 01:45 UTC +1 which is strange as my PC operates in a GMT timezone?

    But i cannot upload it as the file is huge, 374MB?? that cannot be right?
    The reason for the huge file is because you didn't carry out the procedure I gave precisely.

    Don't worry about the timezone thing.
      My Computer


  6. Posts : 17
    Microsoft Windows 7 Home Premium x64
    Thread Starter
       #16

    karlsnooks said:
    toasty,
    I want you to go back over that procedure I gave regarding minidump settings and this time, don't think, just follow the instructions given there.

    After doing that and after rebooting, run that script again. Let's see if this time its correct.

    Your "lock" symbol I don't understand, but we will get to that.
    I followed it to the letter, this file was there prior to me doing that, i just "dug it up".

    I can go back over it again if you like, but i am pretty sure i followed it exactly, the only thing i never did was reboot .
      My Computer


  7. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #17

    I'm rather sure that you didn't. That's why I gave you that script to run. That script lets me know if the settings are as specified.
      My Computer


  8. Posts : 17
    Microsoft Windows 7 Home Premium x64
    Thread Starter
       #18

    karlsnooks said:
    I'm rather sure that you didn't. That's why I gave you that script to run. That script lets me know if the settings are as specified.
    I did go back over it, and where the dmp file is being output has changed... which is odd considering the script said it was something else,

    I have set it to visit "%SystemRoot%\minidump" for the second time. But your script pointed to that anyway, which is why i am confused.

    And you will have to forgive me, i do not know where i have gone wrong, it may well be i have misunderstood your instructions. And it would be helpful if you could point out where it is that is wrong,

    If Overwrite any existing file is checked, then:
    Ø Under Write debugging information, select Kernel memory dump
    Ø Uncheck Overwrite any existing file
    Ø Under Write debugging information, select Small memory dump
    Ø OK button
    This is the bit i am unsure about, my understanding was that if overwrite existing files was checked, keep Kernel memory dump.

    If not then uncheck and change it to small memory dump?
      My Computer


  9. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #19

    I can't say it any simpler. Whether it makes sense or not, If you follow the directions precisely, then all will be correct.

    After carrying the procedure out just as written, then run the script again and upload the file.

    thanks,
    karl
      My Computer


  10. Posts : 17
    Microsoft Windows 7 Home Premium x64
    Thread Starter
       #20

    Code:
    minidumpdirectory          : %SystemRoot%\Minidump
    expandedminidumpdirectory  : C:\Windows\Minidump
    overwriteexistingdebugfile : False
    kerneldumponly             : False
    debuginfotype              : 3
    autoreboot                 : False
    writedebuginfo             : True
    writetosystemlog           : True
    I hope this is the correct output, as i said i believe i misunderstood that specific part of your instructions, i thought the red bullet point was eluding to something else as i couldn't gather why it was needed to select Kernal Memory then Select it to Small Memory dump.

    If this is incorrect then i am sorry, maybe i am tired....
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:36.
Find Us