I used bluescreen viewer and if you dont know it read mini dumps so you dont have to do the debugging process. It showed something to do with the kernel call procedure. I was wondering if anyone know what thats about? It happened only once in the past almost 24 hours. (like 18 hours since, maybe). I was wondering if it was just a fluke. I heard somewhere I might need to make a new user for windows to fix it. Any help is appreciated.
I dont need the mini dumps I found out the problem. Its Utorrent. Its causing it. Anyone got a fix?
And wow really? Instead of reading you like others tell everyone to upload the mini dumps. I have something to read it already. Way easier then Microsoft debug too.
Then why does it only happen with utorrent running? I left it going all day with lunia running (ijji game). Running at 1gb after sitting for so long my ram was almost maxed out. No bsod. I ran utorrent for 20minutes and I bsod.
What else could cause it?
Upload some minidumps and perhaps it'll be possible to answer those questions.
It's not about "reading" the minidump. That is quite simple. A few clicks of the mouse is all it takes to get that basic textual report. The hard(er) part is understanding what it's trying to say, and how to dig out more info when automated analysis fails to find something actionable.
You can rest assured it's not uTorrent, despite the link to its activity. uTorrent lacks the componentry necessary to directly crash the entire OS.
Since you want to help me so badly and the only person to not tell me im the only one who has issues with windows 7 (like many other forums have). Here ya go.
Every time i reinstall windows I have 1 new issue. First I just kept having weird bsod that would only happen once in a while, and never twice. I cant check my ram because I dont have a cd drive and memtest wont work on a usb. I do not trust windows memory check.
I'm quite confident you've got hardware problems, based on those dumps. All four crashes are different, but in all cases it's a low-level memory access that led to the crash sequence. The one from the 12th of October also exhibits a condition known as "IP misalignment" which virtually proves a hardware defect.
The observed link to uTorrent operation is likely caused by the fact that uTorrent tends to stress the network stack. I know for a fact that uTorrent itself is not the cause of your crashes, and I'd recommend you don't spend time further investigating uTorrent itself.
If you're overclocking, that is a bad idea. If the machine is insufficiently cooled, that by itself can provoke almost any symptom imaginable. Otherwise, if the hardware really is outright faulty, the most likely culprit would be bad or mismatched memory, although that does not rule out other components like the processor or motherboard.
All I have done is put in new ram. My netbook is an acer aspre ONE and is known to have some issues with its wireless. I have had problems where it stops responding untill i reboot or let it shut off for a while. The laptop doesnt get very hot. Even playing a game pushing the cpu and ram usage to a high amount it stays at about 50 - 60c. I dont think I have updated the drivers on my wireless card. Will this help any?
I cannot see any obvious link to your wireless NIC or its drivers in those crashes. On the other hand, if all this started after you "put in new RAM", I think it's very probable that the new stuff is either bad or mismatched with what was already present. You may wish to test whether any of the crash scenarios are still reproducible with the new RAM removed.
Quote