PC Keeps Rebooting

[jonny813]

I don't see a Crashdump folder :s

Tried viewing hidden files and folders, and showing protected operating system files? Might be viewable then

 

[Jewelzz]

Tried viewing hidden files and folders, and showing protected operating system files? Might be viewable then

Yep, I'm have those both enabled

 

[wadada]

by any change did the windows update today ? one update is not installing and my computer also rebooted few times. check my other post about this.

 

[Tarun]

The crashdump should be located in C:\Windows\Minidump\

 

[gonaads]

I don't see a Crashdump folder :s

Yeah I read through that link I gave you and it is actually created by whoever may need to create crush dump files. Sooo that's a bummer.

 

[gonaads]

The crashdump should be located in C:\Windows\Minidump\

Yes! Thank you. 🙂

Explanation of Crash Dumps and WinDbg. (Good Read) 5 Parts but they are listed in backward order (5, 4, 3, etc...).

http://www.dumpanalysis.org/blog/index.php/category/crash-dumps-for-dummies/

 

[Jewelzz]

*shrug*

Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Jul 10 07:03:48.894 2007 (GMT-5)
System Uptime: 0 days 11:43:37.882
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
......................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............................
Unable to load image NDIS.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
Unable to load image NVENETFD.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NVENETFD.sys
*** ERROR: Module load completed but symbols could not be loaded for NVENETFD.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {19, 2, 0, f72237d5}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for NVNRM.SYS
*** ERROR: Module load completed but symbols could not be loaded for NVNRM.SYS
Probably caused by : NVENETFD.sys ( NVENETFD+3482 )

Followup: MachineOwner

 

[Jewelzz]

by any change did the windows update today ? one update is not installing and my computer also rebooted few times. check my other post about this.

No new updates have been installed in the last week. You're other post is in regards to Vista, I'm running XP

 

[Tarun]

Try Everest Home Edition 2.20.405 (4.0 MB)

You have two options here. You can go to Summary and scroll down to the Network section and copy the Network Adapter line. Next, right click and choose Copy.

Or.

You can click Network > Windows Network then right click and choose Copy All.

This will tell us exactly what your Network Adapter is so that we can help you get the necessary driver update(s) to resolve the issue efficiently.

 

[Jewelzz]

Think this is what I posted earlier

Network:
Network Adapter NVIDIA nForce Networking Controller
Modem PCI Soft Data Fax Modem with SmartCP

 

[gonaads]

You may need to D/L the Windows Symbol Packages.

http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx

The system crashed at NVENETFD.sys? They maybe related to faulty ram.

Try the Microsoft Windows Memory Diagnostic:- http://oca.microsoft.com/en/windiag.asp

 

[gonaads]

Hey Jewelzz does your MB have an NVIDIA chip set? I went on the NVIDIA forums 😱 and found some info and some relation the the drivers the version network card and other stuff.

http://forums.nvidia.com/lofiversion/index.php?t9088.html

Now it did begin in 05 but there are still posts on through May 07. Maybe some reading of it is needed.

 

[j79zlr]

Yea, those debugger messages look like they are nVidia related. I would check for updates to the NIC and your chipset as well as any BIOS upgrades.

 

[Jewelzz]

Will do on Friday, have to work the next 2 days

 

[Tarun]

You just need to update your drivers. That should resolve the issue.

 

[Jewelzz]

Ok boys, my PC rebooted again this time with a different error...

NVENETFD.sys Is this pointing to my video card or NIC card?

 

[gonaads]

See post about nick card and m/b.

http://www.osnn.net/forum/showpost.php?p=798000&postcount=32

They talk about problems with network card and NVIDIA drivers.

 

[Jewelzz]

They're all talking about 5.10 and 5.11 drivers, mine are 50.0.9.0 so I'm really confused :s

 

[Dark Atheist]

do you know what the chipset is ? norm in the name of the mobo eg m2n-590-sli, best be would be to look on the nvidia website under drivers and get the updated drivers for your board, on mine its still the 9.35 drivers date 26th june 2006 (thats xp btw) if your using vista they are on 15.00

 

[Jewelzz]

This is a Gateway PC, the MB model is GM5052E. I looked on Gateway's site and the MB package driver patch contains:

The files included in this package are:
* Ethernet NRM driver version 50.09 (WHQL)
* Network management tools version 50.09
* SMBus driver version 4.50 (WHQL)
* Installer version 4.90
* Win2K IDE SATARAID driver version 6.22 (WHQL)
* Win2K IDE SATA_IDE driver version 6.22 (WHQL)
* Win2K RAIDTOOL application version 6.22
* WinXP IDE SATARAID driver version 6.22 (WHQL)
* WinXP IDE SATA_IDE driver version 6.22 (WHQL)
* WinXP RAIDTOOL application version 6.22



Which is what I have installed already. As a side note, the PC seems to reboot when I'm downloading torrents using Azureus *shrug* Uploading is fine it's downloading that gives me BSOD