Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

"ntoskrnl.exe" IRQL_NOT_LESS_OR_EQUAL BSOD


  • Please log in to reply
9 replies to this topic

#1 SifuEliminator

SifuEliminator

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:12 AM

Posted 24 September 2017 - 12:23 PM

http://speccy.piriform.com/results/xjOs7dozRaUJHsJ6fuOnRRw

 

Attached is the Sysnative file.

 

--------

 

I'll try to add as much info on what I have done so far and since when this issue arrived.

 

This computer was built 3 months ago, I built it myself had no issue except RAM never posted at rated speed. I RMAed the RAM 3 weeks ago. I have received the RAM 3 days ago, installed it, got a windows update. I have been having BSOD since this.

 

The frequent BSOD are usually happening while gaming, while trying to reinstall drivers, but sometimes happen randomly, like when watch a youtube video, netflix, or even just surfing the web.

 

 

What I have done so far to diagnose and fix this issue:

 

  • Run manually the windows updater to install anything missing (everything is up to date)
  • Updated bios (flashed from version 16 to 17)
  • Factory reset on the UEFI/BIOS, bsod still hapened, so I later on returned to my overclocked settings (3.8Ghz, 1.375V CPUcore, 1.36 RamVoltage, XMP profile 2 (2933Mhz, 1-15-17-17-36 timings)) I also ran AIDA64 for 3 hours and it was stable on my current overclock.
  • Used DDU to remove drivers (I keep getting errors when trying to reinstall the LATEST drivers (old drivers get installed fine) OR a BSOD during the installation process), this means that I currently DO NOT have any display driver installed.
  • Used "chkdsk /f" and "SFC /scannow, nothing was found
  • Used "DISM /Online /Cleanup-Image /RestoreHealth", worked once, then constantly procs a BSOD at 30~40%
  • Ran memtest86+ on a full loop, didn't find any errors
  • Used CCleaner to clean registry
  • Scanned for malware with malware bytes, nothing was found

 

I have yet to try a clean install.

 

My graphic's card is the only used part, it is coming from my old computer, and yes, it is staying at 65~70°C at idle, although I have recently disabled gpu acceleration on firefox, so my graphic's card isn't used at all when I watch videos or netflix. That shouldn't be the issue.

 

Thanks a lot for your time to help me out on my issues with my freshly built computer..

 

EDIT: Started a driver verification following this site's steps. Also starting a clean boot to see if it still BSOD

 

EDIT2: Was able to install most drivers, only 1 failed with the error 1603 code. This is the only driver that failed to install : AMD GPIO Driver (for Promontory).

"DISM /Online /Cleanup-Image /RestoreHealth" caused a BSOD at 50%. Issue is still not fixed from the clean boot.

 

EDIT3: I have tried scanning with AdwCleaner, found nothing. I have tried HitmanPro, found a bunch of tracking cookies on firefox, probably doesn't matter here. 6 BSOD since this post was made, all with same argument. I added a bit of info concerning my graphic's card.

Attached Files


Edited by SifuEliminator, 24 September 2017 - 07:42 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:12 AM

Posted 25 September 2017 - 06:21 AM

The next 2 paragraphs (BIOS and Windows Update) are my standard responses.
I did note that you've updated your BIOS and have run Windows Update.

 

Your UEFI/BIOS (version 1.70) dates from September of 2017.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 3 Windows Update hotfixes installed.  Most build 15063 (1703) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.  i5 and i7 processors can be "auto-overclocked" by using Intel's TurboBoost feature.  If so, it's safe to disregard this caution (for the TurboBoost feature).  Although the system may appear to operate normally with the overclock, there's no way to tell if it's affecting something that we can't see - and that it may be contributing to the problem.

 

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):  New link (15 Aug 2012):  http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html
NOTE:  The uninstaller may not find the SPTD.sys driver.  Don't worry about it, just let us know in your post.
NOTE2:  The latest version has an SPTD2.sys driver - the uninstaller is on the same page as the SPTD.sys driver - just download the version for W10!

Your version of InpOutx64.sys dates from 2008 and is likely not compatible w/W10

