Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

BSOD

Started by lil.devil , Feb 18 2010 12:55 AM

  • Please log in to reply

#16
Broni
Posted 20 February 2010 - 06:59 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Is there anything particular, you're doing while BSOD pops up?

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.
  • 0

Advertisements

#17
lil.devil
Posted 20 February 2010 - 07:33 PM

lil.devil

    Member

  • Topic Starter
  • Member
  • PipPip
  • 21 posts
All done, well except nothing is coming up in the list. I just ran clean up, but I did not think that would have any impact. (registry etc)
How do I check to make sure that mini dump files are saved from BSOD?
  • 0

#18
Broni
Posted 20 February 2010 - 08:11 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
What cleanup was that?

As for dump files, check your settings...

1. Click Start, point to Settings, and then click Control Panel (Start>Control Panel in Vista).
2. Double-click System.
3. Click (Advanced system settings link in Vista, then --->)the Advanced tab, and then click Settings under Startup and Recovery.
4. Make sure, there is a checkmark in Write an event to the system log.
5. In the Write debugging information list, click Small memory dump (64k).
  • 0

#19
lil.devil
Posted 20 February 2010 - 08:33 PM

lil.devil

    Member

  • Topic Starter
  • Member
  • PipPip
  • 21 posts
I am using Desktop Maestro. Guess I should double check what files I have it cleaning.
Ok, it was set for Kernal Memory Dumping. I changed it to small.
  • 0

#20
Broni
Posted 20 February 2010 - 08:45 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Since I'm not familiar with Desktop Maestro, I just check and it deals with registry cleaning.
This is not good. Stay away from any registry cleaning tools.

Now, since you changed settings, let's wait for 3-4 more BSODs and try to run BSV again.
  • 0

#21
lil.devil
Posted 20 February 2010 - 08:56 PM

lil.devil

    Member

  • Topic Starter
  • Member
  • PipPip
  • 21 posts
Oh wow, no kidding...no registry cleaners. Do you use any cleaners at all (well other than spyware,adware etc)?

Are there any programs that you suggest or think are must haves? I feel the need to 're-learn' :)

Edited by lil.devil, 20 February 2010 - 08:59 PM.

  • 0

#22
Broni
Posted 20 February 2010 - 09:02 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Surely, everyone should use cleaners, but those cleaners should concern only garbage (like temporary files).
Couple of cleaners, I use and I recommend:

1. Download Temp File Cleaner (TFC)
Double click on TFC.exe to run the program.
Click on Start button to begin cleaning process.
TFC will close all running programs, and it may ask you to restart computer.

2. Download ATF Cleaner by Atribune.

Double-click ATF-Cleaner.exe to run the program.
Under Main choose: Select All
Unselect Cookies.
Click the Empty Selected button.

If you use Firefox browser
Click Firefox at the top and choose: Select All
NOTE: If you would like to keep your saved passwords, please click No at the prompt.
Unselect Cookies.
Click the Empty Selected button.

If you use Opera browser
Click Opera at the top and choose: Select All
NOTE: If you would like to keep your saved passwords, please click No at the prompt.
Unselect Cookies.
Click the Empty Selected button.

Click Exit on the Main menu to close the program.
  • 0

#23
lil.devil
Posted 20 February 2010 - 09:15 PM

lil.devil

    Member

  • Topic Starter
  • Member
  • PipPip
  • 21 posts
Great, Thanks a bunch!!
It is so hard to find and choose a trustworthy program. And then if you are led in the wrong direction...ugh

I will be back when I have some info from the Blue Screen View.

:)
  • 0

#24
Broni
Posted 20 February 2010 - 09:24 PM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Cool :)
  • 0

#25
lil.devil
Posted 21 February 2010 - 01:17 AM

lil.devil

    Member

  • Topic Starter
  • Member
  • PipPip
  • 21 posts
Well unfortunately I am back already. :)

Hopefully this gives the info needed.

