Helproom Download forum rules

Start new subject | Reply to this subject

[1] 2 

 Roy*

Sat, 17/10/09@13:27

Canon MP610 with XP often causes blue screen crashes, normally when you send to print but sometimes just by switching on. I’ve tried updating drivers from the Canon site but this has had no effect, unless I’m getting the wrong drivers? My PC is few years old and has low memory compared to what’s the norm now, could this have anything to do with it?

Any suggestions much appreciated.

 jack

Sat, 17/10/09@14:05

What cable are you using?

I note you say computer is a few years old so is it a USB or old style parallel?
Could be you see you have set the incorrect port
LPT1 old style
USB Printer new style
Also change the cable[which ever it is]

 Roy*

Sat, 17/10/09@14:30

It's a USB cable

The PC's 4 years old. Hadn't thought of the cable, why could it be that?

Thanks for your help Jack

 Roy*

Mon, 19/10/09@16:24

I've ordered a new cable

So I'll give it a try, could it be anything else?

 jack

Mon, 19/10/09@16:59

Best try one thing at a time

before moving on-
I don't think a duff driver would cause a blue screen.
But to prove this simply delete the printer and install from Windows own library, like this

Go to Start/Printer and Faxes, phen the panel comes up right click delete pn the default printer.
Now move to 'Add Printer'

When that panel comes up ignore ' Have Disk' and go to
'Select from List.
In the left column- select the Printer make = 'Canon'
In the right column scroll down to the model
Click OK
see what happens

 Roy*

Mon, 19/10/09@17:16

OK thanks

Will try new cable when it comes tomorrow (?) until it crashes again or not etc...

 Roy*

Wed, 21/10/09@12:59

OK I've changed the cable but...

It's still crashing. Doesn't crash from laptop with vista when connected with cable?

 jack

Wed, 21/10/09@17:42

OK so its not cable or printer

Try the renistal as above

 Roy*

Wed, 21/10/09@17:45

OK thanks Jack

will do but it'll have to be Thursday night.

 Roy*

Thu, 22/10/09@22:11

OK done the printer reinstal

When I had a look at the drivers installed it has a yes against intel Windows 2000 or XP and a No for the other 5 options. My PC is XP but this printer has shared access for a laptop that runs vista. There is not an option to add additional drivers for vista on the list? The crashes happened before the laptop was here so that is not the cause. Anyway we'll see if it works for a bit?

 Roy*

Wed, 04/11/09@09:26

Any further tips Jack?

Since the printer reinstall it’s been shown as offline from both laptop and desk top PC. When I tried printing last night it crash again (blue screened). I updated drivers again but current status is that the desk top PC thinks the Printer is off line (new cable connected OK). The printer works from laptop if we use a USB cable direct between laptop and printer. So maybe the next course of action is to remove printer and all installed printer software from desktop PC and start again with installation CD?

My only other thought as to why the crashes were happening when it did work, could it be a conflict between Microsoft Office 2003 software as I think it normally crashes when one of those programmes is running (e.g. Outlook, Word, Excel)

Thanks for your help

 Roy*

Fri, 06/11/09@22:11

I've uninstalled all printer software

and deleted it from printer and started again installing it from scratch with CD's etc. but it's still crashing when the printer is on? Any clues people?

 Seth Haniel

Sat, 07/11/09@06:31

click here
'bluescreenofdeath viewer' it shows what was in the stack when PC goes down and helps eliminate the problem

 Roy*

Sat, 07/11/09@09:12

Thanks Seth,

I'll give that a try

 Roy*

Sun, 08/11/09@12:38

Here's what the bluescreen viewer shows

This is a line from dump file many others with similar info any idea what it may be?

Mini110609-02.dmp 06/11/2009 21:16:31 PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xe17ab000 0x00000000 0x82af5798 0x00000001 Ntfs.sys Ntfs.sys+25d63 NT File System Driver Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.5512 (xpsp.080413-2111) 32-bit C:\WINDOWS\minidump\Mini110609-02.dmp


Then it shows the following in the lower window 'filename' not sure what it all means?

Ntfs.sys Ntfs.sys+25d63 0xf82dc000 0xf8368600 0x0008c600 0x48025be5 13/04/2008 19:15:49 Microsoft® Windows® Operating System NT File System Driver 5.1.2600.5512 (xpsp.080413-2111) Microsoft Corporation C:\WINDOWS\system32\drivers\Ntfs.sys

There's around 100 lines like this, can't really postthem on here but I have a screen dump I could email if someone wanted to help?

Any ideas guys?

 Roy*

Sun, 08/11/09@13:08

Registry Easy 5.6

I've seen this scan and repair software which is $40 for teh full version so it apparantly repairs teh problems that causes blue screen crashes? Is this the way to go or is there a another way?

 Seth Haniel

Sun, 08/11/09@13:24

Roy*

make sure Options - Mark drivers found in 'Crash Stack' is ticked
which are the highlighted files in the lower pane as shown on bsd websites top picture?

don't pay out yet for reg editors that probably won't get your problem solved

 Roy*

Sun, 08/11/09@13:28

Thanks Seth

In the lower window the 2 files highlighted are the Ntfs.sys (posted abvove) and ntoskml.exe ?

 Seth Haniel

Sun, 08/11/09@13:30

Roy*

make sure Options - Mark drivers found in 'Crash Stack' is ticked
which are the highlighted files in the lower pane as shown on bsd websites top picture?

don't pay out yet for reg editors that probably won't get your problem solved

Sounds like NTFS.sys could be corrupt
try
Get out an XP CD, and boot from it. Go to Recovery Console, once loaded, get into recovery console by pressing R.
Run chkdsk /r

After that, type CD D:\i386 (assuming D: is cd-rom)
type "copy ntfs.sy_ C:\WINDOWS\system32\drivers\ntfs.sys"

You might need to put C:....ntsy.sys in quotes.

copy ntfs.sy_ "C:\windows\system32\drivesr\ntfs.sys"

For good measure, copy the .\i386 folder to your C: drive. That'll get you around by not needing the XP cd most of the time.

Try Defragging first through. This generally is a pagefile error. Some people have gotten this error with bad memory chips.

 Seth Haniel

Sun, 08/11/09@13:35

Roy*

ntoskml.exe are yuo sure should be ntoskrnl

could be It is a Virus, tries to look like the system file "ntoskrnl.exe". Notice they replaced the "rn" with a "m".

[1] 2 

Total threads 325773 | Total posts 2112113 | Total users 293200

 Forums > Helproom

Back to top