Please uninstall the application that uses this driver (more info on the driver here: http://www.highrez.co.uk/ )

If unable to uninstall the program (or if unable to find it), post back for instructions on how to safely remove it (DO NOT DELETE IT!!!  It may make your system unbootable!)

 

Beyond that, if the BSOD's don't stop, please continue running Driver Verifier and let the system crash several times before zipping up and uploading the minidumps from C:\Windows\Minidump (you may have to copy them to your Desktop in order to zip them up).

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Sun Sep 24 12:03:30.183 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092417-3187-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:08:23.804
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff800352a409f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800352a409f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85d
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep 24 11:54:36.467 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092417-3171-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:01:37.087
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff8023652e09f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8023652e09f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85d
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep 24 11:50:57.159 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092417-3093-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:02:48.779
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff802def3009f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802def3009f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85d
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep 24 11:30:28.396 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092417-4062-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:03:56.016
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff800f271c09f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800f271c09f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  msiexec.exe
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep 24 10:19:20.748 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092417-6437-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:15:10.371
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff8016d4ae09f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8016d4ae09f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Sun Sep 24 12:03:30.183 2017 (UTC - 4:00)**************************
inpoutx64.sys               Fri Oct 17 19:01:16 2008 (48F9193C)
amd_sata.sys                Thu Mar 19 02:43:08 2015 (550A6FFC)
amd_xata.sys                Thu Mar 19 02:43:10 2015 (550A6FFE)
dtlitescsibus.sys           Thu Sep 24 16:17:21 2015 (56045A51)
dtliteusbbus.sys            Mon Dec 28 08:05:52 2015 (568133B0)
amdgpio3.sys                Mon Mar 14 06:19:36 2016 (56E69038)
amdgpio2.sys                Tue Aug  9 06:05:07 2016 (57A9AAD3)
AMDRyzenMasterDriver.sys    Tue Jan 31 05:12:42 2017 (5890631A)
ssdevfactory.sys            Mon May  8 12:03:55 2017 (591096EB)
amdpsp.sys                  Mon Jun  5 17:23:56 2017 (5935CBEC)
RTKVHD64.sys                Tue Jul 11 06:59:54 2017 (5964AFAA)
rt640x64.sys                Fri Aug 11 03:41:25 2017 (598D5FA5)
sshid.sys                   Mon Aug 14 19:21:50 2017 (5992308E)
AMDPCIDev.sys               Fri Aug 18 04:11:32 2017 (5996A134)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep 24 11:30:28.396 2017 (UTC - 4:00)**************************
AtihdWT6.sys                Sat Mar 25 17:04:05 2017 (58D6DB45)
atikmpag.sys                Mon Sep 18 19:02:19 2017 (59C0507B)
atikmdag.sys                Mon Sep 18 20:13:58 2017 (59C06146)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep 24 10:19:20.748 2017 (UTC - 4:00)**************************
MpKsl4f3f82c7.sys           Tue May 19 21:50:37 2015 (555BE86D)
rt640x64.sys                Fri May 26 03:02:29 2017 (5927D305)


http://www.carrona.org/drivers/driver.php?id=inpoutx64.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=dtlitescsibus.sys
http://www.carrona.org/drivers/driver.php?id=dtliteusbbus.sys
amdgpio3.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
amdgpio2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
AMDRyzenMasterDriver.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=ssdevfactory.sys
http://www.carrona.org/drivers/driver.php?id=amdpsp.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=sshid.sys
AMDPCIDev.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
MpKsl4f3f82c7.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys

 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 SifuEliminator

SifuEliminator
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:12 AM

Posted 25 September 2017 - 05:15 PM

First of all, thanks for helping me through this.

 

Following your directives, I started by uninstalling Daemon tools.

The SPTD.sys wasn't found by the uninstaller tool.

 

 

I wasn't able to find what program uses the InpOutx64.sys driver, instructions on how to remove it safely would be appreciated.

 

Just in case, I have reset the options of my motherboard once again, so from now on its on factory default options.

 

 

I have done what I know crashes the system, and did it twice in a row (I tried running "DISM /Online /Cleanup-Image /RestoreHealth"). Both times, it crashed at around 50%. I can reproduce this crash every time using this method.

I have attached a minidump zip including my 7 previous crashes, the latest 2 are the one AFTER making the latest modifications.

 

 

Attached Files



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:12 AM

Posted 26 September 2017 - 06:33 AM

Removing the InpOutx64.sys is fairly simple - but tedious.
Don't be surprised if something stops working when you remove it (if it's the keyboard or mouse, use a USB keyboard or mouse to recover)

If you have problems, post back from another system and we'll work you through it as best we can.

 

