Saving Older Computer - A Tough Situation

Wait for a minute. I'm working through the procedure with a guide on tenforums.com

EDIT: Okay ... I think I have it set to do an Automatic Memory Dump. Am now waiting for the BSOD on Sleep

 

C:\Windows\Minidump, copy the contents to your Desktop, zip them and attach the zip (or several, if they're too big to attach in one go).

 

Well, that was weird. It went into a sleep and then rolled into a wake up and password request. Should I send that minidump???

 

Okay, I guess the file is too large. Now am figuring out how to break it up.

 

Well, things are VERY weird now!!

1. Before I created post #48 I had found out on the AVAST website that there was an emergency update for the aswvmm.sys.
2. So I did a repair of Avast.
3. Now that I am trying to initiate a BSOD I am not able to.
4. The PC is now going into Sleep without any kind of a BSOD!!
5. However, now the PC immediately rolls into a password request screen within 10 seconds of the Sleep being active. Then the log in password request disappears and the background picture is left on screen.

I'm not able to tell if I fixed something or not. I'm also not able to figure out how to break up a dump file into smaller sizes to post to this thread. Currently 129MB in size.

 

Well ... I must say ... since post #48 I am absolutely mentally and physically worn down. I have tried everything under the sun to keep this PC from waking back up. Now that I got the darn thing to go to sleep without a BSOD it won't stay asleep. Go figure. I have been into everything from Wake On LAN to USB Root hubs to powercfg -lastwake reports from a command prompt. Nothing. I have never seen anything like this beast.

 

Configure the PC to create a small memory dump, a minidump: https://support.microsoft.com/en-us/kb/254649

Use the Sysnative tool to collect other useful data but remove/delete the big memory dump from the zip file before you upload/attach it (if/once you do get a fresh BSOD or two, rerun the app. and upload a fresh set of data).

 

I don't know if this is what is wanted or not for a minidump file ...

 

Yes thanks, that's a minidump

It was a 0xC2 BSOD:

Code:

BugCheck C2, {7, 7249534e, 4080006, ffff8002dd621c90}
Probably caused by : NETIO.SYS ( NETIO!NsiFreeTable+67 )

They're almost always driver related (3rd party hardware/software/Utility). The only 3rd party drivers I see loaded (unless I missed some!) are:
nvmf6264.sys 20/04/2011 22:49:36 nForce network driver < v. old and suspect!
ASACPI.sys 02/11/2012 01:54:34 Asus ATK0110 ACPI Utility < Also used by some Gigabyte utilities.
ambakdrv.sys 25/12/2012 08:46:35 Aomei BackUpper < Old, check for updated version.
ammntdrv.sys 25/12/2012 08:46:37 Aomei BackUpper < see above
amwrtdrv.sys 25/12/2012 08:46:38 Aomei BackUpper < see above
nvstor.sys 21/04/2014 18:34:03 nForce IDE/ATA/SATA controller < (better to replace with the default MS drivers)
nvlddmkm.sys 30/01/2015 23:44:08 nVidia Video
HWiNFO64A.SYS 31/03/2015 09:51:32 HWiNFO64 monitoring driver

The crash stack text contained no 3rd party drivers but the crash appeared to be in the networking subsystem (NETIO.sys), it might be that the old for W10 nForce networking driver was at fault, you'd probably need to disable it in the BIOS and use a newer (Intel?) network card during troubleshooting. Otherwise, it might be a remnant of some previously installed security/firewall, ensure you have used the maker's uninstall routine/tool as instructed for any previous AV/firewall.

Code:

**************************Thu Dec 29 04:06:45.313 2016 (UTC + 0:00)**************************
STACK_TEXT: 
ffffc800`8417d528 fffff802`bd6e1ceb : 00000000`000000c2 00000000`00000007 00000000`7249534e 00000000`04080006 : nt!KeBugCheckEx
ffffc800`8417d530 fffff804`c7a1b377 : ffff8002`dd621c90 fffff804`c7a594a8 00000000`00000000 00000000`00000008 : nt!ExDeferredFreePool+0x54b
ffffc800`8417d610 fffff804`c7a1b8be : 00000000`00000000 00000000`00000002 00000000`00000010 ffffc800`00000000 : NETIO!NsiFreeTable+0x67
ffffc800`8417d640 fffff804`c8382fa0 : fffff804`00000001 00000000`00000000 ffffc800`00000000 ffffc800`8417d810 : NETIO!NetioEnumerateAddress+0x326
ffffc800`8417d7c0 fffff804`c83b20d0 : 00000000`00000002 fffff804`c83a5000 00000000`00000002 00000000`00000003 : srvnet!SrvNetDisableInterface+0x1dc
ffffc800`8417d850 fffff804`c83b21c1 : ffff8002`de504138 00000000`00000002 ffff8002`dd707000 ffff8002`dd707000 : srvnet!SrvNetTdiNotifyChangesToNetBt+0xd0
ffffc800`8417d8b0 fffff804`c82622ee : ffffc800`8417d970 ffff8002`de4a84c0 ffff8002`de4a84c0 00000000`00000000 : srvnet!SrvNetTdiPnPBindingHandler+0xe1
ffffc800`8417d940 fffff804`c8261d4d : fffff804`00000000 ffff8002`dd707010 00000000`00000000 00000000`00000000 : TDI!TdiNotifyPnpClientList+0x1fe
ffffc800`8417d9c0 fffff804`c8261b00 : ffff8002`dc481880 fffff804`c89d41db 00000000`00000000 00000000`00000000 : TDI!TdiExecuteRequest+0x13d
ffffc800`8417da10 fffff804`c89d41db : 00000000`c0000225 ffff8002`db63b4f0 ffffc800`8417db80 fffff804`00000000 : TDI!TdiHandleSerializedRequest+0x120
ffffc800`8417da80 fffff804`c89d3d22 : ffff8002`db63b4f0 00000000`00000000 ffff8002`db63b4f0 fffff802`bd851100 : tdx!TdxProcessInterfaceChangeRoutine+0x46b
ffffc800`8417dbc0 fffff802`bd4e8d11 : ffff8002`dc732c10 ffff8002`dc6a8e40 ffff8002`dc177b90 00000000`00000000 : tdx!NetiopIoWorkItemRoutine+0x42
ffffc800`8417dc10 fffff802`bd52b1b9 : fffff802`bd851100 ffff8002`db7f3040 fffff802`bd4e8c90 fffff802`00000000 : nt!IopProcessWorkItem+0x81
ffffc800`8417dc80 fffff802`bd496729 : ffffc800`83fa1180 00000000`00000080 ffff8002`daaaa040 ffff8002`db7f3040 : nt!ExpWorkerThread+0xe9
ffffc800`8417dd10 fffff802`bd5e3bb6 : ffffc800`83fa1180 ffff8002`db7f3040 fffff802`bd4966e8 61007400`61004400 : nt!PspSystemThreadStartup+0x41
ffffc800`8417dd60 00000000`00000000 : ffffc800`8417e000 ffffc800`84178000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

3rd party drivers loaded (for info only):

Code:

**************************Thu Dec 29 04:06:45.313 2016 (UTC + 0:00)**************************
nvmf6264.sys                Wed Apr 20 23:49:36 2011 (4DAF6300)
ASACPI.sys                  Fri Nov  2 01:54:34 2012 (509327DA)
ambakdrv.sys                Tue Dec 25 08:46:35 2012 (50D967EB)
ammntdrv.sys                Tue Dec 25 08:46:37 2012 (50D967ED)
amwrtdrv.sys                Tue Dec 25 08:46:38 2012 (50D967EE)
nvstor.sys                  Mon Apr 21 19:34:03 2014 (5355649B)
nvlddmkm.sys                Fri Jan 30 23:44:08 2015 (54CC1748)
HWiNFO64A.SYS               Tue Mar 31 10:51:32 2015 (551A6E24)
intelppm.sys                Sat Jul 16 03:10:43 2016 (578997A3)

http://www.carrona.org/drivers/driver.php?id=nvmf6264.sys
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=ambakdrv.sys
http://www.carrona.org/drivers/driver.php?id=ammntdrv.sys
http://www.carrona.org/drivers/driver.php?id=amwrtdrv.sys
http://www.carrona.org/drivers/driver.php?id=nvstor.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
http://www.carrona.org/drivers/driver.php?id=intelppm.sys

Debug output:

Code:

Debug session time: Thu Dec 29 04:06:45.313 2016 (UTC + 0:00)
Loading Dump File [C:\Users\Me\SysnativeBSODApps\122816-26796-01.dmp]
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime: 0 days 0:05:18.071
Probably caused by : NETIO.SYS ( NETIO!NsiFreeTable+67 )
BugCheck C2, {7, 7249534e, 4080006, ffff8002dd621c90}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000C2]BAD_POOL_CALLER (c2)[/url]
Bugcheck code 000000c2
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000007249534e, (reserved)
Arg3: 0000000004080006, Memory contents of the pool block
Arg4: ffff8002dd621c90, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc2_7_NETIO!NsiFreeTable
MaxSpeed:     2830
CurrentSpeed: 2833
BiosVersion = ASUS P5N-D ACPI BIOS Revision 1401
BiosReleaseDate = 06/21/2010
SystemManufacturer = System manufacturer
BaseBoardManufacturer = ASUSTeK Computer INC.
SystemProductName = System Product Name
BaseBoardProduct = P5N-D

 

Thanks satrow. I am going to work through everything you have supplied. Again, many thanks. If nothing is cured then I am going to go to Microsoft website and download the latest MS Win10OS ISO and do a new clean install. I probably should have done that a long time ago per your post #25. Anyway, here we go.

 

Well, I'm back. I decided to just reinstall Win10OS. I have a few ongoing questions to address.

1. Windows 10 has gone through a clean install and installed fine on older P5N-D Asus MOBO
2. (No Asus drivers available for Win 10 for this board)
3. Received replacement RAM from Gskill; great customer service; system now back to 8GB RAM
   
4. System Restore performed
   
5. No ! in Device Manager
6. I have a new Intel NIC card coming in a few days; as suggested by satrow
   
7. ONGOING PROBLEM - Cannot get Sleep mode to function properly at all (any and all online research and Win10 settings has been exhausted to the maximum.)
8. I would very much like to have the functionality of Sleep mode for Team Viewer usage etc.
9. Is the following software a good or bad decision to get Sleep mode functioning??? http://www.passmark.com/products/sleeper.htm
10. If Passmark Sleeper appears acceptable - Should the Sleeper software be attempted this quickly AFTER a clean OS install????

 

The program is safe.

 

Do you know of anyone with experience with the program? Any opinions on whether or not you think it is wise to try something of this nature? Should I wait until I have the new NIC card? Etc., etc.

 

