Windows 7: New pc,lot of crash dump

shikabalas · 29 Jun 2010

I tried it but it says i have limited access something like that.How can i run as admin?

CarlTR6 · 29 Jun 2010

Quote:

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

This should work for you.

shikabalas · 29 Jun 2010

Oh my mistake i didnt see that.OK i did it and restarted the pc but because windows are in greek i am not sure where to look now for the logs.I attached a screen i hope you can understand if i am looking in the right place.

CarlTR6 · 29 Jun 2010

That does not look like chkdsk. It looks like the event viewer (since I don't read Greek). Check disk is run from the command prompt. It should look like this:

Attachment 82060

After the command is type in, you press the Enter key to run the command.

shikabalas · 29 Jun 2010

Yes i did that and also restart but i dont know what or where to look next.

PS.Thank you for your time,i really appreciate it.

CarlTR6 · 29 Jun 2010

You are very welcome; that is what we are here for.

To recap:

1. You have run the Western Digital HD test as well as dskchk. This should eliminate your hard drive as the cause.

2. Have you updated this driver, jswpslwfx.sys Thu May 15 06:28:50 2008? If not this is your next step. Do you need help with this?

3. Have you run memtest86+? This will be your next step after updating that driver.

shikabalas · 29 Jun 2010

OK Check disk is done and i didnt see any errors.I searched about the driver but i did not find any updates.Do you know where i should look?

CarlTR6 · 29 Jun 2010

Good job on the disk check; that eliminates the HD as the problem.

This may help you. Go to the website below and search for an updated driver for your specific D-Link model.

jswpslwfx.sys is a D-Link USB Wireless Adapter Driver. D-Link - Tech Support Product List

If there is not a newer driver available, you might consider getting a new adapter, one that is compliant with Win 7 and installing it.

Once you have updated your wireless adapter or driver, you can run your system and see if you get another BSOD. If you do post it and we will look at it. If you don't perhaps you have solved your problem.

If you do get another BSOD, go ahead and run memtest86+.

Quote:

Download a copy of Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a CD using http://isorecorder.alexfeinman.com/Windows 7. Boot from the CD, and leave it running for at least 7 passes. Report back with the results.

shikabalas · 30 Jun 2010

As usually,new BSOD today morning.I attached the minidump file,even though i think it will be a ntfs.sys error again.

I will try to update the driver now,it's something about the network card right?Where can i find what model i have?

Jonathan_King · 30 Jun 2010

Time to enable driver verifier: Using Driver Verifier to identify issues with Drivers

Code:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_shikabalas.zip\063010-17877-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c52e50
Debug session time: Wed Jun 30 05:29:49.660 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:19.018
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {76fc0f8a, 0, ffff0000, fffff88003a3aca0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

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

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them.  A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 0000000076fc0f8a, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 00000000ffff0000, Thread->KernelApcDisable
Arg4: fffff88003a3aca0, Previous KernelApcDisable

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


FAULTING_IP: 
+6230343461643835
00000000`76fc0f8a ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002a84b69 to fffff80002a85600

STACK_TEXT:  
fffff880`03a3aa68 fffff800`02a84b69 : 00000000`00000001 00000000`76fc0f8a 00000000`00000000 00000000`ffff0000 : nt!KeBugCheckEx
fffff880`03a3aa70 fffff800`02a84aa0 : 00000000`00000000 00000000`002f9660 00000000`00000021 00000000`002f9660 : nt!KiBugCheckDispatch+0x69
fffff880`03a3abb0 00000000`76fc0f8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`00c3f9c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fc0f8a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceExit+245
fffff800`02a84aa0 4883ec50        sub     rsp,50h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceExit+245

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_120_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_SysCallNum_120_nt!KiSystemServiceExit+245

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

Windows 7: New pc,lot of crash dump

New pc,lot of crash dump problems?