newsbin.com

I recently upgraded to the latest build and enabled the dual core feature for PARs as I have a x2 6400+ AMD, but when downloading headers it would blue screen Windows 7 I cannot remember the exact message but it was something like "interruption waiting for scheduled task"

Don't know if this will help but this is some of the data from the crash dumps.

Code: Select all

051912-21590-01.dmp   19/05/2012 01:03:43      0x00000101   00000000`00000061   00000000`00000000   fffff880`009e8180   00000000`00000001   HIDCLASS.SYS   HIDCLASS.SYS+d388               x64   ntoskrnl.exe+71f00               C:\Windows\Minidump\051912-21590-01.dmp   2   15   7600   275,536   
051912-21512-01.dmp   19/05/2012 00:42:25      0x00000101   00000000`00000061   00000000`00000000   fffff880`009e8180   00000000`00000001   atikmdag.sys   atikmdag.sys+5d613               x64   ntoskrnl.exe+71f00               C:\Windows\Minidump\051912-21512-01.dmp   2   15   7600   275,536   
051912-31387-01.dmp   19/05/2012 00:22:42      0x00000101   00000000`00000061   00000000`00000000   fffff880`009e8180   00000000`00000001   ataport.SYS   ataport.SYS+945a               x64   ntoskrnl.exe+71f00               C:\Windows\Minidump\051912-31387-01.dmp   2   15   7600   275,536   
051912-32432-01.dmp   19/05/2012 00:15:06      0x00000101   00000000`00000061   00000000`00000000   fffff880`009e8180   00000000`00000001   CLFS.SYS   CLFS.SYS+4cee2               x64   ntoskrnl.exe+71f00               C:\Windows\Minidump\051912-32432-01.dmp   2   15   7600   275,480   


I have since reinstalled newsbin without using dual core mode and it's been on consistently for the last hour.

Might be mistaken but I think the threaded par library had trouble with dual core AMD's, you have that option to force a single core install for that reason.

DT

If that is the case the text before clicking yes or no needs to be more clear.

I have a dual core CPU so obviously I am going to click yes.

If it said it doesn't work on AMD dual core CPUs then I wouldn't bother. At the minute it implies the installer has trouble detecting the CPU and if I have one I should enable it.

Well, I did say I might be mistaken, and I might. It wasn't so much a 'you have to do this' as 'that seemed to help some people in that predicament'. I totally agree if you have a multicore cpu, you should be using it if possible. There's lots of reasons an OS can crash, but if the OS goes down, it's almost *always* a driver problem. Userspace apps don't have permission to crash a system, the entire design is to let the app crash, but keep the OS going. Only drivers have the low level access to cause an exception like that. Sometimes an app can trigger it, but it's always the driver at fault.

You might try that suggestion, see if it helps. It might well not. My anti-AMD sentiments are based on years of running server nodes and very simply, other people running AMD seemed to have issues, and I didn't. It's pure prejudice and might well be out of date. If not, then, you need to look at drivers, graphics driver is one of the most common causes for a desktop. Try updating them if they need it. Also, what the hell, try disabling any antivirus, they are insidious.

I understand you didn't see a problem, you updated NB and suddenly you see a problem, logic dictates it's a 'problem with newsbin'. It's a matter of deleting variables, since so far there's not a swath of crashes out there from users suddenly updating. That symptom is often related to antivirus, FWIW. Each new install is a new program to many AV.

DT