Windows 7: New pc,lot of crash dump

shikabalas · 28 Jun 2010

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 · 28 Jun 2010

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 · 28 Jun 2010

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 · 28 Jun 2010

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:

Code:

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

BSOD BUGCHECK SUMMARY

Code:


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

shikabalas · 29 Jun 2010

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 · 29 Jun 2010

This dmp is another stop error code 24:

Quote:

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.

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.

Next, let's test the hard drive.

HD Diagnostic (read the details at the link)

Quote:

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

Quote:

(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 · 29 Jun 2010

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 · 29 Jun 2010

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 · 29 Jun 2010

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 · 29 Jun 2010

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

Quote:

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.

Windows 7: New pc,lot of crash dump

New pc,lot of crash dump problems?