New Yoga 2 Pro bluescreens every other day.

Not sure if this is the right place, but I saw some links that took me to a very similar place so hopefully someone can help me out.

I just got a new laptop and it keeps blue screening anywhere from twice a day to every other day.

I get BAD_POOL_HEADER and DPC_WATCHDOG_VIOLATION usually.

Also I checked my event viewer and I have 5400(!) errors! Is that common? Many of them are "PGService (PGServiceUpdate): can not access pg_user.ini file"

I uploaded my minidump folder to skydrive here http://sdrv.ms/MjQ4P5

Thanks in advance to anyone who can help me out.

Also segoe UI looks beautiful here.

January 30th, 2014 4:39am

Because of the various apparent causes you need to run driver verifier to find the underlying cause. 

These crashes were related to memory management (probably caused by a driver). 

Please run this test to find which driver is causing the problem.  


 If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

 Driver verifier (for complete directions see our wikihere)

Co-Authored by  JMH3143

Bugcheck code 00000019
Bugcheck code 00000133
Bugcheck code 00000133
Bugcheck code 00000019
Bugcheck code 00000019
Bugcheck code 00000019
Bugcheck code 00000019
Bugcheck code 00000019
Bugcheck code 00000019



``

BugCheck 19, {d, ffffd0003552d230, ffffe000070bb210, 1b6c17bbd601b012}
BugCheck 133, {1, 1e00, 0, 0}
BugCheck 133, {1, 1e00, 0, 0}
BugCheck 19, {d, ffffd00034c06230, ffffe0000687cc70, 3002c6bd323ebe79}
BugCheck 19, {e, ffffd00034a16230, ffffe00006e2ab50, fa805b46fd3c2d47}
BugCheck 19, {e, ffffd000351b2230, ffffe000063b1a70, e6a85969d2dcbc2c}
BugCheck 19, {e, ffffd00023fa1230, ffffe0000127d820, c002ee833c3c7bac}
BugCheck 19, {e, ffffd00023fb6230, ffffe0000721dc40, 77fab3874a0de4ce}
BugCheck 19, {d, ffffd00020dda230, 0, b24066f7ab9dbdaa}
``

``

