My computer often crashed in BSOD during this two months,which even happen after i reinstalled the win7.Here is the bugcheck: 0x0000000a (0x000000000100002c, 0x0000000000000002, 0x0000000000000000, 0xfffff800050045d0)
Windows 7 x64 OEM version,re-installed but the BSOD still happen
Can anyone help me?
Last edited by vangelion; 18 May 2012 at 10:35.
Hi
Have a read of this thread and follow the instructions to upload dump files
https://www.sevenforums.com/crashes-d...tructions.html
Of course
We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
Please attach the DMP files to your next post not to post one.
If you are overclocking STOP
You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.
The procedure:
To ensure minidumps are enabled:* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
@ zigzag3143：Thanks very much and i have already done this by using your steps
This is the error message I got:
IRQL_NOT_LESS_OR_EQUAL
Problem Event Name:BlueScreen
OS Version: 6.1.7601
Additional information about the problem:
BCCode:0x0000000a
BCP1: 0x000000000100002c
BCP2:0x0000000000000002
BCP3: 0x0000000000000000
BCP4: 0xfffff800050045d0
OS Version: 6.1.7601
Service Pack：SP1
Product:768_1
I'm using Windows 7 Ultimate 64-bit with SP1,an OEM version. I have bought my laptop for 2 years. I performed a full reinstall about 3 months ago and made a backup.During these two months, I'm using the μtorrent(one p2p software) which always keeps a high upload speed(about 4 to 5Mb/s),and I also use my computer doing some other things at the same time,but the BSOD always(normally one time a day) happened suddently. So i use the one-key Ghost to recover the system i have backup,which unexpected is BSOD still happened when i do the same thing before after the recovery.
Last edited by vangelion; 19 May 2012 at 01:07.
Related to k57nd60a.sys NetLink (TM) Gigabit Ethernet NDIS6.x Unified Driver. from Broadcom Corporation. I would update to the newest. Yours is from 2009
ALSO OF NOTE
No information available on google for this 360AntiHacker64.sys. If you are sure of what it is no problem if not run malwarebytes.
Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.
Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!
Thank you for your reply.
About the driver for the Network Interface Card,I got it from the official website of my computer.Even though I will try to upgrade it immediately and see how well the computer will running.
By the way, the file named 360AntiHacker64.sys I think it’s one piece of the 360 Antispyware which it's very popular in my country.After I saw your reply,I search the Internet and found out that there are some similar cases(frequent BSOD) happened at other users who installed it with a same verson.SO I will try to stop use it for a while to confirm if the BSOD is caused by my Antispyware.
Last edited by vangelion; 22 May 2012 at 01:07.
Thanks everyone here!After three days I found no BSOD by using my laptop.I just turn off my antispyware and upgrade a newer NIC driver,so the cause will like what zigzag3143 said.
Thank zigzag3143 very much!
Quote