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?
"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.
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.
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.
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?...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?
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.
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
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.
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.
Quote
