Cannot view or upload minidump files!

[necrodragon]

I used BlueScreenView to check what was the cause of the multiple BSOD's i was always getting and it turns out it is ntoskrnl.exe. However, i cannot zip the minidump .dmp file to upload and I cannot view the file's contents at all either.

 

[zigzag3143]

I used BlueScreenView to check what was the cause of the multiple BSOD's i was always getting and it turns out it is ntoskrnl.exe. However, i cannot zip the minidump .dmp file to upload and I cannot view the file's contents at all either.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[necrodragon]

I used BlueScreenView to check what was the cause of the multiple BSOD's i was always getting and it turns out it is ntoskrnl.exe. However, i cannot zip the minidump .dmp file to upload and I cannot view the file's contents at all either.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

You misunderstood, I cannot upload the minidump files because the computer won't let me access them, through the right-click zip method or through 7-zip.

 

[necrodragon]

the minidump file

 

[zigzag3143]

the minidump file

Only thing in that file is the shortcut. NO DMP files try again.

 

[necrodragon]

the minidump file

Only thing in that file is the shortcut. NO DMP files try again.

that's the best i can do, it won't let me make a zip of the actual file from it's original folder or from the desktop. I have never had to deal with anything like this before, please guide me step by step.

 

[necrodragon]

Hopefully it will work this time

 

[zigzag3143]

Hopefully it will work this time

This one is related to your network driver NETw5s64.sys.. re-install using newest.

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


Loading Dump File [C:\Users\K\Desktop\060411-22495-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`0324b000 PsLoadedModuleList = 0xfffff800`03488e50
Debug session time: Sat Jun  4 22:09:00.612 2011 (GMT-4)
System Uptime: 0 days 11:05:39.220
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8004902060, fffff80000b9c518, fffffa800b5d55a0}

*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8004902060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800b5d55a0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800b5d55a0

DEVICE_OBJECT: fffffa8005d36050

DRIVER_OBJECT: fffffa8005c24800

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df6b9

MODULE_NAME: NETw5s64

FAULTING_MODULE: fffff88006093000 NETw5s64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000332a383 to fffff800032bb700

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0332a383 : 00000000`0000009f 00000000`00000003 fffffa80`04902060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`032c72ae : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29270
fffff800`00b9c570 fffff800`032c6de6 : fffffa80`07c4c168 fffffa80`07c4c168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`032c74ce : 0000005c`fda15941 fffff800`00b9cc58 00000000`002710be fffff800`03439a48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`032c6cc7 : 00000013`53b20ec2 00000013`002710be 00000013`53b20ef4 00000000`000000be : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`032c3eea : fffff800`03435e80 fffff800`03443c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_NETw5s64.sys

BUCKET_ID:  X64_0x9F_IMAGE_NETw5s64.sys

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

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[papapnoi]

*Deleted Post*

 

[Craig Beverley]

...