Here's the steps:

1)   Create a Restore Point using System Restore
2)   Create a Repair disc (Recovery Drive in Win8.1/10):
Win 7 - Go to Start...All Programs...Maintenance...Create a System Repair Disc
Win 8 - Press "WIN" and "R" to open the Run dialog...type "RECDISC" (without the quotes) and press ENTER
Win 8.1 - Go to the Start Screen and type in "recoverydrive" (one word, without the quotes).  That will start the recovery drive process.  You will need a USB drive of at least 512 mB - and all data will be erased off of it.  If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
Win 10 - Go to Start (press the "Win" key) and type in "recoverydrive" (one word, without the quotes).  That will start the recovery drive process.  You will need a USB drive of at least 512 mB - and all data will be erased off of it.  If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
3)   Test the System Repair disc/Recovery Drive to make sure that you can get to the System Restore entry when you boot from the disk/drive (you may also want to try actually using System Restore to make sure that it works)
4)   Download this free program (http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx) and use it to disable any instances of InpOutx64.sys that are starting (or any other InpOutx64/HighRez entries) (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
5)   Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of InpOutx64.sys (or any other InpOutx64/HighRez entries) are "Uninstalled" (DO NOT DISABLE THESE).
6)   Check in the Services applet (services.msc) to be sure any instances of InpOutx64.sys or any other InpOutx64/HighRez entries are disabled.
7)   EXPERIMENTAL STEP (only try if you're certain of your abilities - I have not tried this step myself).  Search the registry (use regedit.exe) to locate any entries that have the driver name (InpOutx64.sys) or the program name (InpOutx64/HighRez).  Delete these keys (it's advisable to back them up first - but you've also backed up the entire registry when creating a System Restore point in step 1.  Alternatively, you can set the values in these keys to DISABLED (but the "how" of this is beyond the scope of this guide).
8)   Go to C:\Windows\System32\drivers and rename the InpOutx64.sys driver to InpOutx64.BAD (search the hard drive for it if it's not in C:\Windows\System32\drivers). (search the hard drive for it if it's not in C:\Windows\System32\drivers).

Also search the system to see if there are any other instances of the InpOutx64.sys driver in other locations - and rename them to InpOutx64.BAD also.
9)   Test to be sure that the device is working OK and that any BSOD's/errors have stopped.


In the event that the system doesn't boot:

1)   Boot from the System Repair disc/Recovery Drive and use the Command Prompt option to rename InpOutx64.BAD to InpOutx64.sys
ren C:\Windows\System32\drivers\InpOutx64.BAD C:\Windows\System32\drivers\InpOutx64.sys
2)   Boot from the System Repair disc/Recovery Drive and use the System Restore option to restore the system to a point before the changes were made.

Good luck!

If the BSOD's continue after this, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

The first 5 memory dumps were run in the previous post.  As such I've only run the last 2 here.

They are very similar to the previous one's and all contain the InpOutx64.sys driver from 2008.

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Mon Sep 25 18:03:26.595 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092517-7453-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
System Uptime:0 days 0:03:20.293
*** ERROR: Module load completed but symbols could not be loaded for NTFS.sys
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff803cdd2209f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803cdd2209f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  TiWorker.exe
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Sep 25 17:59:34.477 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092517-7609-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
System Uptime:0 days 0:02:35.174
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff80080c9b09f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80080c9b09f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  TiWorker.exe
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Sep 25 18:03:26.595 2017 (UTC - 4:00)**************************
inpoutx64.sys               Fri Oct 17 19:01:16 2008 (48F9193C)
amd_sata.sys                Thu Mar 19 02:43:08 2015 (550A6FFC)
amd_xata.sys                Thu Mar 19 02:43:10 2015 (550A6FFE)
MpKsldc6254b2.sys           Tue May 19 21:50:37 2015 (555BE86D)
MpKslbaee9d2b.sys           Tue May 19 21:50:37 2015 (555BE86D)
amdgpio3.sys                Mon Mar 14 06:19:36 2016 (56E69038)
amdgpio2.sys                Tue Aug  9 06:05:07 2016 (57A9AAD3)
zam64.sys                   Wed Aug 17 13:06:53 2016 (57B499AD)
zamguard64.sys              Wed Aug 17 13:06:53 2016 (57B499AD)
AMDRyzenMasterDriver.sys    Tue Jan 31 05:12:42 2017 (5890631A)
AtihdWT6.sys                Sat Mar 25 17:04:05 2017 (58D6DB45)
ssdevfactory.sys            Mon May  8 12:03:55 2017 (591096EB)
amdpsp.sys                  Mon Jun  5 17:23:56 2017 (5935CBEC)
RTKVHD64.sys                Tue Jul 11 06:59:54 2017 (5964AFAA)
rt640x64.sys                Fri Aug 11 03:41:25 2017 (598D5FA5)
sshid.sys                   Mon Aug 14 19:21:50 2017 (5992308E)
atikmpag.sys                Mon Sep 18 19:02:19 2017 (59C0507B)
atikmdag.sys                Mon Sep 18 20:13:58 2017 (59C06146)