==================================================
Dump File : Mini022110-03.dmp
Crash Time : 2/21/2010 1:58:25 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x01000014
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x87a6186b
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+5849a
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022110-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini022110-02.dmp
Crash Time : 2/21/2010 12:51:41 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x01000014
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x87a6686b
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+5849a
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022110-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini022110-01.dmp
Crash Time : 2/21/2010 12:03:09 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x01000014
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x87a6686b
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+5849a
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022110-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini022010-01.dmp
Crash Time : 2/20/2010 11:16:05 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x01000014
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x87a5a86b
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+5849a
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022010-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================
  • 0

Advertisements

#26
Broni
Posted 21 February 2010 - 01:35 AM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
How long ago was the hard rive replaced?
Did the BSODs start right after fresh Windows install, or later?
Are you doing anything in particular, when BSOD strikes?

Please download SystemLook from one of the links below and save it to your Desktop.
Download Mirror #1
Download Mirror #2
  • Double-click SystemLook.exe to run it.
  • Vista users:: Right click on SystemLook.exe, click Run As Administrator
  • Copy the content of the following box into the main textfield:
    :filefind
tcpip.sys
  • Click the Look button to start the scan.
  • When finished, a notepad window will open with the results of the scan. Please post this log in your next reply.
Note: The log can also be found on your Desktop entitled SystemLook.txt
  • 0

#27
lil.devil
Posted 21 February 2010 - 01:54 AM

lil.devil

    Member

  • Topic Starter
  • Member
  • PipPip
  • 21 posts
How long ago was the hard rive replaced?
Did the BSODs start right after fresh Windows install, or later?
Are you doing anything in particular, when BSOD strikes?



The hard drive was replaced a couple of weeks ago.
The BSOD's were actually occurring before the new hard drive, which I believe he said he made a ghost of my old hard drive.
I would say I am usually doing something online. But today it actually blue screened and I was not touching my laptop. However I am sure I had a browser window open.

See you when I have the next bit of info. :)

Edited by lil.devil, 21 February 2010 - 01:58 AM.

  • 0

#28
lil.devil
Posted 21 February 2010 - 02:05 AM

lil.devil

    Member

  • Topic Starter
  • Member
  • PipPip
  • 21 posts
Ok, here are the results of that scan.



SystemLook v1.0 by jpshortstuff (11.01.10)
Log created at 02:57 on 21/02/2010 by Pauliene (Administrator - Elevation successful)

========== filefind ==========

