Anyone know a good way to read the codes you get from the BSODs to figure out what the problem is? I thought it was norton and after i erased norton i didn't get one for a couple days. But suddenly they are back today.

I just did a custom install of win7 so my computer was wiped clean. I've run every virus scan and malware scan in the world and those are clean but figured it was anyway since i just wiped my hard drive.


So the problem I'm assuming is either the upgrade to win7 is screwing something up. Or the new 8 GBs of Ram i put in is screwing up. I've ran several tests on the memory itself and all come back fine. And I did a chkdsk on my hard drive and that came up fine. Frustrating the hell out of me.

 

-----signature-----

Did you leave it running memtest86 all night?

http://www.memtest86.com/

 

-----signature-----

You need the first hex code right after the "STOP:" message. Should be "0x########" where the #'s are the code. You can google that number and it'll give you an idea as to the source. If there is also a .dll file listed, you can google that too.

You can also use the Event Viewer (just type 'event' in the start menu search) to find more information as well, under Windows Logs (Application, or System, usually.)

 

-----signature-----

google's probably your best bet outside of calling ms. google the first error code usually outside the parentheses, like 0x000007B for a generic message, and the ones inside the parentheses for more specific info.

 

-----signature-----

Yeah searching the error number didn't come up with much specific. Will try the extensive mem test tomorrow as suggested above, thanks. Also posted my minidumps on a tech forum for win7 in hopes someone there can analyze them and tell me what's up.

 

-----signature-----

memtest doesnt truely STRESS it. Your VOLTAGES and timings can be slightly off and not show during the test but pop up when the whole system is stressed.


You specifically mentioned the memory. Drop down to half of it and run the system normally and see if the problem persists, then swatch the halves out / in and try it again.

I had a driver conflict cause it for the intel onboard gpu (and caused other issues) on my HTPC. I uninstalled all the MB drivers and reinstalled. Then it cleared up.

What I get for using MS update for intel video drivers. Never again for anything non OS specific.

 

-----signature-----

I tried just about everything this weekend. Everything I ran on the memory said it was fine and I tried the above suggestion, the internel memory test and another one I found. No problems found. So spent the rest of the weekend trying to figure it out. Downloaded a program and figured out I was crashing from the ntoskml file having issues. Tried to fix that no luck. Did a repair to replace it. Tried a few other things to fix it that some tech forums said were symptoms of getting a warning on the ntoskml file. Did a complete repair install for win7. etc etc etc


After a day and a half of this s*** finally gave up and yanked out the new memory and put in the old and it fixed the problem lol. Tried to do a few things to make them work and nothing did. So no idea. It was cheap memory from best buy... memory master or something like that so maybe that's what my problem was. Still ran every test I could on them and had no errors or problems reported. Going to take them back today and grab some PNY ones see if that makes a difference. If they cause BSODs I'm giving up and building another computer lol.

 

-----signature-----

"memory master" lol doh.

return em and head directly to newegg to get brand name stuff! really surprising that memtest and your other stress test programs didn't lead you to the memory immediately though.

 

-----signature-----

Yeah it isn't my finest moment. I was getting a bunch of other stuff (mostly blu-rays and some other junk) and was close to the 18 months 0% finance option so went ahead and ordered the RAM there also to get over it lol. Live and learn I suppose.


But yeah, would have made my weekend a lot more enjoyable if those tests worked for me. Not sure what is up with that.

 

-----signature-----