New
#11
After you tested the memory. Did you take a known good ram stick and test each socket?
Hi Rich,
No, I have not tried this yet. This is a brand new laptop and I'm not a laptop hardware expert. If it was a desktop, I would feel more comfortable opening it up and moving stuff around. If there is other options, I would like to try them first. Plus, I'm not sure if I have any extra laptop memory that would fit in these sockets.
why don't you take it back to the store?
Last year i brought a Toshiba. It started bsod in the first week. I took it back to the store twice and the last time i got a new laptop.
where i brought mine they have a machine that stress tests the hardware. It takes about 2 hours. The aim is to bsod and error your machine so they can send it back to the computer maker.
I ordered my machine online. I am moving back to school next week and I would like to get it up and running cleanly before then if possible. Obviously, if I can pinpoint a hardware problem, then my only option will be to send it back and wait for them to fix it. I'm hoping my problem is only software related (crossing my fingers) and is fixable by myself. I have yet to update the drivers that Jonathan stated, because I wanted to get some input after I ran the memtest and driver verifier first. This will be my next step when I get home, unless someone tells me to try something else.
PS: I am still confused about what driver verifier actually does, can someone provide some insight or a link to some info about this?
Just an idea.
maybe you should try running nortons removal tool.NETIO.sys was caused by Antivirus application or firewall. What third party antivirus are you using?
Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support
good luck
Ran norton remover tool. No bsod errors yet though. Should i disable the driver verifier?
Let your system run with Driver verifier for 36 hours. If no BSODs, It can be safe to turn it off
My windows has shut itself off one time since I've enabled the driver verifier. I was not sitting in front of it when this happened. Is there any way I can tell if there was a BSOD from this?