[N130] N130 + Windows 7 getting Bluescreen when booting

[juhulian]

Hello everyone,
I have recently installed Windows 7 on my N130 and after about 1 day it started to crash while loading Windows (sometimes it gets as far as the Welcome screen), giving the following bluescreen:

Hardware Malfunction
NMI: Parity Class / Memory Parity Error

It happend the first time after I updated my BIOS to 05cm, could that be a reason?

I’m realy annoyed because now I never know if it will boot, if not I have to re-try for last time about 10 times and then it works…

Thank you for you help,
Julian

[jeepers01]

[quote1257682195=juhulian]
Hello everyone,
I have recently installed Windows 7 on my N130 and after about 1 day it started to crash while loading Windows (sometimes it gets as far as the Welcome screen), giving the following bluescreen:

Hardware Malfunction
NMI: Parity Class / Memory Parity Error

It happend the first time after I updated my BIOS to 05cm, could that be a reason?

I’m realy annoyed because now I never know if it will boot, if not I have to re-try for last time about 10 times and then it works…

Thank you for you help,
Julian
[/quote1257682195]
Welcome to the forum Julian

It sounds to me to be a memory problem. If you have upgraded to 2GB try putting the 1GB stick back in.

Else run memtest86 to check out the ram.

Have you installed all the Win7 drivers and in particular the VGA(Graphics),INTEL (ver.8.15.10.1912) graphics driver

Hope this helps and let us know how you get on.

[jamiem]

I had the same thing occur and found the fix. I actually performed a bios update and thought it was attributed to that too. Turns out it was the NIC driver received from MS update. I know the error doesn’t correlate to the problem, but I knew my ram was fine since I dual boot linux and that OS had no problems.

Try this;

boot into safe mode
uninstall and remove the drivers of both nics in device manager
download the factory drivers from samsung and install
reboot

[jeepers01]

jamiem – Welcome to the forum

[juhulian]

Thanks for the answers guys, it was acutally one of the drivers. Can’t even tell which, but after installing at least the graphics and the chipset drivers again it didn’t happen again.
cheers

[jeepers01]

[quote1259100858=juhulian]
Thanks for the answers guys, it was acutally one of the drivers. Can’t even tell which, but after installing at least the graphics and the chipset drivers again it didn’t happen again.
cheers
[/quote1259100858]
That’s good news, thanks for letting us know 🙂

[Author]

Posts