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

BSOD


  • Please log in to reply
10 replies to this topic

#1 Digifrog

Digifrog

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 04 July 2009 - 11:37 AM

Hello BC'istas :inlove:

New to the forum as I have a problem. First of all, apologies for this being a BSOD topic, I'm sure there are many & I'm sure most, if not all are fed up reading about them.

OK. My bits are...

Windows XP Pro Pro Version 2002 SP3
AMD Athlon XP 2000+ 1.67GHz
768 MB RAM
(quite an old PC (7 years old) by most modern standards)

The problem is Stop Error screens. They usually occur when I am in Photoshop (and/or associated plug-ins) working away, crashing whilst half way thru a workflow. One has also happened whilst running a full system scan with Norton AV 2009, and once whilst running a full system scan with AdAware 2008. Seems when a lot of memory is being used my PC dies. Odd then that I have had a BSOD whilst watching a Youtube vid and once whilst logged into my Myspace account. Other general PC use and web browsing are by large unaffected. What can it be? Hardware or software?

The BSOD displays...

While in Photoshop (Nik plugin) :flowers:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x000000D1 (0xF7952F41, 0x00000002, 0x00000001, 0xF7110970)
nv4 mini.sys says: Address F7110970 base at F70EE000, datestamp 40746958

While running system scan with Norton AV 2009 :trumpet:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x0000007F (0x0000000D, 0x00000000, 0x00000000)

I have not uninstalled newly added two Ps plugins, though most of this started happening after installing them. Unless I know it is this that is causing the failure or whether it is a hardware issue? I'm not that technically knowledged so any help or advice would be appreciated. :thumbsup:

Many thanks

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,274 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:37 PM

Posted 04 July 2009 - 03:03 PM

Not necessarily applicable, but worth reading: http://support.microsoft.com/default.aspx?...kb;en-us;902973

FWIW: If Photoshop crashes...my guess would be that you don't have enough RAM for it at those times it crashes.

You could also try uninstalling/reinstalling your video drivers...nv4mini.sys is a video driver.

I suspect that the other error message is also related to the video driver.

Louis

#3 Digifrog

Digifrog
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 04 July 2009 - 03:59 PM

Not necessarily applicable, but worth reading: http://support.microsoft.com/default.aspx?...kb;en-us;902973

FWIW: If Photoshop crashes...my guess would be that you don't have enough RAM for it at those times it crashes.

You could also try uninstalling/reinstalling your video drivers...nv4mini.sys is a video driver.

I suspect that the other error message is also related to the video driver.

Louis


Thank you Louis

I reformatted my PC about 3 months ago and this has only started happening in the last few weeks. Funnily enough my PC blue screened just (with the same Stop Error Msg (roughly)) while the PC was in screensaver mode or power save mode, (I was away so not sure which)

It's not Ps that crashes per se, more the system does. It just happens while I'm in Ps. Not sure if its the same thing. Ps has crashed before once, but that was just a freeze up, not a system crash blue screen.

Please forgive my naivity. How do I uninstall/reinstall a video driver? (I only know how to uninstall/reinstall something if it is in Add/Remove Programs.) :thumbsup:

I have read this...
http://www.file.net/process/nv4_mini.sys.html

...what would you suggest?

Thank you

Scott

#4 Digifrog

Digifrog
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 04 July 2009 - 04:42 PM

I opened Eventvwr, this is what I found.

Application: No relevent errors
Security: No items shown
System: One error that happened at a time I recognize as a time I recieved a BSOD. Text=

Error: Service Control Manager.
The General Purpose USB Driver (adildr.sys) service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

There is a host of errors in this section, it seems ALL Service Control Manager error msgs relate to adildr.sys. I couldn't actually find one that relates to nv4_mini :thumbsup:

I noticed also some Information Save Dump entries. They are (and possibly relevent to my bsods (??) as they contain those hexidecimals I see on the blue screens)

1. 04/07/2009 (Event ID 1001)
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0xf7952f41, 0x00000002, 0x00000001, 0xf7110970). A dump was saved in: C:\WINDOWS\Minidump\Mini070409-02.dmp

2. 04/07/2009 (Event ID 1001)
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0xf7952f41, 0x00000002, 0x00000001, 0xf7110970). A dump was saved in: C:\WINDOWS\Minidump\Mini070409-01.dmp.

3. 02/07/2009 (Event ID 1001)
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000000, 0x000000ff, 0x00000001, 0x77c47637). A dump was saved in: C:\WINDOWS\Minidump\Mini070209-02.dmp.

4. 02/07/2009 (Event ID 1001)
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0xf7952f41, 0x00000002, 0x00000001, 0xf7110970). A dump was saved in: C:\WINDOWS\Minidump\Mini070209-01.dmp

5. 01/07/2009 (Event ID 1001)
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x0000000d, 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini070109-03.dmp.

6. 01/07/2009 (Event ID 1001)
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0xf7952f41, 0x00000002, 0x00000001, 0xf7110970). A dump was saved in: C:\WINDOWS\Minidump\Mini070109-02.dmp.

7. 01/07/2009 (Event ID 1001)
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x44ca24f8, 0x00000002, 0x00000000, 0xf7110971). A dump was saved in: C:\WINDOWS\Minidump\Mini070109-01.dmp.

8. 30/06/2009 (Event ID 1001)
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0xf7952f41, 0x00000002, 0x00000001, 0xf7110970). A dump was saved in: C:\WINDOWS\Minidump\Mini063009-01.dmp.

9. 23/06/2009 (Event ID 1001)
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xfc98ce60, 0x00000000, 0xbf80550b, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini062309-01.dmp.

These are ALL the Save Dump entries in this section. It appears the problem started on the 23rd June. :flowers:

Kind regards

Scott

Edited by Digifrog, 04 July 2009 - 04:48 PM.


#5 hamluis

hamluis

    Moderator


  • Moderator
  • 56,274 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:37 PM

Posted 04 July 2009 - 06:11 PM

Uninstall the current driver first (using Device Manager)...then install a new one.

Device Manager Basics - http://www.cybertechhelp.com/tutorial/arti...-manager-basics

How to update a Windows hardware driver - http://www.bleepingcomputer.com/tutorials/how-to-update-a-windows-hardware-driver/

If you need more detail, please use Google to clarify/add info...there's a wealth of informational detail available on the Web re such tasks.

Louis

You have a ton of errors for 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL. You might take a look at the info re such at http://www.aumha.org/a/stop.htm

You might also take a look at 0x10000050 errors at the same link.

As you can see, neither of these is very easy to troubleshoot.

But...you can also use the following procedure to run those last two .dmp messages and post the results here: Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

Edited by hamluis, 04 July 2009 - 06:18 PM.


#6 Digifrog

Digifrog
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 05 July 2009 - 07:22 AM

Thank you Louis

I followed the procedure for the Windows Debugger and have "Copied Window Text To Clipboard". Before I do, simple question. If I uninstall the driver in Device Manager for Display Adapters>NVIDEA GeForce3 Ti200, where do I get a new driver? (current driver is 5.6.7.3)

