hi there, I bought the laptop second hand with this memory installed.
It has been running ok since September last year. just this week been playing up. I think I have a new 4GB stick spare here.
Here is the log reports using version.
I reinstalled a newer version of the realtek audio driver also.
Many thanks for all your help with this.
Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp
zip > post a link into the thread.
I am having problems uploading the memory.dmp zip file as its 170Mb even zipped is that correct !!
The logs indicated that it was 821 MB before zipping.
See if you can post it using one drive or drop box.
As requested with Onedrive thanks again
https://1drv.ms/u/s!AlIKr6hIZk8c73G6LSPlFPpsm8mB
The memory dump confirmed the misbehaving Nvidia GPU driver.
Perform the following steps:
1) Uninstall the Nvidia GPU using DDU (display driver uninstaller)
2) Re-install from Nvidia website checking the clean install box and if applicable installing the PhysX driver.
Official Display Driver Uninstaller DDU Download
NVIDIA
Display Driver Uninstaller: How to use - Windows 7 Help Forums
I have done as you suggested and have installed new NVIDIA drivers.
it was all going ok and then had a series of BSOD.
Please see attached log files.
The bugchecks were 19.
The BAD_POOL_HEADER bug check has a value of 0x00000019. This indicates that a pool header is corrupt.
The debugging did not display a definitive driver.
There is a Windows tool that is used to find misbehaving drivers.
Windows driver verifier will stimulate drivers so that the misbehaving drivers cause BSOD.
The BSOD dump files are then debugged to find the misbehaving driver(s).
The tool repetitively produces BSOD until all of the misbehaving drivers are fixed or until the tool is turned off.
Before using the tool perform the following steps:
1) backup all files to another drive or to the cloud
2) make a backup image using Macrium
Macrium Software | Your Image is Everything
3) make a brand new restore point
4) learn the 3 methods to turn off the tool
After each BSOD you will turn off the tool and return to the desktop. On the desktop you will then uninstall the misbehaving driver and restart the tool to find the next misbehaving driver. New drivers can be uninstalled as soon as they are uninstalled or they all can be installed at the end once there are no longer any BSOD. The end result should be the same.
The tool is used for 48 hours. After the last BSOD it is used for an additional 36 hours. While using the tool there can be problems with sluggishness and or boot problems. If these problems are significant the customized tests can be modified.
All methods that you will use to turn off the tool are in the Windows advanced troubleshooting menu.
a) startup options (not startup repair) > click restart > select #6 safe mode with command prompt > type:
verifier /reset
b) command prompt > Administrator: X:\Windows\System32\cmd.exe > X:\sources> type:
verifier /bootmode resetonbootfail
c) system restore
The methods to turn off Windows driver verifier should be used in the above order and advanced on the menu only if the prior method fails. System restore often leads to a loss of the dump file and little progress is made in the troubleshooting.
Use the information in this link for the customized test settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Use the information in this link for turning off Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials
After each BSOD post a new zip into the thread:
https://www.tenforums.com/attachment...-v2-beta08.zip
Todays first BSOD attached. For some reason version 2 is not working for me now ?
While using windows driver verifier there were additional BSODs.
Debugging displayed a misbehaving hardware driver.
Update: netwsw00.sys
Netwsw00.sys Tue Feb 05 13:00:21 2013 (511156C5)
Updating a driver: Updating a driver. - Microsoft Community
Netwsw00.sys Intel® Wireless WiFi Link Adapter http://www.intel.com/p/en_US/support
Code:Name [00000001] Intel(R) Centrino(R) Wireless-N 130 Driver Adapter Type Ethernet 802.3Product Type Intel(R) Centrino(R) Wireless-N 130 DriverInstalled YesPNP Device ID PCI\VEN_8086&DEV_0896&SUBSYS_50058086&REV_34\DCA971FFFF8497F700Last Reset 11/02/2018 07:35Index 1Service Name NETwNs64IP Address 192.168.1.141, fe80::f942:bdfa:41c5:a88bIP Subnet 255.255.255.0, 64Default IP Gateway 192.168.1.1DHCP Enabled YesDHCP Server 192.168.1.1DHCP Lease Expires 03/01/1970 00:00DHCP Lease Obtained 01/01/1970 00:00MAC Address DC:A9:71:84:97:F7Memory Address 0xF6200000-0xF6201FFFIRQ Channel IRQ 4294967288Driver c:\windows\system32\drivers\netwsw00.sys (15.4.1.1, 10.99 MB (11,518,976 bytes), 29/09/2017 13:40)Code:11/02/2018 07:30 Windows Error Reporting Fault bucket 0xc4_2000_VRF_Netwsw00!prvMemInitializeLookasideEntry, type 0 Event Name: BlueScreen Response: Not available Cab Id: cb1a22dd-decb-489a-b7bf-821e77b793a6 Problem signature: P1: c4 P2: 2000 P3: fffff80b11342cfb P4: 0 P5: 48746e49 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021118-4609-01.dmp \\?\C:\Windows\TEMP\WER-9500-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3817.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3846.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3856.tmp.txt \\?\C:\Windows\Temp\WER41DC.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_d03279618b50e0f45c1d59e71421b18530b19ef_00000000_cab_0ce918a3 Analysis symbol: Rechecking for solution: 0 Report Id: f4dcdc43-68ce-4572-a216-885035528b6c Report Status: 268435456 Hashed bucket:
Quote