http://www.carrona.org/drivers/driver.php?id=inpoutx64.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
MpKsldc6254b2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
MpKslbaee9d2b.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
amdgpio3.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
amdgpio2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=zam64.sys
http://www.carrona.org/drivers/driver.php?id=zamguard64.sys
AMDRyzenMasterDriver.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=ssdevfactory.sys
http://www.carrona.org/drivers/driver.php?id=amdpsp.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=sshid.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 SifuEliminator

SifuEliminator
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:12 AM

Posted 26 September 2017 - 10:27 AM

Allright, I have followed the 9 steps to remove InpOutx64 (including deleting the whole InpOutx64 regedit folder).

 

I have verified with sysInternals, regedit and windows search that nothing was left after a restart of my computer. Nothing was found in sysInternals, nothing in regedit and only the InpOut.BAD was found in the windows search.

 

I have tried my usual method (DISM) and it failed around 50% again twice in a row.

 

Attached is the Sysnative file including the two new Blue screen dumps (I had removed the older dumps earlier). So these dumps are purely from after completely removing InpOutx64.

 

EDIT: Had over 6-7 BSOD since I made this post, so I added a zip file of 5 more BSODs if ever it helps diagnosing my problem :).

Attached Files


Edited by SifuEliminator, 26 September 2017 - 09:28 PM.


#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:12 AM

Posted 27 September 2017 - 05:59 AM

Please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Tue Sep 26 21:39:25.427 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092617-7421-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
System Uptime:0 days 1:07:14.123
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff80166e9709f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80166e9709f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep 26 20:31:41.822 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092617-7484-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
System Uptime:0 days 1:38:43.518
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff8015389e09f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8015389e09f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  LeagueClientUx
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep 26 18:52:28.171 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092617-7593-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
System Uptime:0 days 1:43:56.868
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff802b932509f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802b932509f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep 26 17:08:02.497 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092617-7218-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
System Uptime:0 days 1:21:12.194
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff8032811809f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8032811809f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep 26 15:46:20.403 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092617-7187-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
System Uptime:0 days 1:44:28.101
Probably caused by :memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+18f )
BugCheck A, {30, 2, 0, fffff8020711f09f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8020711f09f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep 26 11:08:49.704 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\092617-7343-01.dmp]
Windows 10 Kernel Version 15063 MP (12 procs) Free x64
System Uptime:0 days 0:16:56.402
*** ERROR: Module load completed but symbols could not be loaded for fileinfo.sys
Probably caused by :fileinfo.sys ( fileinfo+d07f )
BugCheck A, {30, 2, 0, fffff80142aa309f}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80142aa309f, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  TiWorker.exe
FAILURE_BUCKET_ID: AV_fileinfo!unknown_function
  BIOS Version                  1.70
  BIOS Release Date             09/19/2017
  Manufacturer                  MSI
  Product Name                  MS-7A37
  Baseboard Product             B350M MORTAR (MS-7A37)

