Solved

BSD on new windows 7  pc how do I open and fix mii dump files

Posted on 2011-03-10
6
716 Views
Last Modified: 2012-05-11
Hello my new pc just BSD twice in the last 20 mins. I have the mini dump files but I do not know how to open them or fix this. Below are the error code that i received from event viewer.

Event 1001
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x0000000000000008, 0x0000000000000002, 0x0000000000000000, 0xfffff8800458f069). A dump was saved


event 41 Kernel Power Task Category (63)
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event 26 Tasks Category (4)  Kernel Processing Power

Processor 1 in group 0 exposes the following:

1 idle state(s)
4 performance state(s)
0 throttle state(s) 031011-30139-01.dmp
0
Comment
Question by:simmi196
  • 4
  • 2
6 Comments
 
LVL 4

Accepted Solution

by:
dailypcguy earned 500 total points
Comment Utility
The faulting file is WUBS300N.sys
Here is the analysis
Symbol search path is: SRV*C:\Debug\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 Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
Debug session time: Fri Mar 11 06:33:26.250 2011 (UTC + 11:00)
System Uptime: 0 days 5:50:53.686
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 0, fffff8800501e069}

Unable to load image WUBS300N.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WUBS300N.sys
*** ERROR: Module load completed but symbols could not be loaded for WUBS300N.sys
Probably caused by : WUBS300N.sys ( WUBS300N+a069 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800501e069, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf50e0
 0000000000000008

CURRENT_IRQL:  2

FAULTING_IP:
WUBS300N+a069
fffff880`0501e069 4c8b7608        mov     r14,qword ptr [rsi+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c310 -- (.trap 0xfffff80000b9c310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8004bff280
rdx=fffffa8004bfdb02 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800501e069 rsp=fffff80000b9c4a0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002a4d000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
WUBS300N+0xa069:
fffff880`0501e069 4c8b7608        mov     r14,qword ptr [rsi+8] ds:9998:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002abcca9 to fffff80002abd740

STACK_TEXT:  
fffff800`00b9c1c8 fffff800`02abcca9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c1d0 fffff800`02abb920 : fffff800`00b9c310 fffffa80`04b3e000 00000000`00000000 fffffa80`02c47cb0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c310 fffff880`0501e069 : 00000000`00000000 ffff0080`012fb576 fffffa80`04c01338 fffffa80`04b3e000 : nt!KiPageFault+0x260
fffff800`00b9c4a0 00000000`00000000 : ffff0080`012fb576 fffffa80`04c01338 fffffa80`04b3e000 fffff880`0196cd40 : WUBS300N+0xa069


STACK_COMMAND:  kb

FOLLOWUP_IP:
WUBS300N+a069
fffff880`0501e069 4c8b7608        mov     r14,qword ptr [rsi+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  WUBS300N+a069

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WUBS300N

IMAGE_NAME:  WUBS300N.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46e66c93

FAILURE_BUCKET_ID:  X64_0xD1_WUBS300N+a069

BUCKET_ID:  X64_0xD1_WUBS300N+a069

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

0: kd> lmvm WUBS300N
start             end                 module name
fffff880`05014000 fffff880`05066780   WUBS300N T (no symbols)          
    Loaded symbol image file: WUBS300N.sys
    Image path: WUBS300N.sys
    Image name: WUBS300N.sys
    Timestamp:        Tue Sep 11 20:23:15 2007 (46E66C93)
    CheckSum:         00056B28
    ImageSize:        00052780
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Just looking for more info on this module but a guess would be a wireless N usb stick maybe??
0
 
LVL 4

Expert Comment

by:dailypcguy
Comment Utility
Try updating your drivers, or if you recently updated a driver, try rolling back to the previous (non-faulting) driver.
0
 

Author Comment

by:simmi196
Comment Utility
That would be the USB wireless adapter. I didn't load any drivers recently, I'll check for new ones but I think the computer ran windows update last night. Who program did you use to open that dump file?
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 4

Expert Comment

by:dailypcguy
Comment Utility
You can dl the crash dump debuggers with the Windows 7 drivers kit. The included one it windbg.exe

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff

I found that it's quite useful, and a good idea to follow the install docs, there's a few tutes on how to's and reasonably straight forward, you can even remote kernell debug via the interface over 1395/IEEE connection.

The update being a problem is odd, check for new OEM drivers etc first or even system restore? up2U.
0
 

Author Comment

by:simmi196
Comment Utility
Can I use that tool on windows server dumps also?
0
 
LVL 4

Expert Comment

by:dailypcguy
Comment Utility
Think so. Sould be okay for 2008 but maybe not 2003. You'd have to check the documentation to be certain :-)
Glad I could help out! Thanks.
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now