asus 1201N completely hangs

[wpte]

Hello there

I have an Asus 1201N eee pc with Nvidia ION and a 330N atom cpu.
Also I've upgraded my memory from 2 to 4 GB.
And I installed windows 7 64bit ultimate

So I'm quite an experienced user, I'm studying computer engineering and usually I figure out all the problems my self but these crashes I have are really awkward

What happens is that at some point my laptop screen just freezes, everything stops... no hard-drive activity or anything whatsoever.
Now when something like that happens you can't possibly debug it, but I guess it's due to the nvidia drivers which cannot be restarted by windows for some silly reason.

I did hours of ram testing, tested all nvidia drivers, flashed all bios images out there but still I have these freezes

It only appears to be happening at windows, ubuntu runs fine with the linux nvidia drivers installed.

Can somebody make some suggestions on how to debug or fix these problems?
I'm up-to-date with everything installed, so you can't blame it on that probably

thanks

 

[Zaltys]

I had the same problem earlier. Random hangs, no obvious cause. Nothing in the logs.
Took me weeks to figure it out, but turns out that in my case it was caused by BOINC. It tried doing something, my firewall blocked it and whole system just somehow stopped responding. I never would've suspected it...

So check your software. Even if you're not running BOINC, it could be something similar.

 

[wpte]

I had the same problem earlier. Random hangs, no obvious cause. Nothing in the logs.
Took me weeks to figure it out, but turns out that in my case it was caused by BOINC. It tried doing something, my firewall blocked it and whole system just somehow stopped responding. I never would've suspected it...

So check your software. Even if you're not running BOINC, it could be something similar.

I know boinc, but I only run it on my big quadcore pc with no problems
nothing else is continuously running and using cpu like boinc. Sometimes it's just when my laptop isn't doing anything
Did you use any CUDA enabled applications for boinc?

I just use my windows firewall and Microsoft security essentials, so I guess that should be fine

 

[zigzag3143]

Hello there

I have an Asus 1201N eee pc with Nvidia ION and a 330N atom cpu.
Also I've upgraded my memory from 2 to 4 GB.
And I installed windows 7 64bit ultimate

So I'm quite an experienced user, I'm studying computer engineering and usually I figure out all the problems my self but these crashes I have are really awkward

What happens is that at some point my laptop screen just freezes, everything stops... no hard-drive activity or anything whatsoever.
Now when something like that happens you can't possibly debug it, but I guess it's due to the nvidia drivers which cannot be restarted by windows for some silly reason.

I did hours of ram testing, tested all nvidia drivers, flashed all bios images out there but still I have these freezes

It only appears to be happening at windows, ubuntu runs fine with the linux nvidia drivers installed.

Can somebody make some suggestions on how to debug or fix these problems?
I'm up-to-date with everything installed, so you can't blame it on that probably

thanks

can you check event viewer? (type eventvwr ins search)go to the windows logs>application tab. Look for critical errors (they have red in the left hand column) that say app hang, app crash, etc. Note the event ID and source code and relay that info to us

let us know if you need help


Ken

 

[wpte]

can you check event viewer? (type eventvwr ins search)go to the windows logs>application tab. Look for critical errors (they have red in the left hand column) that say app hang, app crash, etc. Note the event ID and source code and relay that info to us

let us know if you need help


Ken

uuhh, a lot of information log entries, but also system hangs.
I have a dutch version of windows, but I guess you can get the basic info out of it

I remember media player classic froze the screen here, but that was once:

Het programma mpc-hc64.exe, versie 1.3.1249.0 reageert niet meer op Windows en is afgesloten. Als u wilt zien of er meer informatie over het probleem beschikbaar is, raadpleegt u de probleemgeschiedenis in het onderdeel Onderhoudscentrum in het Configuratiescherm.
Proces-id: f50
Starttijd: 01cacae2944daa90
Eindtijd: 15
Toepassingspad: C:\Program Files\MPC HomeCinema (x64)\mpc-hc64.exe
Rapport-id: 0142ea21-36d6-11df-8f47-002243d6b167

it says cross-thread in the binary data... not exactly something that should instantly hangs your pc, more or less a critical error tho.

a lot of erros from microsoft security essentials (almost all of them):

Naam van toepassing met fout: MpCmdRun.exe, versie: 2.1.6519.0, tijdstempel: 0x4b207819
Naam van module met fout: mssewat.dll, versie: 1.0.1961.0, tijdstempel: 0x4b81283b
Uitzonderingscode: 0xc0000005
Foutoffset: 0x00000000000045a4
Id van proces met fout: 0x7e8
Starttijd van toepassing met fout: 0x01cac92f73335bc0
Pad naar toepassing met fout: c:\Program Files\Microsoft Security Essentials\MpCmdRun.exe
Pad naar module met fout: C:\Program Files\Microsoft Security Essentials\mssewat.dll
Rapport-id: b2214040-3522-11df-869f-002243d6b167

they are all quite similar to this report

Naam van toepassing met fout: splwow64.exe, versie: 6.1.7600.16385, tijdstempel: 0x4a5bd3ca
Naam van module met fout: ntdll.dll, versie: 6.1.7600.16385, tijdstempel: 0x4a5be02b
Uitzonderingscode: 0xc0000710
Foutoffset: 0x000000000006f089
Id van proces met fout: 0xba4
Starttijd van toepassing met fout: 0x01cabd68a796d180
Pad naar toepassing met fout: C:\Windows\splwow64.exe
Pad naar module met fout: C:\Windows\SYSTEM32\ntdll.dll
Rapport-id: eafd7c80-295b-11df-ab3d-002243d6b167

other events are from regular programs that didn't cause any freeze-ups as far as I can remember.

Are these logs what you are looking for?
I didn't see something quite similar to what you've asked

 

[wpte]

So I had a few other crashes recently, usually when I'm on battery (a fully recharged one)

and when I look in the event viewer, I can't see any log of it!
so I guess we need another way to debug.