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

Stop Error, Bugcheck, Etc.


  • Please log in to reply
18 replies to this topic

#1 David S

David S

  • Members
  • 43 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:07 PM

Posted 03 February 2007 - 01:48 PM

To all,
My computer crashes/reboots almost every morning. It always fixes itself, eventually.
I get the BSoD with something written on it. I cannot read it because the font is messed-up.
I have been searching the web and asking people about a solution, now I found you.

The original error was "the BIOS system version on this computer does not match the specifications for the CPU". So I updated the BIOS version. I got locked out of the computer. A co-worker helped me with this but, I cannot use my wireless keyboard to access the BIOS anymore. There is no power to the USB port until its too late.

The new error is a Stop Error with the same code as 5 or 6 other people on this site.
It passed the first two hard drive tests from WINDLG. The third test has the possibility of losing info from the computer so I didn't do it. Before I run the memtest86, I'll ask you.

The microsoft camera (mscamsvc) was the most recent install before the original problem. I uninstalled it, but parts of it are still in there somewhere, I guess.

It also has other errors as shown below from the event viewer.

Where do I start?

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1000
Date: 1/27/2007
Time: 8:33:12 AM
User: N/A
Computer: STARKS
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000). A full dump was not saved.
************************************************************************
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 1/27/2007
Time: 8:38:06 AM
User: N/A
Computer: STARKS
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x00000008, 0xf8a0fd70, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.
************************************************************************
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 1/27/2007
Time: 8:42:59 AM
User: N/A
Computer: STARKS
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.
******************************************************************************
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 1/27/2007
Time: 8:46:27 AM
User: N/A
Computer: STARKS
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x00000008, 0xf8a0fd70, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.
************************************************************************
Event Type: Information
Event Source: redbook
Event Category: None
Event ID: 10
Date: 1/27/2007
Time: 8:46:04 AM
User: N/A
Computer: STARKS
Description:
This drive has not been shown to support digital audio playback.

Data:
0000: ff 00 04 00 01 00 5c 00 .....\.
0008: 00 00 00 00 0a 00 ff 4f ......O
0010: 00 00 00 00 00 00 00 00 ........
0018: 01 00 00 00 ff ff ff ff ....
0020: 00 00 00 00 00 00 00 00 ........
0028: 01 00 00 00 ....
************************************************************************
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 1/27/2007
Time: 8:46:42 AM
User: N/A
Computer: STARKS
Description:
The MSCamSvc service failed to start due to the following error:
The system cannot find the file specified.
***************************************************************************
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/27/2007
Time: 8:53:58 AM
User: N/A
Computer: STARKS
Description:
Error code 1000007f, parameter1 00000008, parameter2 f8a0fd70, parameter3 00000000, parameter4 00000000.

Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 37 1000007
0020: 66 20 20 50 61 72 61 6d f Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 38 2c 20 000008,
0038: 66 38 61 30 66 64 37 30 f8a0fd70
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000
************************************************************************
Event Type: Warning
Event Source: Tcpip
Event Category: None
Event ID: 4226
Date: 1/27/2007
Time: 11:40:25 AM
User: N/A
Computer: STARKS
Description:
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Data:
0000: 00 00 00 00 01 00 54 00 ......T.
0008: 00 00 00 00 82 10 00 80 ......
0010: 01 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
************************************************************************

BC AdBot (Login to Remove)

 


m

#2 Albert Frankenstein

Albert Frankenstein

  • Members
  • 2,707 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Michigan, USA
  • Local time:03:07 PM

Posted 03 February 2007 - 06:25 PM

I'm leaning toward a hardware problem. Let's start with the easiest to test, the RAM.

If there are two pieces of RAM you could always remove one and see if this issue persists. If it does, swap the pieces and try again. This would identify which piece of RAM is defective, if any.

To test the memory:

Microsoft Memory Diagnostic
Memtest86
ALBERT FRANKENSTEIN
I'M SO SMART IT'S SCARY!


Currently home chillin' with the fam and my two dogs!


#3 Monty007

Monty007

  • Members
  • 1,151 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:04:37 AM

Posted 03 February 2007 - 07:30 PM

Hi david, I let Albert take this one but to stop the reboot process go to start>right click My Computer> properties>advanced>startup and recovery and untick automatically restart.
MCP
MSDST

#4 _Peter_

_Peter_

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:02:07 PM

Posted 03 February 2007 - 10:17 PM

Hey David,

Try this.

Go to
-Start,
-Click Run
-Type: "services.msc /s" and press enter
-and look for a service called MSCamSvc
-when and if you find MSCamSvc, right click on it, and click Properties at the bottom of the menu
-look for where it says "Startup Type:" and set that option to "Disabled"

I think this will disable the remaining part of that camera program that wasn't uninstalled.

Here's some background info. It looks like that Microsoft Camera thingy is what's causing the problem. There's an error in your event log that says...

"The MSCamSvc service failed to start due to the following error: The system cannot find the file specified. "

Which is understandable since you uninstalled the program, but for some reason windows keeps trying to restart the service that the program provided and it's causing an error because the executable file for that service was uninstalled. Most likely there's still entries in the registry for the program.

#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:07 PM

Posted 04 February 2007 - 07:46 PM

A dump was saved in: C:\WINDOWS\MEMORY.DMP


Use this link to analyze the above file, then copy/paste the results in your next post. We can move on from there.

FYI - here's a link to the error message: http://aumha.org/win5/kbestop.php#0x7f

As Albert has stated - this is most commonly a hardware problem. Here's an article that goes into a bit more detail: http://support.microsoft.com/?kbid=137539&sd=RMVP
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#6 David S

David S
  • Topic Starter

  • Members
  • 43 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:07 PM

Posted 04 February 2007 - 09:45 PM

To Albert,
I did this test approx 2 weeks ago. No difference it still had the same BSoD.
I'll have to read the instructions for the memtest86 again, I'm no too comfortable with it yet. The microsoft test requires a disc which I don't have.

To Monty,
I unchecked it, restarted it this morning got the same illegible BSoD and it fixed itself as usual.

To Peter,
What your saying makes sense because of what the event viewer says but, I ran "services.msc /s", it found nothing close to mscamsvc.

To USASMA,
The memory.dmp file is over 520M. Don't know what this means but when I try to open it, I have to use the task manager to stop it.

I noticed that I know less than I thought with regards to the guts of a computer, but I'm willing to learn. Also, I'm not trying to play stump the techs. Thank you all for your help. What's next?
David

#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:07 PM

Posted 05 February 2007 - 07:38 AM

A full memory dump is generally the size of your RAM (I've got 4 gB, so it's even worse for me).

If the Debugging tools lock up when you're trying to analyze the dump file, then I'd suggest either trying this free utility: http://windowsbbs.com/debugwiz.zip (from this post at another forum: http://www.windowsbbs.com/showthread.php?t...ghlight=dumpwiz )

Or, changing your settings to make the next dump smaller. Go to Start...Run...and type in "sysdm.cpl". Click on the Advanced tab, then on the Startup and Recovery Settings button. On the next page, near the bottom will be a dropdown box to select the size of the dump file that is written - select the "Small memory dump". If it's already selected, then search your hard drive for other, smaller dump files.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#8 David S

David S
  • Topic Starter

  • Members
  • 43 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:07 PM

Posted 05 February 2007 - 10:32 PM

John,

I ran the debugwiz. Not sure if I did it correctly. See below:

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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is 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 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Mon Feb 5 06:33:11.875 2007 (GMT-5)
System Uptime: 0 days 0:02:10.578
WARNING: Process directory table base 1061F000 doesn't match CR3 00039000
WARNING: Process directory table base 1061F000 doesn't match CR3 00039000
Loading Kernel Symbols
.......................................................................................................................
Loading User Symbols
...........................
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80042000, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
Probably caused by : nv4_mini.sys ( nv4_mini+3fad3 )

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

#9 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:07 PM

Posted 06 February 2007 - 07:43 AM

It appears to be a problem with your video drivers (nv4_mini.sys). The first thing to do is:

Download the latest drivers from http://www.nvidia.com/
Uninstall the old drivers
Install the one's that you downloaded
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#10 David S

David S
  • Topic Starter

  • Members
  • 43 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:07 PM

Posted 07 February 2007 - 07:12 PM

Loaded the new drivers. It still had the BSoD.

I must have left some stuff out the last time.

Is there a way to send the whole file as an attachment?

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Feb 7 06:12:08.796 2007 (GMT-5)
System Uptime: 0 days 0:02:10.484
WARNING: Process directory table base 0F1F2000 doesn't match CR3 00039000
WARNING: Process directory table base 0F1F2000 doesn't match CR3 00039000
Loading Kernel Symbols
.......................................................................................................................
Loading User Symbols
...........................
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, f8a0fd70, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
Probably caused by : nv4_mini.sys ( nv4_mini+3fad3 )

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

1: kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: f8a0fd70
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_8

TSS: 00000028 -- (.tss 28)
.tss 28
eax=00000000 ebx=82c1db58 ecx=f8ba406c edx=82c1d898 esi=00000008 edi=00000001
eip=f773bad3 esp=f8ba4000 ebp=00000001 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nv4_mini+0x3fad3:
f773bad3 e878ffffff call nv4_mini+0x3fa50 (f773ba50)
.trap
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: logonui.exe

LAST_CONTROL_TRANSFER: from f773bb26 to f773bad3

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f8ba4018 f773bb26 82b6a008 00000008 82b6a008 nv4_mini+0x3fad3
00000000 00000000 00000000 00000000 00000000 nv4_mini+0x3fb26


STACK_COMMAND: .tss 0x28 ; kb

FOLLOWUP_IP:
nv4_mini+3fad3
f773bad3 e878ffffff call nv4_mini+0x3fa50 (f773ba50)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini+3fad3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 453bddb2

FAILURE_BUCKET_ID: 0x7f_8_nv4_mini+3fad3

BUCKET_ID: 0x7f_8_nv4_mini+3fad3

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

eax=f8a0f13c ebx=f8a0fd70 ecx=00000000 edx=00000000 esi=00000000 edi=00000000
eip=804df8e9 esp=f8a13144 ebp=00000000 iopl=0 nv up di ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000086
nt!KiTrap08+0x48:
804df8e9 ebee jmp nt!KiTrap08+0x38 (804df8d9)
ChildEBP RetAddr Args to Child
00000000 f773bad3 00000000 00000000 00000000 nt!KiTrap08+0x48 (FPO: TSS 28:0)
WARNING: Stack unwind information not available. Following frames may be wrong.
f8ba4018 f773bb26 82b6a008 00000008 82b6a008 nv4_mini+0x3fad3
00000000 00000000 00000000 00000000 00000000 nv4_mini+0x3fb26
start end module name
01000000 01090000 logonui logonui.exe Wed Aug 04 02:02:57 2004 (41107C11)
5ad70000 5ada8000 UxTheme UxTheme.dll Wed Aug 04 03:56:43 2004 (411096BB)
5b860000 5b8b4000 NETAPI32 NETAPI32.dll Thu Aug 17 08:28:27 2006 (44E460EB)
5cb70000 5cb96000 ShimEng ShimEng.dll Wed Aug 04 03:56:42 2004 (411096BA)
6c1b0000 6c1fd000 DUSER DUSER.dll Wed Aug 04 03:56:04 2004 (41109694)
6f880000 6fa4a000 AcGenral AcGenral.DLL Wed Aug 04 03:55:58 2004 (4110968E)
74c80000 74cac000 OLEACC OLEACC.dll Sat Aug 18 01:33:18 2001 (3B7DFE1E)
755c0000 755ee000 msctfime msctfime.ime Wed Aug 04 03:57:31 2004 (411096EB)
76080000 760e5000 MSVCP60 MSVCP60.dll Wed Aug 04 03:59:13 2004 (41109751)
76380000 76385000 MSIMG32 MSIMG32.dll Wed Aug 04 03:58:31 2004 (41109727)
76390000 763ad000 IMM32 IMM32.DLL Wed Aug 04 03:56:30 2004 (411096AE)
769c0000 76a73000 USERENV USERENV.dll Wed Aug 04 03:56:41 2004 (411096B9)
76b40000 76b6d000 WINMM WINMM.dll Wed Aug 04 03:57:10 2004 (411096D6)
77120000 771ac000 OLEAUT32 OLEAUT32.dll Wed Aug 04 03:57:39 2004 (411096F3)
773d0000 774d3000 COMCTL32 COMCTL32.dll Fri Aug 25 11:45:55 2006 (44EF1B33)
774e0000 7761d000 ole32 ole32.dll Tue Jul 26 00:39:47 2005 (42E5BE93)
77be0000 77bf5000 MSACM32 MSACM32.dll Wed Aug 04 03:57:03 2004 (411096CF)
77c00000 77c08000 VERSION VERSION.dll Wed Aug 04 03:56:39 2004 (411096B7)
77c10000 77c68000 msvcrt msvcrt.dll Wed Aug 04 03:59:14 2004 (41109752)
77d40000 77dd0000 USER32 USER32.dll Wed Mar 02 13:09:29 2005 (42260159)
77dd0000 77e6b000 ADVAPI32 ADVAPI32.dll Wed Aug 04 03:56:23 2004 (411096A7)
77e70000 77f01000 RPCRT4 RPCRT4.dll Wed Aug 04 03:56:30 2004 (411096AE)
77f10000 77f57000 GDI32 GDI32.dll Wed Dec 28 21:54:35 2005 (43B34FEB)
77f60000 77fd6000 SHLWAPI SHLWAPI.dll Thu Sep 14 04:31:29 2006 (45091361)
7c800000 7c8f4000 kernel32 kernel32.dll Wed Jul 05 06:55:00 2006 (44AB9A84)
7c900000 7c9b0000 ntdll ntdll.dll Wed Aug 04 03:56:36 2004 (411096B4)
7c9c0000 7d1d5000 SHELL32 SHELL32.dll Thu Jul 13 09:33:24 2006 (44B64BA4)
804d7000 806fd000 nt ntkrnlmp.exe Tue Mar 01 19:57:27 2005 (42250F77)
806fd000 8071dd00 hal halmacpi.dll Wed Aug 04 01:59:09 2004 (41107B2D)
bac69000 bac79280 Udfs Udfs.SYS Wed Aug 04 02:00:27 2004 (41107B7B)
bac7a000 bace7880 BsUDF BsUDF.SYS Fri Sep 13 01:35:40 2002 (3D81792C)
bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 20:05:44 2005 (43446A58)
bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf9d4000 bfe25580 nv4_disp nv4_disp.dll Sun Oct 22 17:02:50 2006 (453BDC7A)
f5c1e000 f5c35480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f5c5e000 f5ccca00 mrxsmb mrxsmb.sys Fri May 05 05:41:42 2006 (445B1DD6)
f5ccd000 f5cf7a00 rdbss rdbss.sys Fri May 05 05:47:55 2006 (445B1F4B)
f5d98000 f5db9d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
f5dba000 f5de1c00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f5de2000 f5dfedc0 SYMEVENT SYMEVENT.SYS Sat Sep 16 01:48:19 2006 (450B9023)
f5dff000 f5e1ff00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
f5e20000 f5e5fce0 SYMTDI SYMTDI.SYS Tue Apr 05 14:10:52 2005 (4252D4AC)
f5e88000 f5edfd80 tcpip tcpip.sys Thu Apr 20 07:51:47 2006 (444775D3)
f5ee0000 f5ef2400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f74f1000 f7524200 update update.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7525000 f7555100 rdpdr rdpdr.sys Wed Aug 04 02:01:10 2004 (41107BA6)
f7556000 f7566e00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f757f000 f7581f80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
f7583000 f7586a00 kbdhid kbdhid.sys Wed Aug 04 01:58:33 2004 (41107B09)
f7587000 f758a220 LCcFltr LCcFltr.Sys Wed Mar 03 13:11:06 2004 (40461FBA)
f758f000 f75a5680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f75a6000 f75bd8a0 aeaudio aeaudio.sys Thu Mar 13 16:54:09 2003 (3E70FE01)
f75be000 f75e1980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
f75e2000 f766f300 smwdm smwdm.sys Mon Jun 02 13:42:12 2003 (3EDB8C74)
f7670000 f7692680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f7693000 f76a6900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
f76a7000 f76c9e80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
f76ca000 f76e7c00 e1000325 e1000325.sys Wed May 21 06:36:42 2003 (3ECB56BA)
f76e8000 f76fb780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f76fc000 f7acb400 nv4_mini nv4_mini.sys Sun Oct 22 17:08:02 2006 (453BDDB2)
f7b1e000 f7b26d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
f7b2e000 f7b362e0 LHidUsb LHidUsb.Sys Wed Mar 03 13:11:00 2004 (40461FB4)
f7b4e000 f7b56880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
f7b6e000 f7b76700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f7b7e000 f7b8cd80 arp1394 arp1394.sys Wed Aug 04 01:58:28 2004 (41107B04)
f853d000 f853f580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f854d000 f8550c00 ElbyCDFL ElbyCDFL.sys Thu Nov 28 09:18:04 2002 (3DE6259C)
f8571000 f858b580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f858c000 f85b8a80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f85b9000 f8645480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
f8646000 f8658f00 WudfPf WudfPf.sys Thu Sep 28 21:55:43 2006 (451C7D1F)
f8659000 f866f780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f8670000 f8681f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
f8682000 f86a1780 fltmgr fltmgr.sys Mon Aug 21 05:14:57 2006 (44E97991)
f86a2000 f86b9800 SCSIPORT SCSIPORT.SYS Wed Aug 04 01:59:39 2004 (41107B4B)
f86ba000 f86d1480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f86d2000 f86f7700 dmio dmio.sys Wed Aug 04 02:07:13 2004 (41107D11)
f86f8000 f8716880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f8717000 f8727a80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f8728000 f8755d80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f8777000 f877fc00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f8787000 f8795e80 ohci1394 ohci1394.sys Wed Aug 04 02:10:05 2004 (41107DBD)
f8797000 f87a4000 1394BUS 1394BUS.SYS Wed Aug 04 02:10:03 2004 (41107DBB)
f87a7000 f87b1500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f87b7000 f87c3c80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f87c7000 f87cfe00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f87d7000 f87e3200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f87e7000 f87f1580 agp440 agp440.sys Wed Aug 04 02:07:40 2004 (41107D2C)
f8817000 f8826180 nic1394 nic1394.sys Wed Aug 04 01:58:28 2004 (41107B04)
f8827000 f882f700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
f8877000 f8886900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
f88d7000 f88dfe40 SMBios SMBios.sys Thu Sep 11 18:20:22 2003 (3F60F526)
f88f7000 f88ffd00 intelppm intelppm.sys Wed Aug 04 01:59:19 2004 (41107B37)
f8907000 f8916d80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
f8917000 f8920680 AFS2K AFS2K.SYS Sat Feb 14 18:01:29 2004 (402EA8C9)
f8927000 f8933180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f8937000 f8945080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f8947000 f8951380 Imapi Imapi.sys Wed Aug 04 02:00:12 2004 (41107B6C)
f8957000 f8965b80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
f8967000 f8973880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f8977000 f8981200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f8987000 f8992d00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f8997000 f899f900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f89a7000 f89b0f00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f89b7000 f89c0480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f89c7000 f89d5100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f89f7000 f89fd200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f89ff000 f8a03900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f8a07000 f8a0c600 ElbyVCD ElbyVCD.sys Thu Nov 28 05:43:49 2002 (3DE5F365)
f8a17000 f8a1d180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
f8a37000 f8a3c200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f8a3f000 f8a43a80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
f8a47000 f8a4e880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f8a4f000 f8a56b80 usbccgp usbccgp.sys Wed Aug 04 02:08:45 2004 (41107D6D)
f8a57000 f8a5d780 USBSTOR USBSTOR.SYS Wed Aug 04 02:08:44 2004 (41107D6C)
f8a9f000 f8aa3500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f8b27000 f8b2c000 usbuhci usbuhci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f8b2f000 f8b35800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f8b37000 f8b3db00 fdc fdc.sys Wed Aug 04 01:59:25 2004 (41107B3D)
f8b3f000 f8b46a40 sf sf.sys Fri May 09 00:00:55 2003 (3EBB27F7)
f8b47000 f8b4b880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f8b4f000 f8b53580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f8b57000 f8b5b080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f8b5f000 f8b65000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f8b67000 f8b6ca00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f8b77000 f8b7c000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f8b87000 f8b8a000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f8b8b000 f8b8d480 bsstor bsstor.sys Thu Jun 06 02:41:41 2002 (3CFF0425)
f8c0b000 f8c0ec80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f8c4b000 f8c4d900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f8c4f000 f8c51280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f8c6f000 f8c71f00 ws2ifsl ws2ifsl.sys Fri Aug 17 16:55:58 2001 (3B7D84DE)
f8c73000 f8c76c80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
f8c77000 f8c78b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f8c79000 f8c7a100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f8c7b000 f8c7c700 dmload dmload.sys Fri Aug 17 16:58:15 2001 (3B7D8567)
f8cb3000 f8cb4100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f8cb7000 f8cb8280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f8cb9000 f8cbaf00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
f8cbb000 f8cbc080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f8cbd000 f8cbe080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
f8cbf000 f8cc0080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f8ce9000 f8cea100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f8d3f000 f8d3fd00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
f8e01000 f8e01d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
f8e5f000 f8e5fc00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
f8ec5000 f8ec5b80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)

Unloaded modules:
f7b5e000 f7b67000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f89e7000 f89f4000 i8042prt.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8c4b000 f8c4f000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8b7f000 f8b84000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f8c47000 f8c4a000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

#11 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:07 PM

Posted 08 February 2007 - 08:10 AM

Are you using a custom theme on your system (UXTheme)? This immediately precedes the logonui crash that this dump details - then it cascades into the nv4_mini.sys.

So, presuming that the new drivers are good, there's a couple of things that this could be:

1) faulty vid card
2) faulty Windows files
3) faulty UXTheme files
4) faulty motherboard

To check the vid card, you'll have to use another vid card that's known to be good.

To check the Windows files, there's 2 things to do:
1) Run SFC.EXE (link here: http://www.bleepingcomputer.com/forums/t/43051/how-to-use-sfcexe-to-repair-system-files/ )
2) If that doesn't work, then a repair install may help ( http://www.michaelstevenstech.com/XPrepairinstall.htm )

To check the UXTheme files - uninstall the application. If the errors go away, then it's likely that it was at fault. Reinstalling the app may let you have the theme without the errors - but this depends on what caused the problem.

To check the motherboard, either take the entire system to a shop for a diagnostic test, or try a new motherboard (but, I don't expect that this is a motherboard problem at this early stage of the troubleshooting).
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#12 David S

David S
  • Topic Starter

  • Members
  • 43 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:07 PM

Posted 11 February 2007 - 10:17 PM

Don't have an extra video card. Might be able to get one from work. I sent an e-mail to EVGA, the mfg of the Nvidia graphic card. Waiting for a response.

With SFC.exe, which "i386" folder is required, there are a bunch of them.

The only Uxtheme file are three .dll files. One in "system 32", the other in "ServicePackFiles\i386, and the last in "$NtServicePackUninstall$" (all text for this written in blue).

#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:07 PM

Posted 12 February 2007 - 07:54 AM

SFC.EXE should automatically find the i386 files if they're on your disk. I suspect that it's looking for the i386 on your installation CD tho'. Try inserting it when prompted. You may have to slipstream SP2 into it if you have an older copy of the CD. Instructions here: http://www.winsupersite.com/showcase/windo..._slipstream.asp
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#14 David S

David S
  • Topic Starter

  • Members
  • 43 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:07 PM

Posted 12 February 2007 - 12:56 PM

Found the discs. They are in .GHO format. I have no clue why.
I don't have Norton Ghost.

#15 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:07 PM

Posted 12 February 2007 - 07:00 PM

I suspect if you use the .gho files, you'll restore your computer to it's factory state (thereby destroying the data that's on the computer right now).

Let us know the exact make and model of your system so that we can figger out what to do with the .gho files.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users