Searching for "tcpip.sys"
C:\Windows\System32\drivers\tcpip.sys --a--- 904776 bytes [02:13 13/02/2010] [20:01 08/12/2009] DA467E7619AE5F4588E6262C13C8940A
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.18000_none_b31e1252666640f6\tcpip.sys --a--- 891448 bytes [14:29 13/01/2010] [07:43 19/01/2008] FC6E2835D667774D409C7C7021EAF9C4
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.18063_none_b2e033a8669434a1\tcpip.sys --a--- 891448 bytes [17:12 13/01/2010] [08:26 26/04/2008] 82E266BEE5F0167E41C6ECFDD2A79C02
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.18311_none_b3144862666d6db3\tcpip.sys --a--- 897608 bytes [01:56 12/01/2010] [01:56 12/01/2010] 8A7AD2A214233F684242F289ED83EBC3
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.18377_none_b2d96a966698ad63\tcpip.sys --a--- 897624 bytes [02:13 13/02/2010] [20:52 08/12/2009] 1ACBB7A47E78F4CC82D2EFFB72901528
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.22167_none_b36dd19b7fae39c7\tcpip.sys --a--- 891448 bytes [17:12 13/01/2010] [08:08 26/04/2008] 01EC1E92595F839BEE70D439C46796E3
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.22497_none_b34d67897fc6850f\tcpip.sys --a--- 900168 bytes [01:56 12/01/2010] [01:56 12/01/2010] 2608E71AAD54564647D4BB984E1925AA
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.22577_none_b36309477fb64a54\tcpip.sys --a--- 900696 bytes [02:13 13/02/2010] [20:37 08/12/2009] 5653230D480A9C54D169E1B080B72CF5
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.18005_none_b5098b5e63880c42\tcpip.sys --a--- 897000 bytes [21:20 13/01/2010] [06:33 11/04/2009] 0E6B0885C3D5E4643ED2D043DE3433D8
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.18091_none_b4a43aea63d4a25f\tcpip.sys --a--- 904776 bytes [01:56 12/01/2010] [01:56 12/01/2010] 65877AA1B6A7CB797488E831698973E9
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.18160_none_b4c3ac4a63bd325c\tcpip.sys --a--- 904776 bytes [02:13 13/02/2010] [20:01 08/12/2009] DA467E7619AE5F4588E6262C13C8940A
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22200_none_b58e289d7caa2a80\tcpip.sys --a--- 905784 bytes [01:56 12/01/2010] [01:56 12/01/2010] FF71856BD4CD6D4367F9FD84BE79A874
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22283_none_b53aaa1b7ce8560d\tcpip.sys --a--- 907832 bytes [02:13 13/02/2010] [20:15 08/12/2009] 46E6685F3E92AEC743773ADD4CD54F57
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16386_none_5f4ed3e0926e99e4\tcpip.sys --a--- 802816 bytes [08:58 02/11/2006] [08:58 02/11/2006] D944522B048A5FEB7700B5170D3D9423
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16627_none_5f90b964923d030a\tcpip.sys --a--- 803328 bytes [01:20 12/01/2010] [01:20 12/01/2010] 5DF77458AA92FDB36FCE79C60F74AB5D
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16908_none_5fa75f38922bdbf4\tcpip.sys --a--- 813568 bytes [01:56 12/01/2010] [01:56 12/01/2010] 300208927321066EA53761FDC98747C6
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16973_none_5f56ae52926920d8\tcpip.sys --a--- 813568 bytes [02:13 13/02/2010] [17:58 08/12/2009] 8734BD051FFDCBF8425CF222141C3741
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20597_none_5fcea2efab936c1d\tcpip.sys --a--- 803840 bytes [12:30 25/12/2007] [12:30 25/12/2007] 1915A0B89583583A87563750A543D221
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20752_none_5ff4e4f9ab7777f4\tcpip.sys --a--- 806400 bytes [01:20 12/01/2010] [01:20 12/01/2010] 52A8BD6294F7D1443C6184C67AE13AF4
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.21108_none_6030d425ab49af00\tcpip.sys --a--- 816640 bytes [01:56 12/01/2010] [01:56 12/01/2010] 2512B4D1353370D6688B1AF1F5AFA1CF
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.21175_none_5fe223d3ab852692\tcpip.sys --a--- 816640 bytes [02:13 13/02/2010] [17:45 08/12/2009] CA3A5756672013A66BB9D547A5A62DCA

-=End Of File=-
  • 0

#29
lil.devil
Posted 21 February 2010 - 02:08 AM

lil.devil

    Member

  • Topic Starter
  • Member
  • PipPip
  • 21 posts
Ok, here are the results of that scan.



SystemLook v1.0 by jpshortstuff (11.01.10)
Log created at 02:57 on 21/02/2010 by Pauliene (Administrator - Elevation successful)

========== filefind ==========

Searching for "tcpip.sys"
C:\Windows\System32\drivers\tcpip.sys --a--- 904776 bytes [02:13 13/02/2010] [20:01 08/12/2009] DA467E7619AE5F4588E6262C13C8940A
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.18000_none_b31e1252666640f6\tcpip.sys --a--- 891448 bytes [14:29 13/01/2010] [07:43 19/01/2008] FC6E2835D667774D409C7C7021EAF9C4
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.18063_none_b2e033a8669434a1\tcpip.sys --a--- 891448 bytes [17:12 13/01/2010] [08:26 26/04/2008] 82E266BEE5F0167E41C6ECFDD2A79C02
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.18311_none_b3144862666d6db3\tcpip.sys --a--- 897608 bytes [01:56 12/01/2010] [01:56 12/01/2010] 8A7AD2A214233F684242F289ED83EBC3
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.18377_none_b2d96a966698ad63\tcpip.sys --a--- 897624 bytes [02:13 13/02/2010] [20:52 08/12/2009] 1ACBB7A47E78F4CC82D2EFFB72901528
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.22167_none_b36dd19b7fae39c7\tcpip.sys --a--- 891448 bytes [17:12 13/01/2010] [08:08 26/04/2008] 01EC1E92595F839BEE70D439C46796E3
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.22497_none_b34d67897fc6850f\tcpip.sys --a--- 900168 bytes [01:56 12/01/2010] [01:56 12/01/2010] 2608E71AAD54564647D4BB984E1925AA
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6001.22577_none_b36309477fb64a54\tcpip.sys --a--- 900696 bytes [02:13 13/02/2010] [20:37 08/12/2009] 5653230D480A9C54D169E1B080B72CF5
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.18005_none_b5098b5e63880c42\tcpip.sys --a--- 897000 bytes [21:20 13/01/2010] [06:33 11/04/2009] 0E6B0885C3D5E4643ED2D043DE3433D8
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.18091_none_b4a43aea63d4a25f\tcpip.sys --a--- 904776 bytes [01:56 12/01/2010] [01:56 12/01/2010] 65877AA1B6A7CB797488E831698973E9
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.18160_none_b4c3ac4a63bd325c\tcpip.sys --a--- 904776 bytes [02:13 13/02/2010] [20:01 08/12/2009] DA467E7619AE5F4588E6262C13C8940A
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22200_none_b58e289d7caa2a80\tcpip.sys --a--- 905784 bytes [01:56 12/01/2010] [01:56 12/01/2010] FF71856BD4CD6D4367F9FD84BE79A874
C:\Windows\winsxs\x86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22283_none_b53aaa1b7ce8560d\tcpip.sys --a--- 907832 bytes [02:13 13/02/2010] [20:15 08/12/2009] 46E6685F3E92AEC743773ADD4CD54F57
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16386_none_5f4ed3e0926e99e4\tcpip.sys --a--- 802816 bytes [08:58 02/11/2006] [08:58 02/11/2006] D944522B048A5FEB7700B5170D3D9423
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16627_none_5f90b964923d030a\tcpip.sys --a--- 803328 bytes [01:20 12/01/2010] [01:20 12/01/2010] 5DF77458AA92FDB36FCE79C60F74AB5D
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16908_none_5fa75f38922bdbf4\tcpip.sys --a--- 813568 bytes [01:56 12/01/2010] [01:56 12/01/2010] 300208927321066EA53761FDC98747C6
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16973_none_5f56ae52926920d8\tcpip.sys --a--- 813568 bytes [02:13 13/02/2010] [17:58 08/12/2009] 8734BD051FFDCBF8425CF222141C3741
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20597_none_5fcea2efab936c1d\tcpip.sys --a--- 803840 bytes [12:30 25/12/2007] [12:30 25/12/2007] 1915A0B89583583A87563750A543D221
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20752_none_5ff4e4f9ab7777f4\tcpip.sys --a--- 806400 bytes [01:20 12/01/2010] [01:20 12/01/2010] 52A8BD6294F7D1443C6184C67AE13AF4
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.21108_none_6030d425ab49af00\tcpip.sys --a--- 816640 bytes [01:56 12/01/2010] [01:56 12/01/2010] 2512B4D1353370D6688B1AF1F5AFA1CF
C:\Windows\winsxs\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.21175_none_5fe223d3ab852692\tcpip.sys --a--- 816640 bytes [02:13 13/02/2010] [17:45 08/12/2009] CA3A5756672013A66BB9D547A5A62DCA

-=End Of File=-
  • 0

#30
Broni
Posted 21 February 2010 - 10:32 AM

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
I asked you for the above log, because I was thinking about replacing tcpip.sys file with another good copy, but since you told me, that BSODs were happening before replacing hard drive (I assume, you performed clean Windows install, not used some hard drive image), it doesn't make sense anymore.
Are we talking here about wireless, or wired internet connection?
  • 0
Back to Windows Vista and Windows 7 · Next Unread Topic →




Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Geeks to Go Community
  2. → Retired Forums
  3. → Windows Vista and Windows 7

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP