BSOD due to kernel.

[Herox]

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.

 

[H2SO4]

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.

If you upload the minidumps here somebody might be able to help you.

Computers don't do "flukes". Healthy hardware always produces the exact same results when executing a given chunk of code, given the same starting conditions.

 

[Herox]

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.

 

[H2SO4]

I dont need the mini dumps I found out the problem. Its Utorrent. Its causing it. Anyone got a fix?

uTorrent cannot cause a BSOD. It has no kernel-mode componentry. It can theoretically expose a flaw in privileged code, but that's not a uTorrent bug.

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.

da kernAl did da BSODz

 

[Herox]

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?

 

[H2SO4]

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.

 

[Herox]

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.

 

[H2SO4]

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.

 

[Herox]

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?

 

[H2SO4]

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.

 

[Herox]

Well i updated the drivers for it anyway. Its a netbook so it only has 512mb integrated. I cant run a memory test because i have no cd drive. Usb wont work for me. The ram is exactly the same except 1gb instead of the 512mb stick it came with. Both pci 5300. The ram had no problems on windows xp. So why is 7 having so many issues?

 

[H2SO4]

...The ram is exactly the same except 1gb instead of the 512mb stick it came with. Both pci 5300. The ram had no problems on windows xp. So why is 7 having so many issues?

"Mismatched" can mean many things beyond the labeled type.

It doesn't really matter why it did or didn't crash in the past. All that matters is the direct cause of the current crashes. You seem reluctant to entertain the possibility that the new RAM is bad, or that some other hardware component is faulty. Look at it this way: either it's your machine OR Win7 has a bug which causes daily crashes. Since the vast majority of machines running (the same) Win7 code - including mine - don't exhibit this behaviour, it is obviously going to be something specific to your computer.

I'm trying to help you, not upset you. The sooner you get over the (understandable) "surely it can't be my hardware" indignation, the sooner you'll be running tests and identifying the problematic component. I'd suggest lowering your standards and using the Windows memory diagnostic utility.

 

[Herox]

Thats just it. I have used it. No problems. So I wanna use memtest86 but I have no cd drive. It bsod on the old ram too, i did try it before. It cant just be the hardware. I did an extended memory test with windows7 tester before and it froze up. 2 hours later it was still on 21%. I know it says it may look frozen but isnt, but i couldnt navigate to the options. The normal test came up nothing.

 

[H2SO4]

...It cant just be the hardware...

I hope for your sake that my gut feeling (from looking at those minidumps) is wrong.

Given the amount of work already invested, you may want to test what happens when the OS is reinstalled cleanly from scratch, and before it has any updates applied, drivers installed, or anything of the sort. Just the bare OS. You might want to flash the BIOS to the latest version before you start.

Use it long enough to convince yourself whether the behaviour is different. If it doesn't crash, start slowly adding updated drivers. If this turns out to be a software issue, the cause will be a driver.

 

[Herox]

Ive already done a clean install. This one is a clean install. I lost all my game saves and music that ive actually payed for just because of it. At this rate windows 7 isnt even worth it. I only changed from xp because it doesnt get T&L drivers for this **** intel chipset.

It has the latest bios already (3310)

http://www.4allmemory.com/index.cfm?fuseaction=search.memorySearch&manufacturer_id=6&model_id=-8845

It says quote " Memory speed may differ from the original system memory but is guaranteed to work in your computer. When mixed, the memory will run at the slowest speed installed or the highest speed allowed by your system."

This tells me that it should sync up with my integrated ram. Is it just bad? As in its just a not working right?

 

[H2SO4]

Ive already done a clean install. This one is a clean install....

Except it's not exactly clean clean, is it? Here's a list of non-default drivers on your machine at the time of the latest crash, give or take a couple:

87ac0000 87add000 ehdrv Thu May 14 23:31:56 2009 (4A0C1D4C)
8b8c4000 8b8cf000 Epfwndis Thu May 14 23:12:03 2009 (4A0C18A3)
8d26e000 8d37e000 athr Wed Jun 10 04:04:52 2009 (4A2EA444)
a0c12000 a0cce000 eamon Thu May 14 23:30:44 2009 (4A0C1D04)
a0ce8000 a0d0b000 epfw Thu May 14 23:12:05 2009 (4A0C18A5)
a0e40000 a0e4e000 epfwwfp Thu May 14 23:12:05 2009 (4A0C18A5)

NIC drivers, ESET, NOD32, some other firewall... the presence of any of them invalidates the "clean" build test.

 

[Herox]

Because I updated them? Why the hell wouldnt I update my video drivers and install my antivirus? How the hell does that make the install unclean? So I should get a virus just to see if they are causing the problem? Then Id have another problem.

Also when I install windows 7 it updates my video drivers before I even run windows update. I dont freaking understand what my antivirus or a video driver update even has to do with this.

ESET =/= NOD32, they are the same thing, same program.

 

[ickymay]

Because I updated them? Why the hell wouldnt I update my video drivers and install my antivirus? How the hell does that make the install unclean? So I should get a virus just to see if they are causing the problem? Then Id have another problem.

Also when I install windows 7 it updates my video drivers before I even run windows update. I dont freaking understand what my antivirus or a video driver update even has to do with this.

ESET =/= NOD32, they are the same thing, same program.

I have trusted avira antivirus for years as my antivirus of choice and it has never (until now) caused any problems.

using windows 7 i was getting occasional random disk check on boot and I couldn't update my graphics card drivers without getting a BSOD

It took me 6 months of testing then a suggestion from another poster to run a clean install with absolutely nothing installed and sure enough no avira and no BSOD, problem solved

I strongly suggest that you at least try the methods that H2SO4 suggest's, you never know

looking through your mindump files the fact that over the four files youv'e provided only two are caused by the same driver would suggest to me this is random so It's unlikely to be a driver, but is consistent with a ram problem or process intefering with access

 

[Herox]

But i just reinstalled everything yesterday. This is ridicules. YESTERDAY. I reformatted the drive freaking 100% empty using the windows 7 install. nothing left, gone, zip. I installed windows 7. The only times I bsod is when running pidgin multi messenger and utorrent at the same time. I just ran utorrent for an hour no bsoding but i had the messenger off. The messenger is also known to cause BSOD with messages like driver irql not less or equal (you can google it there is a video of it on 7 pro). I dont want to reformat AGAIN. Why do I have to do it again when I just did? I will say that I didnt have any bsod errors before the AV or the messenger or the torrent downloader. It has gotta be one of them pissing something else off. The ram has been checked. the regular windows memory diag finds nothing and the extended gets stuck at 21% and never finishes.

oddly enough I have no BSOD since i started this thread.

 

[H2SO4]

Because I updated them? Why the hell wouldnt I update my video drivers and install my antivirus? How the hell does that make the install unclean? So I should get a virus just to see if they are causing the problem? Then Id have another problem.

Also when I install windows 7 it updates my video drivers before I even run windows update. I dont freaking understand what my antivirus or a video driver update even has to do with this.

ESET =/= NOD32, they are the same thing, same program.

Unlike uTorrent, these drivers most certainly do have the capability to cause a BSOD. Search the web for any one of those names and you'll see examples. It doesn't mean that the specific builds you've got are buggy, nor does their presence prove their guilt, but it does invalidate your "clean machine" testing.

A "clean" install is literally NOTHING that's not part of the OS image. No updates, no AV, no apps, no games... nothing at all. Your aim in this instance is to test whether the machine still crashes in that configuration. If it does, that's another indicator that the hardware is borked.