I have heard of the program - it's a 'tester' - it doesn't change anything, and coming from PassMark tells me it's safe.
Try it now and then again after installing the NIC card.

 

Thanks Eldon.

 

I would try installing ASUS/nForce chipset drivers for W8 or even 7 before attempting to force sleep with a third party tool, which is likely to rely on some sleep support via native drivers anyway.

 

Now there is a reply I have been waiting to see!!!!! I have been wondering about that very issue. There are no chipset drivers for the ASUS P5ND 8.1 64bit - but - there are for the Win7 64 bit.

Which brings me to the next thought that has been running through my mind. If I do install the Win7 chipset would you expect the Win10OS to override the Win7 chipset install upon reboot and again install its own Win10 drivers???

 

If they prove stable in the short term but are 'updated' by a W10 Update, you should be able to do a rollback to activate them again from within Task Manager, which should, I think, 'stick' - at least until WU decides it has a later version that might work.

 

Okay. I'm going to give it a try.

 

I have installed the chipset for Windows7. I thought I would just look in Device Manager - but - where exactly do I check to see the chipset driver version in Windows 10?

 

When I last checked 10's Device Manager, it was very similar to W7's, so under System Devices > nVidia or nForce and also under IDE/Atapi controllers in the main section? For exact drivers loaded, Properties tab > Drivers > Driver details button?

 

At this point it looks like nothing installed. I'm going to try a System Restore and then try again. When I installed the Win7 drivers I went into the 64bit sub folder and initiated the install with that executable. This time around I think I'll try to execute via the top ranked setup.exe file and see if there is any option for 64bit vs 32bit. However, it doesn't seem like to me that either way in which I am proceeding would make any difference.

 

Well, that went bad. Restore and Win7 drivers evidently conflicted. Reinstalling Win10OS (for the 5th time). I'm just about ready to trash this MOBO and get some cheap AMD stuff just to get a computer back and running - or - forget about Sleep Mode and let Windows10 do what it wants to do with this motherboard.

 

What did you expect?

When Device Manager shows no ! or ?, you don't mess with updating drivers. Something is bound to go wrong.

 

Well, some of us do, Eldon, esp. where history has shown us that with the first WU run W10 will install 'better' drivers that cause BSODs/black screens and another enforced repair/reinstall on a specific chipset/graphics driver.


Dekade, nVidia must have something later than the nForce 15.57 version from 2011, in the BSOD breakdown above, one of the nForce package drivers was dated as 2014, maybe only MS were supplied with later 'legacy' drivers, maybe for 8.1?

 

My bad satrow, I forgot Windows 10 forces updates on users.

 

Not taking sides, but, I have to agree with this. I am pretty dog gone careful on OS installs and I have learned and experience first hand tons of stuff about the Win10OS especially through ALL the times I have been patiently going through this - on this particular machine. I have read just about every article I can find on the internet. However, I do turn to this forum to finalize any approach I ultimately take.

All indications have been that old windows drivers back through Windows 7 are workable with Windows 10. that doesn't mean they will work; it just means that it is indicated that potential exists. Thus, I try.

Red typeset - I agree. I will take a look at nvidia and see if I can find anything. In the meantime - guess what? - OS clean install number 6! Am I determined or what? This time I am going to install the Chipset drivers before WU can do anything to see if that makes a difference.

 

No Problem. You're fine with me Eldon.

 

The minidump should have been created when the BSOD occurred. You'll find it/them in C:\Windows\minidump. Open the folder, zip the file and upload it in your next reply.

 

No worries here, either Eldon; this 'board isn't 'mainstream', so it's at greater risk of not having decent support/drivers available.

Dekade, how about allowing Windows install drivers to stay but prevent WU from updating them so that you could at least test them for a while?

 

So ... I search for nVidia nforce drivers. This is what I find that offers hope.


Then I follow the link to here - http://www.nvidia.com/download/driverResults.aspx/84889/en-us

That page doesn't make sense.

Then I go to nVidia for Chat support and get this:



Then another inquiry to chat reveals that the MOBO is definitely legacy and no chipsets have been continued for it. And, supposedly 8.1 didn't use a chipset. So the chipset I have is the latest. http://www.nvidia.com/download/driverResults.aspx/30589/en-us

So, I will experiment a few more times then just install the WIN10OS and let it do what it wants to do. Then decided on whether or not to go some cheaper AMD components from NE. At least I have an extra Win10OS license now. Yay!

 

Keep plugging away, either it'll work (eventually) or it won't