Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Driver IRQL not less or equal


  • Please log in to reply
15 replies to this topic

#1 jwh Bob

jwh Bob

  • Members
  • 71 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Luxembourg
  • Local time:03:12 PM

Posted 12 July 2011 - 03:19 AM

Hi there,

Guess I need your help.


This is on a Vista upgraded to a Windows 7 Home Premium, Intel Core 2 Duo CPU E6550 2,33 Ghz and 2 GB RAM.

The problems started slowly but now it's getting very bad, such as I'm forced to use "save mode" to write this.

The PC is protected by Kaspersky. As read in other threads I did the TDSSkiller as well as the Malwarebytes - nothing found.

Hereafter a "bluescreenview" which, I hope, will help to identify the problem. I understand there's something wrong with ataport.sys but I don't know what to do next

Do thank you for your always kind support

Bob

==================================================
Dump File : 071211-32058-02.dmp
Crash Time : 12/07/2011 09:28:20
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x1c4a76ff
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88dd9e41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\071211-32058-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 152 992
==================================================

==================================================
Dump File : 071211-32058-01.dmp
Crash Time : 12/07/2011 09:00:58
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x247910ff
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88dc3e41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\071211-32058-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 153 088
==================================================

==================================================
Dump File : 071211-24242-01.dmp
Crash Time : 12/07/2011 08:59:12
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x0000000c
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x88dcf171
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+37ab
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+f171
Stack Address 2 : ataport.SYS+f1ac
Stack Address 3 : ataport.SYS+f208
Computer Name :
Full Path : C:\Windows\Minidump\071211-24242-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 152 912
==================================================

==================================================
Dump File : 071111-30404-01.dmp
Crash Time : 11/07/2011 23:02:05
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x23a77153
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88dc1e41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\071111-30404-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 152 992
==================================================

==================================================
Dump File : 071111-22900-01.dmp
Crash Time : 11/07/2011 23:00:23
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x24bd9bbb
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88dc8e41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\071111-22900-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 153 088
==================================================

==================================================
Dump File : 071111-23493-01.dmp
Crash Time : 11/07/2011 22:58:41
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x204d48c4
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88db9e41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\071111-23493-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 152 912
==================================================

==================================================
Dump File : 071011-24242-01.dmp
Crash Time : 10/07/2011 12:04:44
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x21873820
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88dcfe41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\071011-24242-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 153 088
==================================================

==================================================
Dump File : 071011-24445-01.dmp
Crash Time : 10/07/2011 12:02:14
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x20ce022f
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88dc3e41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\071011-24445-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 153 088
==================================================

==================================================
Dump File : 071011-25022-01.dmp
Crash Time : 10/07/2011 12:00:15
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x1c8beb1c
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88dc1e41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\071011-25022-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 152 912
==================================================

==================================================
Dump File : 070511-22885-01.dmp
Crash Time : 05/07/2011 21:12:01
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x20852afc
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88dc0e41
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+a36468
File Description : NVIDIA Windows Kernel Mode Driver, Version 258.96
Product Name : NVIDIA Windows Kernel Mode Driver, Version 258.96
Company : NVIDIA Corporation
File Version : 8.17.12.5896
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\070511-22885-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 153 464
==================================================

==================================================
Dump File : 070511-23712-01.dmp
Crash Time : 05/07/2011 08:57:39
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x1fedb4be
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88db8e41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\070511-23712-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 152 992
==================================================

==================================================
Dump File : 070411-22510-01.dmp
Crash Time : 04/07/2011 22:21:15
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x1e017be0
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88dcde41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\070411-22510-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 152 912
==================================================

==================================================
Dump File : 062111-23493-01.dmp
Crash Time : 21/06/2011 22:47:12
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x1fd4ad97
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88db4e41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\062111-23493-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 152 992
==================================================

==================================================
Dump File : 062011-23290-01.dmp
Crash Time : 20/06/2011 08:51:10
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x1f457249
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88c01e41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\062011-23290-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 153 152
==================================================

==================================================
Dump File : 062011-23992-01.dmp
Crash Time : 20/06/2011 08:49:33
Bug Check String : WORKER_INVALID
Bug Check Code : 0x000000e4
Parameter 1 : 0x00000001
Parameter 2 : 0x85955120
Parameter 3 : 0x00000001
Parameter 4 : 0x00000000
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+184ae
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+def2c
Stack Address 1 : ntkrnlpa.exe+7746f
Stack Address 2 : ntkrnlpa.exe+77444
Stack Address 3 : ntkrnlpa.exe+77415
Computer Name :
Full Path : C:\Windows\Minidump\062011-23992-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 152 912
==================================================

==================================================
Dump File : 061911-23868-01.dmp
Crash Time : 19/06/2011 22:23:58
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x1c5ff8e5
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x88ddde41
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+1e41
File Description : ATAPI Driver Extension
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+415cb
Stack Address 1 : ataport.SYS+1e41
Stack Address 2 : ataport.SYS+a214
Stack Address 3 : ataport.SYS+a677
Computer Name :
Full Path : C:\Windows\Minidump\061911-23868-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 152 912
==================================================

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,627 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:12 AM

Posted 12 July 2011 - 06:50 AM

What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

Please look in device manager - do you see any errors?

Also, please do the following:

1) Open the case and make sure all connections to and from the hd(s) are secure

2) right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

3) To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

Edited by Allan, 12 July 2011 - 06:54 AM.


#3 MarkGS

MarkGS

  • Members
  • 245 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:12 AM

Posted 12 July 2011 - 09:23 AM

In addition to what Allen said, check the MFG website of your computer and update the chipset drivers if there are any available.

#4 jwh Bob

jwh Bob
  • Topic Starter

  • Members
  • 71 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Luxembourg
  • Local time:03:12 PM

Posted 13 July 2011 - 11:04 PM

What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

Please look in device manager - do you see any errors?

Also, please do the following:

1) Open the case and make sure all connections to and from the hd(s) are secure

2) right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

3) To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.


Hi Allan!
Thanks for taking your time.

So what's different? It started maybe a month ago.

At the beginning I didn't realize I had a problem. Usually I start the PC without watching the startup process and return later when the system is up. So sometimes I found a "Windows has recovered from an unexpected shutdown. A problem has caused Windows to stop working correctly. Windows will notify you if a solution is available." At that time I didn't know that a blue screen had happened and misinterpreted the message as that the shutdown before didn't work properly.

As far as I remember this PC was never infected with some kind of a virus.

"Programs and Features" tell me that GoogleEarth was added (must be an update) and also 2 updates for Microsoft Visual CC++ since June.

In Devices and Printers FinePix HS20 is added, but only when I plug that camera, I suppose that's normal. But thinking about, my troubles could have begun when I got that camera, guess it's a coincidence - I didn't install any software which came with it.

Following your instructions I opened the case, checked the connections and cleaned the ventilators. Nothing wrong so far as I could see.

Did the checkdisk, took some time, when I came back the PC was running normally - is there a log somewhere? Since the checkdisk I had no more crashes however.

Memtest, as well as "Windows memory diagnostics" didn't report any problem.

Let's see if this continues in the good way - I'll keep an update here anyway.

Thanks
Bob

#5 jwh Bob

jwh Bob
  • Topic Starter

  • Members
  • 71 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Luxembourg
  • Local time:03:12 PM

Posted 13 July 2011 - 11:13 PM

In addition to what Allen said, check the MFG website of your computer and update the chipset drivers if there are any available.


Hi Mark!

Sorry, but besides "Message From God" I couldn't translate MFG.

Is it about the processor? System says it has an Intel Core 2 Duo CPU E6550 2.33GHz

Or where do I have to look for?

Thanks for your time

Bob

#6 Warped55

Warped55

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:09:12 AM

Posted 14 July 2011 - 12:16 AM

Is "MFG" Manufacturer?
Anyways, no reason to really get panicy, but I had that a while back, and ended up having to replace the HDD. But I'm sure it's not that bad.

#7 Allan

Allan

  • BC Advisor
  • 8,627 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:12 AM

Posted 14 July 2011 - 06:45 AM

jwh Bob - yes, mfg = manufacturer. Have there been any recurrences or is everything running okay now?

#8 jwh Bob

jwh Bob
  • Topic Starter

  • Members
  • 71 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Luxembourg
  • Local time:03:12 PM

Posted 14 July 2011 - 07:20 AM

jwh Bob - yes, mfg = manufacturer. Have there been any recurrences or is everything running okay now?


Thanks Allan, so I'd go to Intel to check for updates? Never did that, so let's see tonite.

Yeaph, unfortunatly I got the blue screen again after I posted. Curiously for me, I had plugged in the camera at that session... I won't plug it anymore and instead use the stick, such the "normal" Windows dialog opens instead the one from Fuji, who knows.

Btw, I always see "Caused By Driver : ataport.SYS" is that a way to look for, although I ignore how...

Thanks and best regards

Bob

Edited by jwh Bob, 14 July 2011 - 07:21 AM.


#9 Allan

Allan

  • BC Advisor
  • 8,627 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:12 AM

Posted 14 July 2011 - 07:45 AM

There are a number of possible causes for the ataport-sys blue screen. Two of those are a problem with the mbr and a rootkit infection (in the mbr).

To address the first, use the /fixboot and /fixmbr commands as outlined in this link: http://support.microsoft.com/kb/927392

As for the second, you can post in the Am I Infected forum on this site and refer back to this thread

#10 jwh Bob

jwh Bob
  • Topic Starter

  • Members
  • 71 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Luxembourg
  • Local time:03:12 PM

Posted 14 July 2011 - 07:56 AM

To address the first, use the /fixboot and /fixmbr commands as outlined in this link: http://support.microsoft.com/kb/927392


Thanks Allan,

Looks like these fixes gonna keep me busy tonite :wink:

#11 Allan

Allan

  • BC Advisor
  • 8,627 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:12 AM

Posted 14 July 2011 - 07:57 AM

No guarantees Bob - it may or may not fix the issue.

#12 jwh Bob

jwh Bob
  • Topic Starter

  • Members
  • 71 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Luxembourg
  • Local time:03:12 PM

Posted 17 July 2011 - 04:14 AM

I'm back,

I followed the instructions given by Microsoft support and I first tried the Startup Repair option in the System Recovery Options dialog box. After that the bootrec.exe with /FixMbr and the /FixBoot.

Then I went to Device Manager where I run one by one the "Update Driver Software". Windows rated them all "up to date" except for the Adapters "NVIDIA GeForce 8600 GTS". Did the update for it, rebooted and found an NVIDIA icon in the "Show hidden icons" which I used to download another driver update (275.33 release 2011.06.01).

During the installation I got a "multiscreen application error": "Samsung Monitor not found". (multiscreen utility came with this Samsung monitor and still works fine after this update). Also, the error message doesn't seem to have done any harm, as NVIDIA now reports that driver version is the latest.

This is what I did so far. Unfortunately, the problem still persists.

More or less at every second boot I get the blue screen, Windows usually works after one automatic reboot, but sometimes it needs two or three reboots.

I should have mentioned that this PC has only this start-up problem, once running all works perfectly.

Still being lost...

Thanks

Bob

#13 Allan

Allan

  • BC Advisor
  • 8,627 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:12 AM

Posted 17 July 2011 - 04:51 AM

Drivers for video, audio, ethernet, modem, etc should be obtained from the oem websites, not from Driver Update in Device Manager or from Windows Update, but okay - that's not the problem at the moment.

The fact that the error is intermittent (every other boot) and even then the system will run well after it does load makes this a difficult issue to diagnose. The only other thought I have is to boot to Windows 7 DVD and run the startup repair options.

Edited by Allan, 17 July 2011 - 04:51 AM.


#14 jwh Bob

jwh Bob
  • Topic Starter

  • Members
  • 71 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Luxembourg
  • Local time:03:12 PM

Posted 18 July 2011 - 02:18 AM

Hi Allen,

As outlined in my previous post I did the Startup repair with booting from the DVD already before running the bootrec.exe
I did it now again, same result:

Startup Repair could not detect a problem.
If you have recently attached a device to this computer, such as a camera... remove it and restart your computer


Is this camera talk a standard reply or specific for this PC? Besides an Epson printer and the cordless Logitech Keyboard & Mouse, which are there since the beginning, there's nothing else attached to it.

As explained earlier, I've connected once a HS20 Fuji camera and this maybe was at the same time the troubles began. I didn't use it afterwards, as I prefer to put the Sandisk directly in the slot of the PC. I didn't install any software which came with the camera nor did I notice that it installed something on the computer - no trace in the Program & Features, is there a place I could check?

Do you think it would be an idea to install the camera's software now? My idea behind this is that the camera could have "half-installed" something and didn't finish as the software CD wasn't there...

Very sorry still bothering you with this.

Bob

#15 Allan

Allan

  • BC Advisor
  • 8,627 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:12 AM

Posted 18 July 2011 - 07:10 AM

First of all, it's not a bother - this is what we're here for. And sorry for regurgitating the Startup Repair option - forgot you already did it.

I honestly don't know what to say at this point. Sure - go ahead and try to reinstall the camera driver / software - what's the harm? While I could be way off base here, the only thing I can think of is a bad cable from the hd - but admittedly that's a longshot. I'm going to ask one of our other Advisors who is more technically knowledgeable on the hw side than I am to take a look at this thread and see if he has any ideas.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users