BSOD (ntoskrnl.exe tcpip.sys)

[ludo92]

Hi guys,

Yesterday came to me the very good idea to change my OS and install Windows 7 instead of my old good friend XP :huh: !

The problem I have is that I get sometimes BSOD when starting computer. It appears to be only when OS is loading, because once loaded I can use it during hours without blue screen...

I opened dump files and it appears to come from ntoskrnl.exe and tcpip.sys. Unfortunately, my knowledges of Windows errors stops here and I really don't know how to solve the problem : I updated all my drivers, ... but nothing is changing. I also did a memory check but no errors are returned.

System Info:

1. My version is a student one (MSDN) of win 7 Pro 64bits.
2. ASUS P5E3 Pro
3. Nvidia GTX 260
4. 4Go RAM (2x2Go DDR3 G.Skills)

I hope that someone could help me before returning to my old XP!

 

[Ell]

Hi, have you tried searching for your error on the actual Win 7 forums on the MS support site???
I have the OEM-RTM of the software and have never seen this problem myself, nor have any of my friends who run Win 7 which leads me to suspect that it may be a glitch in the academic version you have which MS may have posted a fix for.
Sorry I can't really help you more than this, All the best!!!
EJK

 

[ludo92]

No actually some friends have this version too and no problem at all, thats weird...

 

[yowanvista]

You may have a malware infection, run a scan of malwarebytes

Update your LAN/Networking drivers

 

[ludo92]

Well Malwarebytes returned nothing. I updated all drivers, I think now they are all up to date, but this morning again BSOD. Again that's very strange because I have the BSOD at first computer start, then I restart and nothing during all day...

 

[r0mph]

Similar problem with mine:

http://www.sevenforums.com/crashes-debugging/135238-bsod-every-day-only-first-pc-start.html.

I have BSOD only at first PC start of the day...

 

[Tews]

These are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to enable Driver Verifier to help pinpoint the faulting module...

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part). Be sure to upload any new .dmp files that driver verifier generates...

 

[ludo92]

r0mph I have exactly the same problem than you have : BSOD at very first start and than nothing after starting it again... Did you solved it? I did a driver verifier and restarted my computer, no blue screen, so I won't stop computer to see what's happening!

 

[r0mph]

No i haven't solved it yet. I cannot find the root of the problem.

Every BSOD has a different reason. The last one was caused by an ATI driver.

I have uninstalled it and installed a new one and waiting until tomorrow morning to see if I get BSOD again.

 

[ludo92]

BSOD AGAIN! :-( I joined the dmp file. Well I think if i can't solve it I'll try to install the 32bits version or return to XP but that's a little weird...

 

[CarlTR6]

You have some out of date drivers loaded on your system. Out dated drivers can and do cause BSOD's. One driver is really obsolete.

AsIO.sys Mon Dec 17 04:11:49 2007 - Asus PCProbe Utility. ASUSTeK Computer Inc.-Support-. This driver is obsolete. Upgrade PCProbe or uninstall it.

KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - UASSOFT.com HID (mouse) Driver. Suspect that this is a Kensington Mouse Works driver - but there's nothing listed here AFAIK: ÆóÒµµç×ÓÓʾÖ. See if you can update this mouse driver. If you can't, try another mouse and uninstall this one.

RTKVHD64.sys Tue Jun 16 06:12:51 2009 - Realtek High Definition Audio Function Driver. Realtek. Update this driver.

yk60x64.sys Wed Mar 18 12:38:59 2009 - Marvell Yukon Network driver. Marvell: Support. Update this driver.

Take care of these drivers, reboot and see how your system does.