![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) |
|
Registered User
Join Date: Jan 2008
Posts: 14
OS: Vista SP1
|
Help Read Minidump!
I just built a new system and the hardware seems to be fine. However, when I install Vista, both 32 and 64 bits, I get random BSODs and crashes. I just reinstalled 64 bit today and while I was trying to upgrade to SP1 the computer crashed. I attached two minidumps. Please read them and help me figure out what the problem is!
Ah, I just tried to install SP1 and I got error code 0x8007000D in the middle. I'll try installing drivers instead. |
|
|
|
| Important Information |
|
Join the #1 Tech Support Forum Today - It's Totally Free!
TechSupportForum.com is a leading support website for your computer needs. We offer free, friendly and personalized computer support. Why pay to have your computer fixed when you can do it for free. Join TechSupportforum.com Today - Click Here |
|
|
#3 (permalink) |
|
Registered User
Join Date: Jan 2008
Posts: 14
OS: Vista SP1
|
Re: Help Read Minidump!
No help? :(
Okay, status update. The last install crashed and wouldn't boot up so I was forced to reinstall Vista. The catch was my SATA DVD drive wouldn't install Vista (neither x32 or x64), so I had to use a temporary IDE drive. Now, I had Vista x64 w/ SP1 installed. All my drivers are updated (Radeon 4870 GPU, Soundmax sound, Marvell Yukon ethernet controllers) and most Vista updates are installed. The update exceptions are security updates, which have failed to install (BSOD in middle of installation), some Media Center updates, and KB947562 (a compatibility update), which also failed. This system (Intel Duo E8400, WD6400AAKS 640GB HDD, CORSAIR XMS2 DHX 4GB RAM [2 GB installed now], Asus Rampage Formula mobo) passed Memtest86+ and chkdsk with flying colors and I'm subjecting it to Prime95 right now. If the computer doesn't crash during Prime95, I think it's driver issues, or 64-bit issues in general... Oh, might it be the SATA DVD drive? It run CDs fine and I don't see how it could crash Vista when it's not in use, but it couldn't install Vista in the first place... |
|
|
|
|
|
#4 (permalink) |
|
Moderator, Microsoft Support
Join Date: Sep 2007
Location: Palm Springs, California
Posts: 9,802
OS: Windows 7, Vista Ultimate
|
Re: Help Read Minidump!
Hi hellic. . .
I have downloaded the mini kernel dumps and will process them as soon as possible. In the interim, please run msinfo32 and save as an NFO file (default save option), zip it up and attach to your next post. Regards. . . jcgriff2 . |
|
|
|
|
|
#5 (permalink) |
|
Moderator, Microsoft Support
Join Date: Sep 2007
Location: Palm Springs, California
Posts: 9,802
OS: Windows 7, Vista Ultimate
|
Re: Help Read Minidump!
Hi. . . I have some prelim results for you - 07-29-08-07 - the STOP error code (bugcheck) was [color=red] 0x0000001e (0xc0000005, 0x01c84d39, 0x00000000, 0xffffffff), listing memory corruption along with the Vista NT Kernel & System module ntkrnlmp.exe as the probable cause. I also found the process running when the system crashed was TrustedInstaller - the "user" that installs all programs under Vista - including Windows Updates. A bugcheck 0x0000001e = 0x1e along with the 0xc0000005 exception (first of 4 parameters) indicates that a kernel mode driver attempted access of an area of memory that is off-limits or that the memory address is bad. So far the others are showing the same 0x1e bugcheck - except for the dump file from 7-27-08-01. This particular crash had a bugcheck of 0x00000050 (0x06906128, 0x00000001, 0x0907c90, 0x00000002), listing the probable cause as the Microsoft NT File System driver ntfs.sys and the process was simply System. The 0x50 bugcheck = PAGE_FAULT_IN_NONPAGED_AREA and again is indicative of invalid system memory being referenced. I noticed the timestamp of the crash was Sun Jul 27 18:31:55.347 2008 (GMT-4) and shows mostly November 2006 pre-Vista SP1 modules, whereas the 0x50 dump two days later on 07-29-08-07 does contain Vista SP1 modules. I did read your post where you intitially had trouble with SP1, but apparantly got it in. What I am finding of interest in these dumps are the "stacks" - the disassembled program code, which I can only guess at its meaning as we are not privy to Vista source code. From the 0x50 dump, failing on the line in red: Code:
00c88560 : nt!KeBugCheckEx 02031180 : nt!MmAccessFault+0x509 00001400 : nt!KiPageFault+0x119 00000801 : Ntfs!NtfsUpdateFcbInfoFromDisk+0x700 01870439 : Ntfs!NtfsOpenRootDirectory+0x1a8 02156c10 : Ntfs!NtfsMountVolume+0x1cbd 01868d10 : Ntfs!NtfsCommonFileSystemControl+0xa3 02156c10 : Ntfs!NtfsFspDispatch+0x328 00000001 : nt!ExpWorkerThread+0x12a 018fa660 : nt!PspSystemThreadStartup+0x5b 00000000 : nt!KiStartSystemThread+0x16 Code:
00000000 : nt!KeBugCheckEx 000300bf : nt! ?? ::FNODOBFM::`string'+0x29317 00000000 : nt!KiExceptionDispatch+0xa9 00000004 : nt!KiGeneralProtectionFault+0xcd (TrapFrame @ fffffa60`0416d880) 00002474 : nt!MiUnlinkFreeOrZeroedPage+0x89 02472000 : nt!MiRemoveAnyPage+0xda 00000000 : nt!MiResolveDemandZeroFault+0x176 02471fc0 : nt!MmAccessFault+0x2054 00000000 : nt!KiPageFault+0x119 (TrapFrame @ fffffa60`0416dc20) 00000000 : 0x7798f1da - Check the Event Viewer - start with the filtered Admin log, looking for events leading up to a BSOD. - Check out wercon - Problem Reports and Solutions Although I did not find any direct reference to the Marvell Yukon Ethernet driver yk60x64.sys, I have seen it show up as a contributing factor in some BSODs. The timestamp on your driver is December 6, 2007, so I am unsure if the information in the code box below from May 2007 even applies - but I do think a visit with the Device Manager to check it out would be prudent. From a "read-me" file by Marvell: Code:
(C)Copyright 2002-2007 Marvell(R).
All rights reserved.
===========================================================================
yk60x64.txt created 24-May-2007
Readme File for YK60X64.sys v10.15.4.3
Marvell Yukon Ethernet Controller
NDIS6.0 Miniport Driver for Windows Vista x64
This file contains
1 Overview
2 Required Files
3 Installation
3.1 Installing the driver
3.2 Updating the driver
4 Parameters
===========================================================================
1 Overview
===========
YK60X64.sys is the NDIS6.0 64-bit Miniport driver.
***
2 Required Files
=================
To install the driver, the following files are required:
YK60X64.sys NDIS6.0 Miniport driver
YK60X64.inf installation setup script
YK60X64.CAT digital signature (only if the driver is certified)
***
3 Installation
===============
3.1 Installing the driver
--------------------------
Read the installation instructions in the adapter manual carefully.
Follow these instructions to install the adapter in your computer.
Due to the plug & play facility, the operating system is able to find,
identify, and configure an adapter automatically.
If the adapter is not detected during installation by the operating system the
adapter is installed as "Ethernet Controller" under "Other Devices".
To install the driver you have to perform a driver update as described
in the next section.
***
3.2 Updating the driver
------------------------
To update the driver, proceed as follows:
1. On the desktop right click on MY COMPUTER.
2. Select MANAGE.
3. In the "Device Manager" select the adapter you wish to update.
4. Double click.
5. Select DRIVER.
6. Click UPDATE DRIVER ... .
7. Follow the instructions given by the operating system to locate the driver.
8. If the driver which is found to be the latest is not the one you want
to install, select the checkbox "Install one of the other drivers".
9. Click NEXT.
10. Select the driver to be installed in the next listbox.
11. Click NEXT.
If a message is displayed saying that the driver is not digitally signed
by Microsoft, click YES.
12. The message "Windows has finished installing the software for this
device" is displayed.
13. Click FINISH to complete the installation.
Please note that the latest version of the YK60X64 driver is
available for download from our web site.
4 Parameters
=============
The YK60X64.sys driver allows you to modify several options in order to
optimize the operation of your adapter.
1. In "Network Connections" right click on the adapter you
want to configure.
2. Select "Properties".
3. Click "Configure".
4. Click "Advanced".
5. In the "Property" box, select the option that you want to change.
6. Enter the desired value in the "Value" box.
7. When finished, click OK .
The operating system will reload the driver with the changed settings.
The parameters supported by the driver are described below.
Network Address
------------------------
Default value: burned-in adapter address
Valid range: 02-00-00-00-00-01 to FE-FF-FF-FF-FF-FF (hexadecimal),
where at least the "multicast" bit(Bit 0) must not be set
(it indicates that the address field contains an
individual address)and the "locally administered" bit (Bit 1)
is set (the address has been assigned by a local
administrator). These two bits are first and second
bits transmitted on the LAN medium.
CAUTION: Each individual network MAC address can only be used once in a
network. Assigning the same address to more than one adapter in
the same network is not allowed and can cause serious network
problems.
To use a network MAC address other than the one burned into the adapter,
enter the network address in the following hexadecimal format:
e.g.: 02-00-5A-98-12-34
If the network address field blank is left blank (or a different number of
digits is specified), the network address burned into the adapter will
be used.
Jumbo-Packet
------------------------
Default value: "1514"
Valid values:
-"4088"
-"9014"
This parameter specifies the frame size that the driver will support.
The performance of your network usually increases If "Jumbo" frames
with a size > 1514 are used. Do not set the size to >1514 when
you are not sure if your network supports jumbo frames.
Note: For Fast Ethernet adapters the valid range is limited to 1514.
IPv4 Checksum Offload
---------------------
Default Value: "Tx & Rx Enabled"
Valid Values:
- "Tx & Rx Enabled"
- "Tx Enabled"
- "Rx Enabled"
- "Disabled"
This parameter is used to control the hardware checksum offload for
IPv4 traffic. There should be no need to disable it.
TCP Checksum Offload (IPv4),
UDP Checksum Offload (IPv4),
TCP Checksum Offload (IPv6),
UDP Checksum Offload (IPv6)
---------------------------
Default Value: "Tx & Rx Enabled"
Valid Values:
- "Tx & Rx Enabled"
- "Tx Enabled"
- "Rx Enabled"
- "Disabled"
These parameters are used to control the hardware checksum offload for
the combinations of TCP/UDP and IP versions. There should be no need to
disable them.
Wake Up Capabilities
------------------------
Default value: "Magic Packet and Pattern Match"
Valid values:
-"None"
wake on LAN capabilities are disabled
-"Magic Packet"
wake up with MagicPacket from ShutDown state,
OS Controlled from Hibernate or Standby state
-"Pattern Match"
wake up with a packet containing a special pattern
from ShutDown state, OS Controlled from Hibernate
or Standby state
-"Magic Packet and Pattern Match"
wake up with both from ShutDown state, OS Controlled
from Hibernate or Standby state
-"Link Change"
wake up with link change from ShutDown state,
OS Controlled from Hibernate or Standby state
Wake From Shutdown
------------------------
Default value: "Off"
Valid values:
-"Off"
disable the capabilities of the NIC to wake the computer
from shutdown.
-"On"
enable the NIC to be capable to wake the computer from shutdown.
Receive Buffers
------------------------
For Yukon family based ethernet controllers the following values are used:
Default value: 50 (decimal)
Valid range: 3..500 (decimal)
For Yukon2 family based ethernet controllers the following values are used:
Default value: 256 (decimal)
Valid range: 256..512 (decimal)
This parameters defines the number of receive buffers allocated by the
driver. If the system does not have enough resources the driver will fail
to load. Increasing this value may improve performance.
Transmit Buffers
------------------------
For Yukon family based ethernet controllers the following values are used:
Default value: 50 (decimal)
Valid range: 4..200 (decimal)
For Yukon2 family based ethernet controllers the following values are used:
Default value: 256 (decimal)
Valid range: 256..512 (decimal)
This parameters defines the number of transmit buffers allocated by the
driver. If the system does not have enough resources the driver will
fail to load. Increasing this value may improve performance.
Interrupt Moderation
------------------------
Default value: "On"
Valid values:
-"On"
-"Off"
If more than the specified rate of interrupts occur, the function
Interrupt Moderation groups these interrupts so that several data packets
can be handled per interrupt. This will lead to lower CPU utilization
but may increase the latency.
Max IRQ per Sec
------------------------
Default value: 5000 (decimal)
Valid range: 1000..30000 (decimal)
This parameter specifies the interrupt rate for Interrupt Moderation. If
Interrupt Moderation is set to "Off" it will be ignored.
Log Status Messages
------------------------
Default value: "Status Messages"
Valid values:
-"All Messages":
This option should only be used for test purposes.
-"Status Messages":
In this mode the driver will generate an event log
entry every time the link status changes.
-"Warnings":
In this mode you will only receive warning or error
messages.
-"Errors":
In this mode you will only receive error messages.
-"None":
All driver messages will be suppressed. It is not
recommended to use this value.
This parameter specifies the messages, which are to be logged in the
Event Log.
Speed & Duplex
------------------------
Default value: "Auto-Sense"
Valid range:
-"Auto-Sense"
-"10Mbps Half Duplex"
-"10Mbps Full Duplex"
-"100Mbps Half Duplex"
-"100Mbps Full Duplex"
This parameter contain information regarding autonegotiation,
duplex capabilities and link speed. Only if the setting is "Auto" the
Autonegotiation is set to "On", in every other settings it is turned "Off".
NOTE: This parameter is not valid for fiber adapter.
Preferred Port
------------------------
Default value: "A"
Valid range:
-"A"
-"B"
NOTE: This parameter is only available for dual link adapters.
Use this parameter to set the preferred port the RLMT (Redundant
Link Management Technology) will use for all network traffic, if more than
one port has an active link to the network.
RLMT Mode
------------------------
Default value: "CLS"
Valid range:
-"CLS" (Check Link State):
RLMT uses the link state reported by the
adapter hardware for each individual port to determine whether a
port can be used for all network traffic or not.
-"CLP" (Check Local Port):
In this mode, RLMT monitors the network path
between the two ports of an adapter by regularly exchanging packets
between them. This mode requires a network configuration in which
the two ports "see" each other (i.e. there must not be any router
between the ports).
-"CLPSS" (Check Local Ports and Segmentation Status):
This mode supports
the same functions as the CLP mode and additionally checks network
segmentation by sending BPDU hello packets. Thus, this mode is only
to be used if Gigabit Ethernet switches are installed on the network
that have been configured to use the Spanning Tree protocol.
NOTE: RLMT modes "CLP" and "CLPSS" are designed to operate in
configurations where a network path between the ports on one adapter
exists. Moreover, they are not designed to work where adapters are
connected back-to-back.
This parameter is only available for dual link adapters.
Priority & VLAN
------------------------
Default Value: "Priority and VLAN Disabled"
Valid Values:
- "Priority Enabled"
- "VLAN Enabled"
- "Priority & VLAN Enabled"
- "Priority and VLAN Disabled"
This parameter will enable/disable 802.1p (QoS) and/or 802.1q (VLAN)
capability.
NOTE: This will only enable the CAPABILITY of the driver to handle such
packets. There must be a protocol or application that passes such packets
to the driver.
BatteryModeLinkDetection
------------------------
Default Value: "EnergyDetect+(TM)"
Valid Values:
-"NoEnergySaving":
No Energy saving functions are switched on in the NIC.
-"MaximumEnergySaving":
The NIC is switched off if there is no link in battery mode.
The driver wakes up the NIC every 20 seconds to check
if there is a new link.
-"EnergyDetect+(TM)":
If battery-powered the NIC is set to "EnergyDetect+"(TM) mode.
The link is activated faster than in "MaximumEnergySaving" mode,
but the NIC requires more power.
This parameter will set the mode in which the NIC is working if there
is no link and the PC is battery-powered.
BatterySpeedSettings
------------------------
Default Value: "FullSpeed"
Valid Values:
-"SmartSpeedDown":
If the computer is battery-powered, the NIC speed is
switched to 10/100Mbit/s to reduce the power consumption.
- "FullSpeed":
If the computer is battery-powered the NIC is working with
maximum speed and maximum power consumption.
If the computer is supplied by AC power all power saving features
are switched off, and the NIC is working with maximum speed.
This parameter will sets the Line speed for the NIC if PC is
battery-powered.
FlowControl
------------------------
Default value: "On"
Valid range:
-"Off":
No link partner is allowed to send PAUSE frames.
-"On":
Both link partners are allowed to send PAUSE frames.
This parameter can be used to set the flow control capabilities the port
reports during auto-negotiation. This parameter can be set for each port
individually, which is helpful if the port at the other end of the cable cannot
handle all possible combinations. Using the default setting, the adapter should
automatically detect the capabilities of the peer port.
Large Send Offload (IPv4)
-------------------------
Default value: "Enabled"
Valid range:
-"Enabled":
The big packets are segmented on the NIC before to be sent to the
network. Using this method the processor will be not loaded to do
this job.
-"Disabled":
The packets are not segmented by the NIC.
NOTE: This parameter is only available starting with the NICs based on
Yukon2 chip.
Large Send Offload v2 (IPv4),
Large Send Offload v2 (IPv6)
----------------------------
Default value: "Enabled"
Valid range:
-"Enabled"
-"Disabled"
These parameters control the capability of Large Send Offload version 2
for IPv4 and IPv6 traffic.
NOTE: This parameter is not available on every hardware version.
*** End of Readme File ***
Another item that caught my eye was the Macrovision driver secdrv.sys, dated Wed Sep 13 09:18:38 2006. Again, not sure if relevant, but Microsoft updated a security bulletin on this driver in December 2007, found HERE. Was this one of the updates that failed? I would also like you to check the Vista hardware compatibility list, found HERE, if you have not already done so. Lastly, a few reports for me, please: - msinfo32 - type it into the start search box, hit enter. Save it as an NFO file - very important. - dss - Deckard's System Scanner - this will show me your system services, start-up apps, file movements, a few event log entries, etc... Please click on the dss link below in my sig area and save it to your desktop. Then go to an elevated command prompt - START | type cmd.exe | right-click on cmd.exe above | run as admin - then type the following into the black "DOS" box (hit enter after each line): Code:
cd %userprofile%\desktop dss /config --> another screen will come up asking about HiJackThis - your choice - allow it to install it or use the clone It will run for a few minutes, then a Notepad will appear - main.txt - and another will be minimized - extra.txt. Please gather these two text files and the msinfo32 NFO file, zip them up and attach to your next post. I have attached a zip file to this post containing the dbug output from the two dumps that I went over here today. Regards. . . jcgriff2 |
|
|
|
|
|
#6 (permalink) |
|
Registered User
Join Date: Jan 2008
Posts: 14
OS: Vista SP1
|
Re: Help Read Minidump!
First off, thank you for responding in such detail.
For the Marvell Yukon Ethernet driver, I installed the latest Vista x64 version from their website, but I had to system restore to before then so I'm not sure what driver I'm running now. I don't believe the Macrovision driver secdrv.sys is an issue, as it doesn't affect Vista builds. I think all my hardware is compatible with Vista x64, or at least "certified". I saved a msinfo32 log and ran dss, but while I ran dss for the first two times I got two BSODs (minidumps #2 and #3). The third time, everything went well except for the messages "swreg.exe - Entry point not found" and "verclsid.exe - Entry point not found", under which the description read "The procedure entry point ???? (gibberish symbols) could not be located in the dynamic link library Kernel32.dll". Also, before most BSODs I get error messages like "Superfetch stopped working" or "Host processes for Windows services stopped working" or "Catalyst Control Centre: Host application stopped working" (my Radeon 4870 driver application, the latest edition). |
|
|
|
![]() |
| Thread Tools | |
|
|