Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD, need help


  • Please log in to reply

#1
richardtran

richardtran

    New Member

  • Member
  • Pip
  • 8 posts
Hi,

I recently got a vaio model vgn ar710e. I installed on windows 7 64bit and shortly after I am getting a bunch of BSOD and hope someone here would be able to solve my problem.

I ran memtest86 and that produced no errors after 5-7 passes.

I have attached the minidump files. If there is any other info you need please let me know.

Attached Files


  • 0

Advertisements


#2
ex_agent

ex_agent

    Member

  • Member
  • PipPip
  • 97 posts
Are you able to provide the error code that it displays?
  • 0

#3
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Your last BSOD indicates that the NETwLv64.sys
Intel® Wireless WiFi Link 4965AGN is the culprit.
Try going HERE and filling in the drop down menus to get the driver. Install and let us know if it corrects the issue for you. I am going over the older BSOD
s now to see if it is the same or not.
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
The other ones form the 28th and 26th for the ntoskrnl.exe suggests you need to look and see if there is any Windows updates from Microsoft you have not done.
  • 0

#5
richardtran

richardtran

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
rshaffer61,

I used http://www.intel.com.../support/detect to find the latest wireless driver. That driver is older than the one found in your link provided. Newest driver is now installed.

As far as I can tell my windows is up to date as of 26/11/2013 with only language packs not installed.
  • 0

#6
richardtran

richardtran

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
ex_agent,

Here are BSOD stop codes.

Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Bugcheck code: 0xD1 (0xFFFFF8000B459510, 0x2, 0x8, 0xFFFFF8000B459510)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80007CB600, 0xFFFF, 0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88002F19110, 0x0, 0x0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002AEF6A0, 0xFFFFF8800310F608, 0xFFFFF8800310EE60)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
  • 0

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
That is strange considering the wireless link is the BSOD from the 28th.
Have you tried a manual Windows update to see if there is anything available. What about optional updates?
  • 0

#8
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
There was also a memory management error from the 26th that might be a memory issue but it points to the nt kernal which is windows and would answer why memtest showed no memory issues.
  • 0

#9
richardtran

richardtran

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
The intel auto detect downloaded the wireless driver version 15.3.1 while finding the driver manually I got version 16.6.0. Sorry for the confusion.

There are no other optional updates other than the language packs. I went threw the update history and found some that failed.

Update for Windows 7 for x64-based Systems (KB977074)
Update for Windows 7 for x64-based Systems (KB974431)
Update for Windows 7 for x64-based Systems (KB2888049)
Update for Windows 7 for x64-based Systems (KB2882822)
Update for Windows 7 for x64-based Systems (KB2729094)
System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [November 2013]
Security Update for Windows 7 for x64-based Systems (KB982799)
Security Update for Windows 7 for x64-based Systems (KB982665)
Security Update for Windows 7 for x64-based Systems (KB979688)
Security Update for Windows 7 for x64-based Systems (KB978542)
Security Update for Windows 7 for x64-based Systems (KB975560)
Security Update for Windows 7 for x64-based Systems (KB972270)
Security Update for Windows 7 for x64-based Systems (KB2347290)
Security Update for Windows 7 for x64-based Systems (KB2296011)
Security Update for Windows 7 for x64-based Systems (KB2281679)
Security Update for Windows 7 for x64-based Systems (KB2032276)
Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 for x64-based Systems (KB2736418)
Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 for x64-based Systems (KB2729451)
Microsoft .NET Framework 3.5 SP1 Update for Windows 7 and Windows Server 2008 R2 for x64-based Systems (KB982526)
Internet Explorer 10 for Windows 7 for x64-based Systems

I will try to manually get them and install them.
  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK thanks and I will wait for your results. :thumbsup:
  • 0

Advertisements


#11
richardtran

richardtran

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
Still having BSOD problems.

I got all the windows updates that failed however upon installing I get 'not applicable' for all updates. This is the last BSOD pulled from WhoCrashed v5.00:


On Fri 29/11/2013 2:54:28 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x89BC9)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Can you do a BlueScreenView for me please.


Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program
  • 0

#13
richardtran

richardtran

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
==================================================
Dump File : 112913-27019-01.dmp
Crash Time : 29/11/2013 5:37:41 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+56e22
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+75b90
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112913-27019-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 270,168
Dump File Time : 29/11/2013 5:38:47 PM
==================================================

==================================================
Dump File : 112913-25069-01.dmp
Crash Time : 29/11/2013 5:05:30 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+56e70
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+75b90
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112913-25069-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 270,168
Dump File Time : 29/11/2013 5:34:06 PM
==================================================

==================================================
Dump File : 112813-38485-01.dmp
Crash Time : 28/11/2013 1:12:39 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+14f4e8
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+75b90
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112813-38485-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 270,168
Dump File Time : 28/11/2013 6:26:41 PM
==================================================

==================================================
Dump File : 112813-28314-01.dmp
Crash Time : 28/11/2013 12:45:02 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff800`0b459510
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : fffff800`0b459510
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112813-28314-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 270,168
Dump File Time : 28/11/2013 12:46:36 PM
==================================================

==================================================
Dump File : 112813-28423-01.dmp
Crash Time : 28/11/2013 12:40:44 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : NETwLv64.sys
Caused By Address : NETwLv64.sys+391130
File Description : Intel® Wireless WiFi Link Driver
Product Name : Intel® Wireless WiFi Link Adapter
Company : Intel Corporation
File Version : 13.4.0.139
Processor : x64
Crash Address : ntoskrnl.exe+75b90
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112813-28423-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 270,112
Dump File Time : 28/11/2013 12:42:55 PM
==================================================

==================================================
Dump File : 112613-29796-01.dmp
Crash Time : 26/11/2013 8:01:21 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+1a7c88
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+75b90
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112613-29796-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 270,168
Dump File Time : 26/11/2013 8:43:37 PM
==================================================

==================================================
Dump File : 112613-56347-01.dmp
Crash Time : 26/11/2013 4:32:52 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`007cb600
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112613-56347-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 270,168
Dump File Time : 26/11/2013 5:05:40 PM
==================================================

==================================================
Dump File : 112613-42603-01.dmp
Crash Time : 26/11/2013 2:09:33 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`02f19110
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112613-42603-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 270,168
Dump File Time : 26/11/2013 2:17:37 PM
==================================================

==================================================
Dump File : 112613-37175-01.dmp
Crash Time : 13/11/2013 2:46:39 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`02aef6a0
Parameter 3 : fffff880`0310f608
Parameter 4 : fffff880`0310ee60
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+5bd80
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+956a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112613-37175-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 270,168
Dump File Time : 26/11/2013 12:53:26 PM
==================================================

==================================================
Dump File : 111213-44803-01.dmp
Crash Time : 12/11/2013 1:43:31 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ndis.sys
Caused By Address : ndis.sys+22f7
File Description : NDIS 6.20 driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+75bd0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111213-44803-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 284,352
Dump File Time : 12/11/2013 1:45:16 PM
==================================================
  • 0

#14
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Most of your BSOD's seem to be caused by the tcpip.sys driver which is related to your network.

First step would be to check Windows update for any updates. Then check motherboard manufacturer or branded system manufacturer website for updated network related drivers.
I would be more leaning toward Windows Updates.
  • 0

#15
rockmilk

rockmilk

    Certified monkey.

  • Member
  • PipPipPipPipPip
  • 2,773 posts
Download and run security check post the log.

http://www.bleepingc.../securitycheck/
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP