New pc,lot of crash dump

[shikabalas]

Hello guys i bought a new pc about 3 weeks ago.I first installed win 7 32bit but two days ago i had the 64-bit version installed.Since that,i have a serious problem with a lot of crash dump.After the installation i thought everything was ok and i powered off the pc.After about 10 hours i tried to log on windows but i couldn't!In the welcome screen i got a BSOD.The pc kept restarting every time i tried,even from Safe mode!

Finally,i powered it off again.And the strange thing,after a little it was working just fine!But every time the pc is not working for 5-6 hours i cant log on and i have those BSODs.

I uploaded the dump files so you can help me.

PS.Sorry for my bad english.

 

[WalkerA WinTeam]

Hi shikabalas,

Welcome to SevenForums. Please fill out your System Specs as completely as possible so we can better assist you.

Cheers,

Walker
Windows Outreach Team

 

[shikabalas]

OK i did it.Oh,i should also add that after i replace 32bit with 64bit my hard disk is a little bit louder.

Anybody to help?

 

[Jonathan_King]

Seven dumps, six bugchecks.

One dmp blames ESET, so let's tackle that before anything else. Please remove it completely with this tool: http://download.eset.com/special/ESETUninstaller.exe

Install the latest updated version, as the older one is known to have problems in Windows 7.

You may also consider this free alternative if money is an issue: http://www.microsoft.com/security_essentials

Update your JumpStart Wireless driver as well:

jswpslwfx.sys Thu May 15 06:28:50 2008

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 07:00:55.093 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:20.593
BugCheck 24, {1904fb, fffff88007bb4de8, fffff88007bb4650, fffff80001cae4a3}
Probably caused by : Ntfs.sys ( Ntfs!NtfsInsertNameLink+d9 )
PROCESS_NAME:  services.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 18:23:10.658 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:42.016
BugCheck D1, {24005a, 2, 0, fffff88001007ef7}
Probably caused by : volsnap.sys ( volsnap!VspReadCompletionRoutine+17 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 15:18:36.270 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:37.003
BugCheck C2, {7, 1097, 0, fffff8a001e5c940}
Probably caused by : ntkrnlmp.exe ( nt!IopDeleteFile+168 )
BUGCHECK_STR:  0xc2_7_Toke
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 18:40:52.161 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:13.519
BugCheck 1E, {ffffffffc0000005, fffff80002d6e144, 0, 30}
*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
Probably caused by : eamonm.sys ( eamonm+1bcc1 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 18:25:02.130 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:15.630
BugCheck C5, {8, 2, 0, fffff80001fb90bf}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
BUGCHECK_STR:  0xC5_2
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 18:21:50.048 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:58.407
BugCheck 1E, {ffffffffc0000005, fffff80002aab82f, 0, 88800000860}
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 06:42:59.978 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:15.336
BugCheck 1000007E, {ffffffffc0000005, fffff80002d7357e, fffff880031afa48, fffff880031af2b0}
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKCBWorker+d6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[shikabalas]

I suspected that NOD 32 could be the problem and i unistall it before posting here but no result.I did it through Control Panel though,could i have better results if i used this programm you suggest?

Also,as i predicted,i turned the pc on after it was off for 8 hours and i had a new crash dump.

 

[CarlTR6]

This dmp is another stop error code 24:

STOP 0x00000024: NTFS_FILE_SYSTEM

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

Since this latest dump and the previous one's indicate hardware problems, let's do some testing.[FONT=&quot]
[/FONT]

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

Next, let's test the hard drive.

HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware

(read the details at the link)
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

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"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Copy/paste the results into your next post.

 

[shikabalas]

OK i am a little bit confused now.Right now i am runnig a test with Western Digital Data Lifeguard to check the hard drive.Then i will try what you suggest,i hope i can do it right and not cause another problem.

 

[CarlTR6]

That is good. Let us know what the results of the Western Digital test. Running chkdsk (check disk) will not cause a problem.

After you finish running the hard drive tests, you need to test your RAM (memory).

 

[shikabalas]

After two and a half hour the extended test completed and the hard drive passed it.Weird,i was pretty sure that it was the hard drive because of the ntfs.sys and the strange noise...

 

[CarlTR6]

That is a good sign. Go ahead and run chkdsk using the instructions above.

I suspected that NOD 32 could be the problem and i unistall it before posting here but no result.I did it through Control Panel though,could i have better results if i used this programm you suggest?

Yes, that is the only way to completely uninstall all traces. Try it and install MSE in its place for troubleshooting purposes.

 

[shikabalas]

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

 

[CarlTR6]

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]

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]

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:

View attachment 82060

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

 

[shikabalas]

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]

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]

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]

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+.

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]

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]

Time to enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

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
---------