New
#1
BSOD on W7 on new notebook
minidump files are in attachment, please help.
thank you
minidump files are in attachment, please help.
thank you
Hello cotanapadne.
As it is a new computer, the best is you take it to the vendor, as it is within warranty.
But if you want us to do something without wasting the warranty, my first suggestion is to uninstall Daemon Tools.
Then Get rid of Lenovo RapidBoot etc, follow Clean Up Factory Bloatware.
Some other things are also may be needed be done, you upload your MSINFO32.nfo file.
- Click on the start button
- Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
- File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
- Give the time for processing, it will save a .nfo file on your desktop.
- Zip it, and upload it following the instruction.
MSINFO32 file uploaded
That is why I wanted it.... in a new computer, the drivers should be new. And so it is. Say the network driver.
But still it is founding the network drivers as a cause of the crash.Code:Name [00000007] Intel(R) 82579LM Gigabit Network Connection Driver c:\windows\system32\drivers\e1c62x64.sys (11.15.16.0, 352,17 KB (360 624 bytes), 5. 10. 2012 0:17)
It appears to me that there must be something that is blocking the drivers. What that may be?Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffffa808d724000, 2, 0, fffff88001c7dc07} *** WARNING: Unable to verify timestamp for ndis.sys *** ERROR: Module load completed but symbols could not be loaded for ndis.sys *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : tcpip.sys ( tcpip!Ipv6AddressType+27 ) Followup: MachineOwner ---------
Most probably the firewall, Comodo.
Alongwith the aforesaid suggestions, you uninstall Comodo, at least as a test.
let us know the results.
thank you, i will try it.