3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Tue Sep 26 21:39:25.427 2017 (UTC - 4:00)**************************
amd_sata.sys                Thu Mar 19 02:43:08 2015 (550A6FFC)
amd_xata.sys                Thu Mar 19 02:43:10 2015 (550A6FFE)
MpKsl4d47aede.sys           Tue May 19 21:50:37 2015 (555BE86D)
MpKslb4d3f470.sys           Tue May 19 21:50:37 2015 (555BE86D)
MpKsl3ff30dd5.sys           Tue May 19 21:50:37 2015 (555BE86D)
amdgpio3.sys                Mon Mar 14 06:19:36 2016 (56E69038)
amdgpio2.sys                Tue Aug  9 06:05:07 2016 (57A9AAD3)
zam64.sys                   Wed Aug 17 13:06:53 2016 (57B499AD)
zamguard64.sys              Wed Aug 17 13:06:53 2016 (57B499AD)
AMDRyzenMasterDriver.sys    Tue Jan 31 05:12:42 2017 (5890631A)
AtihdWT6.sys                Sat Mar 25 17:04:05 2017 (58D6DB45)
ssdevfactory.sys            Mon May  8 12:03:55 2017 (591096EB)
rt640x64.sys                Fri May 26 03:02:29 2017 (5927D305)
amdpsp.sys                  Mon Jun  5 17:23:56 2017 (5935CBEC)
RTKVHD64.sys                Tue Jul 11 06:59:54 2017 (5964AFAA)
sshid.sys                   Mon Aug 14 19:21:50 2017 (5992308E)
atikmpag.sys                Mon Sep 18 19:02:19 2017 (59C0507B)
atikmdag.sys                Mon Sep 18 20:13:58 2017 (59C06146)


http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
MpKsl4d47aede.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
MpKslb4d3f470.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
MpKsl3ff30dd5.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
amdgpio3.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
amdgpio2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=zam64.sys
http://www.carrona.org/drivers/driver.php?id=zamguard64.sys
AMDRyzenMasterDriver.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=ssdevfactory.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=amdpsp.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=sshid.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 SifuEliminator

SifuEliminator
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:12 AM

Posted 27 September 2017 - 10:17 AM

Ok, I did the driver verifier steps, as soon as it would boot it would crash with the "Driver verifier" argument. I then tried to let it repair itself with the microsoft tools, it did a blue screen during the process. I then try to restart the computer and use the recovery drive, it crashed once again during the process.

 

Restarting the computer, now it does not find an operating drive, which means that the system files were deleted/modified and are now not functionning anymore. While I was creating an installation disk on another computer, I decide to run memtest86+ again.

 

For a reason I do not comprehend, now a full memtest86+ pass yeilded 60000 errors. The issue was one of the two RAM module was bad.

 

Thanks for the time invested into my issue and really sorry for the time I made you loose (since it seems I didn't properly test the ram in the first place.

 

I am now sending back for a second time the RAM kit for RMA and will be doing a clean installation of windows (no choice now!).


Edited by SifuEliminator, 27 September 2017 - 10:18 AM.


#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:12 AM

Posted 28 September 2017 - 06:28 AM

I'm glad that you were able to figure out what the problem was and take the steps to get it fixed properly.

 

I have to wonder about the problems with the disk and the OS that's on it.

Have you checked to see if the disk can be read on another system (or with a bootable OS)?
The data may still be on the disk and may be recoverable.

 

Secondly, if this is the second RMA for the RAM, you have to wonder what's causing it to fail like this.
I'd suggest posting over in the Internal Hardware forums for help with that - as you don't want the system down every couple of weeks while you wait for the RMA .

Here's a link to the Internal Hardware forums:    http://www.bleepingcomputer.com/forums/f/7/internal-hardware/ 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#9 SifuEliminator

SifuEliminator
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:12 AM

Posted 28 September 2017 - 10:45 AM

For information, the first RMA was because the RAM was only posting on 2400 Mhz or lower (while it is rated for 3000Mhz).

 

I started getting the BSOD after I installed the new RAM kit (and got the windows update in the same time), since it seems one of the two module was defective.

 

I currently reinstalled win10, and it is currently running flawlessly (with the defective module removed).

 

About the OS, when booting, I was prompted with a message saying "An operating system wasn't found." (I attached a picture of it) I didn't think of trying to remove it and connect it to another pc as a Data drive to see if it could be read, that would have been a good idea.

 

Thanks for the heads up, if the problem arises again I'm surely going to check on the Internal Hardware forums.

Attached Files



#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:12 AM

Posted 29 September 2017 - 08:17 AM

The Operating System not found error can be due to several different problems:

- bad hard drive

- bad boot stuff

- bad BCD

- missing partitions with the boot stuff.

- missing Windows directory (I think)
- destroyed data structures essential to the loading of Windows

 

As I recall, it's a bit different than a boot problem (but I'm unsure of the details).

I used to know a bit about this, but got away from it in W8. 

The folks in Internal Hardware will likely know more about it than I do.

 

Good luck!


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users