Please help: Computer restarts when trying to print

T

tonybagadonuts

New Member
One of the computers in my office keeps rebooting to the safe mode option when trying to print. The print job is coming from Quickbooks, but I don't think that is the root of the issue. The printer is a b&w Brother HL-2070N laser printer and has been set up on the same computer for over a year. The desktop computer is running Vista Home Basic. The problem just started and I don't know where to start. I haven't found anything online that relates to my issue yet, so if you can help it would be greatly appreciated.

Thanks,

Tony
 

My Computer

System One

tonybagadonuts said:
One of the computers in my office keeps rebooting to the safe mode option when trying to print. The print job is coming from Quickbooks, but I don't think that is the root of the issue. The printer is a b&w Brother HL-2070N laser printer and has been set up on the same computer for over a year. The desktop computer is running Vista Home Basic. The problem just started and I don't know where to start. I haven't found anything online that relates to my issue yet, so if you can help it would be greatly appreciated.

Thanks,

Tony
Click to expand...

Use the document View attachment Print Spooler.pdf to delete your printer drivers, And add the printer again.

Let me know the result :)
 

My Computer

System One

  • Manufacturer/Model
    Wipro
    Motherboard
    Intel dq35j0
    Memory
    8 Gb
    Graphics card(s)
    inter express chipset
    Sound Card
    Realtek
    Monitor(s) Displays
    Wipro
    Screen Resolution
    1024*768
    Hard Drives
    500 gb
    Mouse
    Dell
    Keyboard
    DELL
    Internet Speed
    100 mbps(office lan)
You mean it automagically reboots whenever you try to print, and then you see the dialog box asking you whether you'd like to go into safe mode?

If that's the case, you may see some recent files with a DMP extension in the \windows\minidump folder on that machine - one for each of the reboots. They're memory dumps each corresponding to one crash/reboot sequence.

If you copy a few of the latest DMPs out of that folder and into another directory, then zip them up and upload them here, someone might be able to analyse them for you and tell you precisely why the machine is crashing and rebooting.
 

My Computer

System One

I'll be more than happy to analyze them for you- I have a special program. As H2SO4 said, copy them to a folder, zip them, and upload them. I'll try my best.

Good luck,
RFCA
 

My Computer

System One

  • Manufacturer/Model
    Apple MacBook Pro 13inch
    CPU
    Intel Core 2 Duo @ 2.26GHz
    Motherboard
    ?
    Memory
    2GB DDR3 RAM
    Graphics card(s)
    NVIDIA GeForce 9400M @256MB Dedicated DDR3 VRAM
    Sound Card
    Intel High Definition Audio
    Monitor(s) Displays
    Laptop: 32 bit Color LCD
    Screen Resolution
    1280x800
    Hard Drives
    HITACHI HTS545025B9SA02 250GB (Internal) IOMEGA PRESTIGE PORTABLE 500GB (External)
    PSU
    N/A
    Case
    N/A
    Cooling
    N/A
    Mouse
    No-Button Aluminum Trackpad w/ Mouse Gestures
    Keyboard
    Black Chiclet-Style Keyboard (Standard US) with Backlight
    Internet Speed
    T1
First, I want to thank all 3 of you for your reply. Delphin, I plan on trying your method if the other way doesn't help determine the problem.

I wasn't familiar with a dmp file, but looked into it after being unable to find it under /windows/... I went into my advanced settings in the control panel, and it looks like it was doing a "kernel" type of file instead of a "minidump". This is why I don't think I have any dmp files to work with just yet. It states that the kernel method saves and replaces the previous file as opposed to creating a file for each failure, so I am guessing there is just one. The only file I could find created today was a dat file that I attached.

I changed it to create minidump files moving forward. As the computer does not crash every single time we print, I am hoping to get it to do so again and will repost the dmp data files.
 

Attachments

My Computer

System One

Good researching there. However, it should be creating minidumps along the full "kernel" dumps (which are hundreds of MB in size and therefore impractical for our purposes here). The fact that there's no minidump suggests one of a few possibilities:

1) A kernel dump is not generated because the OS lacks a sufficiently large pagefile on the OS boot partition - the one with the \windows folder on it. Since minidumps are technically "extracted" from a full dump, there's nothing to extract from and no minidump is created. Make sure there's a pagefile on the boot partition that's at least 500MB in size, and preferably 1GB.

2) The reboot is due to a bugcheck (bluescreen) which affects some portion of the OS responsible for disk writing, and no dump is generated. This is possible but unlikely in your scenario. Try unticking the "automatically reboot" option in Control Panel, system, "advanced" tab, startup and recovery options, settings... same place you found the kernel dump settings. If it still reboots after that, unfortunately the last possibility becomes more likely...

3) It's actually a hardware fault. The act of attempting to print trips over some underlying hardware glitch and causes a spontaneous reboot. That's fundamentally different to a bluescreen so no dump is generated. I wouldn't have thought this likely, but it is possible. Try moving the printer around to a different USB port perhaps, just to test what happens.
 

My Computer

System One

You must log in or register to reply here.
Back
Top