Good day guys,
First time ever visiting these forums, found it through google. I can't actually boot into windows at all - every time I type in my password, it loads for about 10-20 seconds and seems to lag for a little while, and then jumps straight to the BSOD, or occassionally it will load all the icons just to tease me, and once that i done, it will BSOD. Same thing happens in Safe Mode (the most basic version).
After this happened about 20 times, I got a bootable windows 7 repair USB and tried to have it scan drivers etc for errors but it found nothing wrong. Finally I decided to do a System Restore to just 1 week before the BSOD started (strange enough the only 1 that was saved - I couldn't find any more)
I'm running a USB bootable copy of Linux Mint right now and have access to the HDD. I was actually ready just format the laptop but while backing up files I discovered ALL 5 years worth of my photos from My Pictures are gone, including photos from a 4 month backpacking trip to Europe from just a few months ago!
I have no idea how to interpret the minidump but have read somewhere that it helps determine what causes the BSOD so I've attached it (there were 3 in the minidump folder, i've put them into a zip). System details as follows:
Windows 7: Retail x64
Laptop make: Acer 1810tz, purchased brand new around 1 yr ago, no reinstalls since.
Software last installed (or should I say software installations that System Restore advised would be changed as a result of the restore): Acoustica (fresh install), Firefox (update).
Bottom line is I just want to get my photos back - if there's a way to do it in Linux Mint I am more than willing to learn but I have no idea how to even start. The only option as I see it is to find out how to get back into Windows and go from there. Any advice would be appreciated!:)
These three crashes were probably caused by your network driver (NETw5s64.sys) I would re-install with the newest version available.
Intel(R) Wireless WiFi Link 5000 Series Adapter ... Description: Related to NETw5s64.sys Wireless WiFi Link Driver from Intel ...
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\061510-19796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c4c0?
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce50
Debug session time: Mon Jun 14 22:44:23.581 2010 (GMT-5)
System Uptime: 1 days 8:06:24.891
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
...........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8004ab4a20, fffff80000b9c4d8, fffffa800416fa00}
*** 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: fffffa8004ab4a20, Physical Device Object of the stack
Arg3: fffff80000b9c4d8, Functional Device Object of the stack
Arg4: fffffa800416fa00, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa800416fa00
DEVICE_OBJECT: fffffa80052a3050
DRIVER_OBJECT: fffffa80052f75c0
IMAGE_NAME: NETw5s64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b4df6b9
MODULE_NAME: NETw5s64
FAULTING_MODULE: fffff8800487b000 NETw5s64
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002afe1b3 to fffff80002a8f600
STACK_TEXT:
fffff800`00b9c488 fffff800`02afe1b3 : 00000000`0000009f 00000000`00000003 fffffa80`04ab4a20 fffff800`00b9c4d8 : nt!KeBugCheckEx
fffff800`00b9c490 fffff800`02a9b6a6 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c530 fffff800`02a9aa26 : fffffa80`03f5d338 fffffa80`03f5d338 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`02a9b57e : 0000010d`1df6c469 fffff800`00b9cc18 00000000`00710e58 fffff800`02c0cd88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`02a9ad97 : 00000022`40e1aec2 00000022`00710e58 00000022`40e1ae15 00000000`00000058 : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`02a97dfa : fffff800`02c09e80 fffff800`02c17c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 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
---------
Quote