OK, the Debug Analysis Info is (I have chosen 3 randomly picked dmp's)

Minidump 1.

Microsoft Windows Debugger Version 6.11.0001.404 X86
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini070109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Wed Jul 1 16:54:31.156 2009 (GMT+1)
System Uptime: 0 days 0:54:25.703
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {44ca24f8, 2, 0, f7110971}

Probably caused by : nv4_mini.sys ( nv4_mini!odbDefaultDestructObject+41 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 44ca24f8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f7110971, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: 44ca24f8

CURRENT_IRQL: 2

FAULTING_IP:
nv4_mini!odbDefaultDestructObject+41
f7110971 e84a230000 call nv4_mini!pdbGetProperty (f7112cc0)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Photoshop.exe

LAST_CONTROL_TRANSFER: from f7120c4c to f7110971

STACK_TEXT:
f794aeb4 f7120c4c 82ca2490 00000024 82e06c50 nv4_mini!odbDefaultDestructObject+0x41
f794aec8 f714a897 82e06c50 82ca2490 006013d4 nv4_mini!osGpuReadReg008+0xc
f794aee0 f7134d51 82ca2490 006013d4 82b8a000 nv4_mini!notifyBufferHWComplete+0xdb7
f794aefc f7154596 82b8a000 f794af2c f794afa0 nv4_mini!dacSynchronizeCRTCAccessWithVBIOS+0x131
f794afa0 f7122231 82ca2490 82f88388 82e70768 nv4_mini!objMcService+0xc6
f794afc0 f70db2ca 82ea3350 82b8a000 ffdff980 nv4_mini!RmDpcForIsr+0xd1
f794afd0 804dbbd4 82ea3240 82ea3350 f7122160 VIDEOPRT!pVideoPortDpcDispatcher+0xe
f794aff4 804db89e f4573d44 00000000 00000000 nt!KiRetireDpcList+0x46
f794aff8 f4573d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
804db89e 00000000 00000009 bb835675 00000128 0xf4573d44


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini!odbDefaultDestructObject+41
f7110971 e84a230000 call nv4_mini!pdbGetProperty (f7112cc0)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini!odbDefaultDestructObject+41

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4074b958

FAILURE_BUCKET_ID: 0xD1_nv4_mini!odbDefaultDestructObject+41

BUCKET_ID: 0xD1_nv4_mini!odbDefaultDestructObject+41

Followup: MachineOwner
---------

===============================================

Minidump 2.


Microsoft Windows Debugger Version 6.11.0001.404 X86
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini070409-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Jul 4 21:04:54.625 2009 (GMT+1)
System Uptime: 0 days 2:57:54.187
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {f7952f41, 2, 1, f7110970}

Probably caused by : nv4_mini.sys ( nv4_mini!odbDefaultDestructObject+40 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: f7952f41, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f7110970, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: f7952f41

CURRENT_IRQL: 2

FAULTING_IP:
nv4_mini!odbDefaultDestructObject+40
f7110970 50 push eax

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: ccSvcHst.exe

LAST_CONTROL_TRANSFER: from f7120c4c to f7110970

STACK_TEXT:
f794aeb4 f7120c4c 82d60a08 00000024 82c814b8 nv4_mini!odbDefaultDestructObject+0x40
f794aec8 f714a897 82c814b8 82d60a08 006013d4 nv4_mini!osGpuReadReg008+0xc
f794aee0 f7134d51 82d60a08 006013d4 82b81000 nv4_mini!notifyBufferHWComplete+0xdb7
f794aefc f7154596 82b81000 f794af2c f794afa0 nv4_mini!dacSynchronizeCRTCAccessWithVBIOS+0x131
f794afa0 f7122231 82d60a08 82c7fec0 82d6d138 nv4_mini!objMcService+0xc6
f794afc0 f6f842ca 82d3d350 82b81000 ffdff980 nv4_mini!RmDpcForIsr+0xd1
f794afd0 804dbbd4 82d3d240 82d3d350 f7122160 VIDEOPRT!pVideoPortDpcDispatcher+0xe
f794aff4 804db89e f08bed44 00000000 00000000 nt!KiRetireDpcList+0x46
f794aff8 f08bed44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
804db89e 00000000 00000009 bb835675 00000128 0xf08bed44


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini!odbDefaultDestructObject+40
f7110970 50 push eax

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini!odbDefaultDestructObject+40

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4074b958

FAILURE_BUCKET_ID: 0xD1_nv4_mini!odbDefaultDestructObject+40

BUCKET_ID: 0xD1_nv4_mini!odbDefaultDestructObject+40

Followup: MachineOwner
---------

==============================================

Minidump 3.


Microsoft Windows Debugger Version 6.11.0001.404 X86
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini070209-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Thu Jul 2 13:11:49.687 2009 (GMT+1)
System Uptime: 0 days 1:54:23.234
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {f7952f41, 2, 1, f7110970}

Probably caused by : nv4_mini.sys ( nv4_mini!odbDefaultDestructObject+40 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: f7952f41, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f7110970, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: f7952f41

CURRENT_IRQL: 2

FAULTING_IP:
nv4_mini!odbDefaultDestructObject+40
f7110970 50 push eax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Photoshop.exe

LAST_CONTROL_TRANSFER: from f7120c4c to f7110970

STACK_TEXT:
f794aeb4 f7120c4c 82cab9a0 00000024 82d930d8 nv4_mini!odbDefaultDestructObject+0x40
f794aec8 f714a897 82d930d8 82cab9a0 006013d4 nv4_mini!osGpuReadReg008+0xc
f794aee0 f7134d51 82cab9a0 006013d4 82b84000 nv4_mini!notifyBufferHWComplete+0xdb7
f794aefc f7154596 82b84000 f794af2c f794afa0 nv4_mini!dacSynchronizeCRTCAccessWithVBIOS+0x131
f794afa0 f7122231 82cab9a0 82ce1710 82da0c78 nv4_mini!objMcService+0xc6
f794afc0 f70db2ca 82e56350 82b84000 ffdff980 nv4_mini!RmDpcForIsr+0xd1
f794afd0 804dbbd4 82e56240 82e56350 f7122160 VIDEOPRT!pVideoPortDpcDispatcher+0xe
f794aff4 804db89e f3912d44 00000000 00000000 nt!KiRetireDpcList+0x46
f794aff8 f3912d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
804db89e 00000000 00000009 bb835675 00000128 0xf3912d44


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini!odbDefaultDestructObject+40
f7110970 50 push eax

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini!odbDefaultDestructObject+40

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4074b958

FAILURE_BUCKET_ID: 0xD1_nv4_mini!odbDefaultDestructObject+40

BUCKET_ID: 0xD1_nv4_mini!odbDefaultDestructObject+40

Followup: MachineOwner
---------

Rgds

Scott

Edited by Digifrog, 05 July 2009 - 08:04 AM.


#7 hamluis

hamluis

    Moderator


  • Moderator
  • 56,274 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:37 PM

Posted 05 July 2009 - 11:09 AM

<<If I uninstall the driver in Device Manager for Display Adapters>NVIDEA GeForce3 Ti200, where do I get a new driver? (current driver is 5.6.7.3)>>

XP has a driver cache, it may automatically load the driver when it boots up.

If not, the CD which accompanied the system purchase...has known working drivers on it.

This is changing...but the website of the system or motherboard manufacturer is still the best place to check for drivers when not using the original CD.

Photoshop crashes...check for updates and address failure to meet memory needs. If you don't have XP managing your virtual memory...let it do so.

Louis

#8 Digifrog

Digifrog
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 05 July 2009 - 03:56 PM

Louis thank you.

OK, I uninstalled the driver in Device Manager and restarted the PC. I am guessing XP has reinstalled the driver upon restart as the 5.6.7.3 driver has reinstalled. In short, not a new driver but the same one.

From the debug info above, what is being stated in laymans terms?

I have happily been using Ps for several months now without incident, why has my system suddenly decided to BS on a regular basis? I have ran full system scans with Norton 2009 without incident in the past, why did my system BS the last time I ran a virus check?

Something tells me that Ps isn't the issue, rather there is a systemic error bought on by something else. (?)

Despite uninstalling and reinstalling the video driver, I am 'frightened' of working normally in Ps, or running a virus scan just in case the same thing happens again, meaning the original hunch was the incorrect assumption. As a dedicated photographer I cannot bear to be without Ps. :thumbsup:

I will test the steps we have taken so far by running a full virus scan, and by doing some Ps work to see if I am free of the BSOD, tho I am not hopeful.

Many thanks again

Rgds

Scott

#9 hamluis

hamluis

    Moderator


  • Moderator
  • 56,274 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:37 PM

Posted 05 July 2009 - 04:13 PM

Minidump1: BugCheck 100000D1 = STOP error 1000000D1. Probably caused by : nv4_mini.sys (video driver). PROCESS_NAME: Photoshop.exe, I interpret this to mean that you were in Photoshop when STOP error occurred.

Minidump2: Same as #1, except that it was the PROCESS_NAME: ccSvcHst.exe (it was your Symantec product, rather than Adobe Phototshop. You want to read possible reasons why, http://www.instant-registry-fixes.org/how-...stexe-problems/ . Don't buy or download anything, just read their summary data on this error.

Minidump3: Same #1.

FWIW: It doesn't matter that the same driver was installed...what matters is that it's a fresh copy of that driver, as opposed to an impaired/damaged copy that may be responsible for your BSODs.

Louis

#10 Digifrog

Digifrog
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:37 PM

Posted 10 July 2009 - 06:11 PM

Thank you Luis

Well, after uninstalling the driver and puting a 'fresh' one in I thought the problem had passed. PC was pretty much behaving itself, used Ps earlier without any problems & ran a full system virus scan yesterday without incident. But while I was watching a Youtube vid earlier tonight this happened,


Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071009-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Fri Jul 10 23:53:13.640 2009 (GMT+1)
System Uptime: 0 days 3:16:26.203
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {f7952f41, 2, 1, f7110970}

Probably caused by : nv4_mini.sys ( nv4_mini!odbDefaultDestructObject+40 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: f7952f41, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f7110970, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: f7952f41

CURRENT_IRQL: 2

FAULTING_IP:
nv4_mini!odbDefaultDestructObject+40
f7110970 50 push eax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from f7120c4c to f7110970

STACK_TEXT:
f794aeb4 f7120c4c 82dba0c8 00000024 82e57c50 nv4_mini!odbDefaultDestructObject+0x40
f794aec8 f714a897 82e57c50 82dba0c8 006013d4 nv4_mini!osGpuReadReg008+0xc
f794aee0 f7134d51 82dba0c8 006013d4 82ba4000 nv4_mini!notifyBufferHWComplete+0xdb7
f794aefc f7154596 82ba4000 f794af2c f794afa0 nv4_mini!dacSynchronizeCRTCAccessWithVBIOS+0x131
f794afa0 f7122231 82dba0c8 82c9e590 82e649e8 nv4_mini!objMcService+0xc6
f794afc0 f70db2ca 82e72350 82ba4000 ffdff980 nv4_mini!RmDpcForIsr+0xd1
f794afd0 804dbbd4 82e72240 82e72350 f7122160 VIDEOPRT!pVideoPortDpcDispatcher+0xe
f794aff4 804db89e f2fa6d44 00000000 00000000 nt!KiRetireDpcList+0x46
f794aff8 f2fa6d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
804db89e 00000000 00000009 bb835675 00000128 0xf2fa6d44


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini!odbDefaultDestructObject+40
f7110970 50 push eax

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini!odbDefaultDestructObject+40

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4074b958

FAILURE_BUCKET_ID: 0xD1_nv4_mini!odbDefaultDestructObject+40

BUCKET_ID: 0xD1_nv4_mini!odbDefaultDestructObject+40

Followup: MachineOwner
---------

As it's happened again (on a new driver) what is going on? It's not as if watching a Youtube vid can cause that much upset is there? The only thing I can think of is maybe a Ps plugin is damaging the driver leaving it vulnerable, or my graphics card is dying, or I have a virus (which I'm doubtful as one didn't show on the full system virus scan with Norton 2009)

Any advice would be helpful. Thank you.

Rgds

Scott

#11 hamluis

hamluis

    Moderator


  • Moderator
  • 56,274 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:37 PM

Posted 10 July 2009 - 06:45 PM

Unfortunately...I have no clue.

I suppose that troubleshooting BSODs can have a scientific approach/result...but I find much of it (as suggested by most guidance on such) to just be trial-and-error elimination of possible causes.

Have you taken a look in Event Viewer for possible clues?

Is your system adequately protected from malware?

Have you tried running a chkdsk /r on the system partition?

Louis

Edit: The problem with a system that is 7 years old...is that it's 7 years old and anything might be taking place. I'm not the same person physically that I was 7 years ago and I wouldn't expect my system to be in the same functional condition :thumbsup:.

Edited by hamluis, 10 July 2009 - 06:48 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users