BugCheck 19, {d, ffffd0003552d230, ffffe000070bb210, 1b6c17bbd601b012}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
``
BugCheck 133, {1, 1e00, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
``
BugCheck 133, {1, 1e00, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
``
BugCheck 19, {d, ffffd00034c06230, ffffe0000687cc70, 3002c6bd323ebe79}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
``
BugCheck 19, {e, ffffd00034a16230, ffffe00006e2ab50, fa805b46fd3c2d47}
Probably caused by : tcpip.sys ( tcpip!UdpTlProviderEndpoint+ed )
``
BugCheck 19, {e, ffffd000351b2230, ffffe000063b1a70, e6a85969d2dcbc2c}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+c0d )
``
BugCheck 19, {e, ffffd00023fa1230, ffffe0000127d820, c002ee833c3c7bac}
Probably caused by : tcpip.sys ( tcpip!UdpTlProviderEndpoint+ed )
``
BugCheck 19, {e, ffffd00023fb6230, ffffe0000721dc40, 77fab3874a0de4ce}
Probably caused by : Ndu.sys ( Ndu!NduCreateFlowContext+151 )
``
BugCheck 19, {d, ffffd00020dda230, 0, b24066f7ab9dbdaa}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
``
SYSTEM UP-TIME
System Uptime: 0 days 0:28:15.297
System Uptime: 0 days 3:02:36.953
System Uptime: 0 days 4:12:10.328
System Uptime: 0 days 9:04:48.899
System Uptime: 0 days 15:52:28.866
System Uptime: 0 days 1:36:01.870
System Uptime: 0 days 1:32:50.916
System Uptime: 1 days 10:06:55.239
System Uptime: 0 days 1:28:20.703
``



Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Tue Jan 28 16:57:59.272 2014 (UTC - 5:00)
System Uptime: 0 days 0:28:15.297
BugCheck 19, {d, ffffd0003552d230, ffffe000070bb210, 1b6c17bbd601b012}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
BUGCHECK_STR:  0x19_d
PROCESS_NAME:  System
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Tue Jan 28 09:33:05.483 2014 (UTC - 5:00)
System Uptime: 0 days 3:02:36.953
BugCheck 133, {1, 1e00, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
BUGCHECK_STR:  0x133
PROCESS_NAME:  networx.exe
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Mon Jan 27 05:49:39.304 2014 (UTC - 5:00)
System Uptime: 0 days 4:12:10.328
BugCheck 133, {1, 1e00, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
BUGCHECK_STR:  0x133
PROCESS_NAME:  networx.exe
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Mon Jan 27 01:37:08.859 2014 (UTC - 5:00)
System Uptime: 0 days 9:04:48.899
BugCheck 19, {d, ffffd00034c06230, ffffe0000687cc70, 3002c6bd323ebe79}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
BUGCHECK_STR:  0x19_d
PROCESS_NAME:  chrome.exe
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Sun Jan 26 16:31:34.794 2014 (UTC - 5:00)
System Uptime: 0 days 15:52:28.866
BugCheck 19, {e, ffffd00034a16230, ffffe00006e2ab50, fa805b46fd3c2d47}
Probably caused by : tcpip.sys ( tcpip!UdpTlProviderEndpoint+ed )
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  LsvController.
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Thu Jan 23 15:25:21.844 2014 (UTC - 5:00)
System Uptime: 0 days 1:36:01.870
BugCheck 19, {e, ffffd000351b2230, ffffe000063b1a70, e6a85969d2dcbc2c}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+c0d )
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  MsMpEng.exe
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Wed Jan 22 15:27:19.875 2014 (UTC - 5:00)
System Uptime: 0 days 1:32:50.916
BugCheck 19, {e, ffffd00023fa1230, ffffe0000127d820, c002ee833c3c7bac}
Probably caused by : tcpip.sys ( tcpip!UdpTlProviderEndpoint+ed )
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  chrome.exe
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Sun Jan 19 04:26:36.207 2014 (UTC - 5:00)
System Uptime: 1 days 10:06:55.239
BugCheck 19, {e, ffffd00023fb6230, ffffe0000721dc40, 77fab3874a0de4ce}
*** WARNING: Unable to verify timestamp for NETwbw02.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwbw02.sys
Probably caused by : Ndu.sys ( Ndu!NduCreateFlowContext+151 )
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  System
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Fri Jan 17 15:09:56.670 2014 (UTC - 5:00)
System Uptime: 0 days 1:28:20.703
BugCheck 19, {d, ffffd00020dda230, 0, b24066f7ab9dbdaa}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
BUGCHECK_STR:  0x19_d
PROCESS_NAME:  chrome.exe




Free Windows Admin Tool Kit Click here and download it now
January 30th, 2014 7:47am

I read one of your dumps and it is not looking good.

011714-3968-01.dmp 1/17/2014 3:09:56 PM BAD_POOL_HEADER 0x00000019 00000000`0000000d ffffd000`20dda230 00000000`00000000 b24066f7`ab9dbdaa hal.dll hal.dll+6627     x64 ntoskrnl.exe+14dca0    011714-3968-01.dmp 4 15 9600 284,608 1/17/2014 3:10:21 PM 

the error is caused by driver hal.dll

sfc /scannow

You may need to do a reset, you have corrupted system files





  • Edited by colakid 21 hours 44 minutes ago
January 30th, 2014 8:54am

I have gone through all the files and they are all system files, what caused that I'm not sure. Virus, overclocking, bad harddrive.

Reset you computer.

Caused by afdsys


  • Edited by colakid 21 hours 40 minutes ago
Free Windows Admin Tool Kit Click here and download it now
January 30th, 2014 9:04am
Hopefully I did the driver verifer thing right. Here is the new dump. http://sdrv.ms/1bakwkW
January 30th, 2014 11:37am
Gonna reset my computer this afternoon. Computer is definitely not overclocked. I suppose a virus is a possibility. What is the percentage chance that the problem is a bad hard drive and what steps can I do to test that? 
Free Windows Admin Tool Kit Click here and download it now
January 30th, 2014 11:39am

Check your drive for errors, there is a chance or a driver, antivirus software something you installed mostly causing a error. let some of us look at your new dump we well get back. Repair your files using this command

sfc /scannow



  • Edited by colakid 16 hours 25 minutes ago
January 30th, 2014 11:57am

Because of the various apparent causes you need to run driver verifier to find the underlying cause. 

These crashes were related to memory management (probably caused by a driver). 

Please run this test to find which driver is causing the problem.  


 If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

 Driver verifier (for complete directions see our wikihere)

Co-Authored by  JMH3143

Bugcheck code 00000019
Bugcheck code 00000133
Bugcheck code 00000133
Bugcheck code 00000019
Bugcheck code 00000019
Bugcheck code 00000019
Bugcheck code 00000019
Bugcheck code 00000019
Bugcheck code 00000019



``

BugCheck 19, {d, ffffd0003552d230, ffffe000070bb210, 1b6c17bbd601b012}
BugCheck 133, {1, 1e00, 0, 0}
BugCheck 133, {1, 1e00, 0, 0}
BugCheck 19, {d, ffffd00034c06230, ffffe0000687cc70, 3002c6bd323ebe79}
BugCheck 19, {e, ffffd00034a16230, ffffe00006e2ab50, fa805b46fd3c2d47}
BugCheck 19, {e, ffffd000351b2230, ffffe000063b1a70, e6a85969d2dcbc2c}
BugCheck 19, {e, ffffd00023fa1230, ffffe0000127d820, c002ee833c3c7bac}
BugCheck 19, {e, ffffd00023fb6230, ffffe0000721dc40, 77fab3874a0de4ce}
BugCheck 19, {d, ffffd00020dda230, 0, b24066f7ab9dbdaa}
``

``

BugCheck 19, {d, ffffd0003552d230, ffffe000070bb210, 1b6c17bbd601b012}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
``
BugCheck 133, {1, 1e00, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
``
BugCheck 133, {1, 1e00, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
``
BugCheck 19, {d, ffffd00034c06230, ffffe0000687cc70, 3002c6bd323ebe79}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
``
BugCheck 19, {e, ffffd00034a16230, ffffe00006e2ab50, fa805b46fd3c2d47}
Probably caused by : tcpip.sys ( tcpip!UdpTlProviderEndpoint+ed )
``
BugCheck 19, {e, ffffd000351b2230, ffffe000063b1a70, e6a85969d2dcbc2c}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+c0d )
``
BugCheck 19, {e, ffffd00023fa1230, ffffe0000127d820, c002ee833c3c7bac}
Probably caused by : tcpip.sys ( tcpip!UdpTlProviderEndpoint+ed )
``
BugCheck 19, {e, ffffd00023fb6230, ffffe0000721dc40, 77fab3874a0de4ce}
Probably caused by : Ndu.sys ( Ndu!NduCreateFlowContext+151 )
``
BugCheck 19, {d, ffffd00020dda230, 0, b24066f7ab9dbdaa}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
``
SYSTEM UP-TIME
System Uptime: 0 days 0:28:15.297
System Uptime: 0 days 3:02:36.953
System Uptime: 0 days 4:12:10.328
System Uptime: 0 days 9:04:48.899
System Uptime: 0 days 15:52:28.866
System Uptime: 0 days 1:36:01.870
System Uptime: 0 days 1:32:50.916
System Uptime: 1 days 10:06:55.239
System Uptime: 0 days 1:28:20.703
``



Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Tue Jan 28 16:57:59.272 2014 (UTC - 5:00)
System Uptime: 0 days 0:28:15.297
BugCheck 19, {d, ffffd0003552d230, ffffe000070bb210, 1b6c17bbd601b012}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
BUGCHECK_STR:  0x19_d
PROCESS_NAME:  System
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Tue Jan 28 09:33:05.483 2014 (UTC - 5:00)
System Uptime: 0 days 3:02:36.953
BugCheck 133, {1, 1e00, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
BUGCHECK_STR:  0x133
PROCESS_NAME:  networx.exe
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Mon Jan 27 05:49:39.304 2014 (UTC - 5:00)
System Uptime: 0 days 4:12:10.328
BugCheck 133, {1, 1e00, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
BUGCHECK_STR:  0x133
PROCESS_NAME:  networx.exe
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Mon Jan 27 01:37:08.859 2014 (UTC - 5:00)
System Uptime: 0 days 9:04:48.899
BugCheck 19, {d, ffffd00034c06230, ffffe0000687cc70, 3002c6bd323ebe79}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
BUGCHECK_STR:  0x19_d
PROCESS_NAME:  chrome.exe
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Sun Jan 26 16:31:34.794 2014 (UTC - 5:00)
System Uptime: 0 days 15:52:28.866
BugCheck 19, {e, ffffd00034a16230, ffffe00006e2ab50, fa805b46fd3c2d47}
Probably caused by : tcpip.sys ( tcpip!UdpTlProviderEndpoint+ed )
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  LsvController.
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Thu Jan 23 15:25:21.844 2014 (UTC - 5:00)
System Uptime: 0 days 1:36:01.870
BugCheck 19, {e, ffffd000351b2230, ffffe000063b1a70, e6a85969d2dcbc2c}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+c0d )
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  MsMpEng.exe
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Wed Jan 22 15:27:19.875 2014 (UTC - 5:00)
System Uptime: 0 days 1:32:50.916
BugCheck 19, {e, ffffd00023fa1230, ffffe0000127d820, c002ee833c3c7bac}
Probably caused by : tcpip.sys ( tcpip!UdpTlProviderEndpoint+ed )
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  chrome.exe
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Sun Jan 19 04:26:36.207 2014 (UTC - 5:00)
System Uptime: 1 days 10:06:55.239
BugCheck 19, {e, ffffd00023fb6230, ffffe0000721dc40, 77fab3874a0de4ce}
*** WARNING: Unable to verify timestamp for NETwbw02.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwbw02.sys
Probably caused by : Ndu.sys ( Ndu!NduCreateFlowContext+151 )
BUGCHECK_STR:  0x19_e
PROCESS_NAME:  System
``
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Debug session time: Fri Jan 17 15:09:56.670 2014 (UTC - 5:00)
System Uptime: 0 days 1:28:20.703
BugCheck 19, {d, ffffd00020dda230, 0, b24066f7ab9dbdaa}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+e97 )
BUGCHECK_STR:  0x19_d
PROCESS_NAME:  chrome.exe




http://www.file.net/process/networx.exe.html
Free Windows Admin Tool Kit Click here and download it now
January 30th, 2014 12:31pm

I have the sutiable time to debug your dmps

Dump file shows a error in lsvcontroller.exe.(different files for filename lsvcontroller.exe . This files most often belongs to product Lenovo Smart Voice)cause of the tcp error.

Second error in chrome.exe do a google for reason for chrome.exe error.

Error in tcp possible cause of this is lvs sharing the same irq as a device you may need a new driver or check irqs.

Error networkx  

it is very possible networkx and lsv and chrome, is the culprit of the error looks like you need updated drivers or programs that are compatible with windows 8.1. It may be to late because core windows components have been infected



  • Edited by colakid 6 hours 18 minutes ago
January 31st, 2014 12:20am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics