New
#1
BSOD Ntoskrnl.exe, tcpip.sys
My PC's been blue screening every hour or so and I'm not too sure why. I've attached my crash dumps, if someone could help it would be greatly appreciated!
My PC's been blue screening every hour or so and I'm not too sure why. I've attached my crash dumps, if someone could help it would be greatly appreciated!
The BSOD is caused by Intel(R) 82583V Gigabit Network Connection driver.
And the driver is old.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {8, 2, 0, fffff880016465b3} *** WARNING: Unable to verify timestamp for e1q62x64.sys *** ERROR: Module load completed but symbols could not be loaded for e1q62x64.sys Probably caused by : e1q62x64.sys ( e1q62x64+239e9 ) Followup: MachineOwner ---------
Update it from https://downloadcenter.intel.com/default.aspxCode:fffff880`11000000 fffff880`1104c000 e1q62x64 T (no symbols) Loaded symbol image file: e1q62x64.sys Image path: \SystemRoot\system32\DRIVERS\e1q62x64.sys Image name: e1q62x64.sys Timestamp: Fri Jul 09 03:37:00 2010 (4C364C04) CheckSum: 000506D5 ImageSize: 0004C000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Let us know the results.
Hello! About an hour after I posted this thread I decided to do some research and from this I discovered what tcpip.sys was responsible for and decided that it was a good idea to update the Intel ethernet drivers after this I encountered no BSODs. The ones I had downloaded previously were from the motherboard's manufacture website, this had taught me the lesson of always getting up to date drivers.
Thank you very much for your help.