Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFFA80660C553B
BCP2: 0000000000000000
BCP3: FFFFF80002CE65FF
BCP4: 0000000000000005
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\081710-23306-01.dmp
C:\Users\GameOn\AppData\Local\Temp\WER-30966-0.sysdata.xml
It keep restart my computer even if i am just using msn.Can anyone help me?I tried change the ram slot after all it works fine.But next day if i dun change the ram slot again,the problems will still appear.
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFFA80660C553B
BCP2: 0000000000000000
BCP3: FFFFF80002CE65FF
BCP4: 0000000000000005
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\081710-23306-01.dmp
C:\Users\GameOn\AppData\Local\Temp\WER-30966-0.sysdata.xml
It keep restart my computer even if i am just using msn.Can anyone help me?I tried change the ram slot after all it works fine.But next day if i dun change the ram slot again,the problems will still appear.
Time to enable driver verifier: Driver Verifier - Enable and Disable
Also, do you have another video card you can try? Try a friend or another computer.
...Summary of the Dumps:
Also, do you have another video card you can try? Try a friend or another computer.
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Aug 16 01:49:16.216 2010 (UTC - 4:00) System Uptime: 0 days 0:30:08.262 BugCheck 50, {fffff680100131f8, 0, fffff80002ca49fa, 2} Probably caused by : memory_corruption ( nt!MiSwapWslEntries+6a ) BUGCHECK_STR: 0x50 PROCESS_NAME: iexplore.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Aug 16 01:18:02.490 2010 (UTC - 4:00) System Uptime: 0 days 1:05:34.912 BugCheck 1A, {41790, fffffa8000973950, ffff, 0} Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 ) BUGCHECK_STR: 0x1a_41790 PROCESS_NAME: iexplore.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 03:21:16.770 2010 (UTC - 4:00) System Uptime: 0 days 0:11:32.191 BugCheck 1A, {41790, fffffa8000912120, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 ) BUGCHECK_STR: 0x1a_41790 PROCESS_NAME: svchost.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 04:00:47.583 2010 (UTC - 4:00) System Uptime: 0 days 0:18:59.004 BugCheck 50, {fffffa80660c553b, 0, fffff80002ce65ff, 5} Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df ) BUGCHECK_STR: 0x50 PROCESS_NAME: WerFault.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 04:32:49.948 2010 (UTC - 4:00) System Uptime: 0 days 0:28:32.368 BugCheck 1A, {41790, fffffa80009a3950, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339c8 ) BUGCHECK_STR: 0x1a_41790 PROCESS_NAME: WerFault.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 03:41:11.786 2010 (UTC - 4:00) System Uptime: 0 days 0:17:46.206 BugCheck 1A, {41790, fffffa80009665a0, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 ) BUGCHECK_STR: 0x1a_41790 PROCESS_NAME: iexplore.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 03:09:08.387 2010 (UTC - 4:00) System Uptime: 0 days 0:15:24.808 BugCheck 1A, {41790, fffffa8000996120, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339c8 ) BUGCHECK_STR: 0x1a_41790 PROCESS_NAME: WerFault.exe �������������������������������������������������������������������������������������� The driver verify manager tick all that is not microsoft corporation isit?To disable it or enable it?
Tick all that is NOT MS Corp, so that all drivers except MS drivers get tested.
Ok done.Must restart it?Then wont have blue screen anymore?.
Restart it, then you will get BSODs faster than you have ever seen before. However, hopefully the dumps it generates will be of some use to us.
what is BSODs anyway?
Read this article: Blue Screen of Death - Wikipedia, the free encyclopedia
It is when Windows shut down when it encounters a critical error, to avoid data loss or hardware damage.
It is when Windows shut down when it encounters a critical error, to avoid data loss or hardware damage.
AFter i restart still will blue screen.How?
It stresses 3rd-party drivers, in hopes of making them cause a BSOD.
what should i do now?
If you have rebooted, use your computer normally until it crashes. Wait for about 3-5 crashes, then follow these directions: http://www.sevenforums.com/crashes-d...tructions.html
Do u have msn?cos i dun really understand about the bsod instrution.
3. Run a System Health Report -
START | type perfmon /report - a viewer will appear | Save as an HTML file .
what is mean by that?>
START | type perfmon /report - a viewer will appear | Save as an HTML file .
what is mean by that?>
Open the start menu, and enter perfmon /report. Wait for it to finish, then go to File>Save As, and save as a .html file.
all the steps i done.Now send as post?
Now look in Documents, and you will see the Windows7_Vista folder. Right-click on it, and select Send to>New compressed folder.
When that is done, drag the perfmon file into the new zip folder.
On your next post, click on the paperlclip icon in the editing bar, navigate to the new zip folder, and upload it.
When that is done, drag the perfmon file into the new zip folder.
On your next post, click on the paperlclip icon in the editing bar, navigate to the new zip folder, and upload it.
here is my post.
I upload it seperately can?.Cos i dunno how to drag in.I have post on new thread.Do check out.
Thanks, I'll reply to the new thread, and ask the mods to merge the 2 threads.
Oh u saw the post name *BSOD post to JK*? So what should i do now?.
Just hold on, I'll post in the new thread in a few minutes.
okok thanks
I wonder if ESET is causing the issue.
Please remove it with this tool: http://download.eset.com/special/ESETUninstaller.exe
Install MSE (free) for the time being: http://www.microsoft.com/security_essentials
ESET is known to be stable, so if ESET is indeed the cause, I'll send this thread to an ESET beta tester I know.
...Summary of the Dumps:
Please remove it with this tool: http://download.eset.com/special/ESETUninstaller.exe
Install MSE (free) for the time being: http://www.microsoft.com/security_essentials
ESET is known to be stable, so if ESET is indeed the cause, I'll send this thread to an ESET beta tester I know.
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 06:51:32.743 2010 (UTC - 4:00) System Uptime: 0 days 0:13:07.179 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0x7E PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 03:21:16.770 2010 (UTC - 4:00) System Uptime: 0 days 0:11:32.191 BugCheck 1A, {41790, fffffa8000912120, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 ) BUGCHECK_STR: 0x1a_41790 PROCESS_NAME: svchost.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 06:37:35.904 2010 (UTC - 4:00) System Uptime: 0 days 0:05:08.966 BugCheck C4, {e3, fffffa8008d03b51, 49bf3b4, 0} Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c ) BUGCHECK_STR: 0xc4_e3 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: ekrn.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 07:14:55.047 2010 (UTC - 4:00) System Uptime: 0 days 0:09:45.498 BugCheck D1, {fffff9801b70cff8, 2, 0, fffffa80078ddfc6} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xD1 PROCESS_NAME: msiexec.exe �������������������������������������������������������������������������������������� Okay, I posted.
http://www.sevenforums.com/crashes-d...tml#post904002
The threads should be merged soon.
http://www.sevenforums.com/crashes-d...tml#post904002
The threads should be merged soon.
need to un install eset?
Yes, uninstall ESET, then run this tool: http://download.eset.com/special/ESETUninstaller.exe
alright hold on
what nexts?
what nexts?
Turn off Verifier, as given instructions here: Driver Verifier - Enable and Disable
Then just wait and see if you get more BSODs.
Then just wait and see if you get more BSODs.
disable and restart?
Yes. 
alright hope it can be solve. hold on
good luck!
ok restarted. waiting to see whether still will blue screen anot. the Windows7_BSOD_jcgriff2 and HTML file can del?
Yes, you can delete that if you wish. We have no need of it now.
alright,now so far still didnt blue screen.Hope it will remain
That is good news. 
JK the blue screen problem start again!
Quote:
Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.
you go page one of this post.i had already uploaded
Please remove Eset Node32, why did you re-install it? I suspect it the cause since the process running at the time of crash in one of the crash dump is svchost, which can be recognized as virus or malware sometime.
Go to previous page and use uninstall tool Jonathan King provided to uninstall Eset completely
Regard,
Tuan
Go to previous page and use uninstall tool Jonathan King provided to uninstall Eset completely
Code:
BugCheck 1A, {41790, fffffa8000912120, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 ) Followup: MachineOwner --------- PROCESS_NAME: svchost.exe BugCheck 50, {fffffa80660c553b, 0, fffff80002ce65ff, 5} Could not read faulting driver name Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df ) Followup: MachineOwner --------- Tuan
ytd i have uninstall already.But today still blue screen happen
I saw them in the loaded drivers, that means you haven't sucesfully uninstall it my friend. May be I was looking at wrong DMP but I was looking at 4 DMP date 17/8, are those what you got today?
ok i re-upload. hole on
ok newest uploaded
I have seen you not completely remove Eset Node, based on the newest dmp 18/8, I still saw 2 of the drivers which belong to Eset loaded
Code:
fffff880`0121a000 fffff880`0123f000 ehdrv ehdrv.sys Mon Apr 19 13:47:01 2010 (4BCBFC65) fffff880`04600000 fffff880`04621000 epfwwfpr epfwwfpr.sys Mon Apr 19 13:43:18 2010 (4BCBFB86)
then how to remove it?
Did you uninstall Eset first before using the tool JK provided, read this article:
How to uninstall or remove ESET Nod32 antivirus totally?
How to uninstall or remove ESET Nod32 antivirus totally?
use which method?
Please uninstall ESET first. Go to Control Panel>Programs and Features, and the Uninstall ESET.
Then download this tool, and run it: http://download.eset.com/special/ESETUninstaller.exe
Then download this, and install it: http://www.microsoft.com/security_essentials
Then download this tool, and run it: http://download.eset.com/special/ESETUninstaller.exe
Then download this, and install it: http://www.microsoft.com/security_essentials
Check if if uninstalled?.i have upload new minidump
Nope, still installed. 
Download this tool: http://download.eset.com/special/ESETUninstaller.exe
Save it to your computer, then double-click on it. Say "Yes" to any warnings you might get.
Download this tool: http://download.eset.com/special/ESETUninstaller.exe
Save it to your computer, then double-click on it. Say "Yes" to any warnings you might get.
its say ERROR! pc is running in normal boot,please run safe boot or boot live CD/DVD/USB
PRess any key to exit
PRess any key to exit
No problem.
Boot your computer up in Safe Mode. See this tutorial: Safe Mode
Then run the tool again.
Boot your computer up in Safe Mode. See this tutorial: Safe Mode
Then run the tool again.
press what button to go safe mode?i dun understand the steps
1. Reboot the computer.
2. As soon as it shuts down, start pressing F8 as fast as you can. Just keep on pressing it repeatedly until you see a screen that offers you the choice of Safe Mode, Safe Mode with Networking, Normal Mode, and a few more,
3. Use the up and down arrows to select Safe Mode.
4. Press enter.
5. When the desktop is loaded, double-click on the ESET tool you downloaded.
2. As soon as it shuts down, start pressing F8 as fast as you can. Just keep on pressing it repeatedly until you see a screen that offers you the choice of Safe Mode, Safe Mode with Networking, Normal Mode, and a few more,
3. Use the up and down arrows to select Safe Mode.
4. Press enter.
5. When the desktop is loaded, double-click on the ESET tool you downloaded.
it only appear SATA boot and CD DVD boot
ok done.do check isit removed anot thank
Now just wait for more bluescreens.
In the meanwhile, install this: http://www.microsoft.com/security_essentials
If you get more BSODs, upload the new dumps.
In the meanwhile, install this: http://www.microsoft.com/security_essentials
If you get more BSODs, upload the new dumps.
okok thanks.the microsoft anti virus i installed already
Great, let's hope the BSODs stop now.
How often were they occurring before, when you posted for the first time here?
How often were they occurring before, when you posted for the first time here?
Hope so.i ytd scold at google.com and then it come to this website.So i wanna try whether it help me anot.Will know by tmr hahas.
oh no.the BSODs happy again today.What should i do now?.
Please upload the latest dump files. http://www.sevenforums.com/tutorials...en-forums.html
Help check whether anything goes wrong?.newest upload
So whats go wrong now?.
The error code is 1A - MEMORY_MANAGEMENT usually caused by a Device driver, memory, kernel.
The dump does not tell us very much.
I found two obsolete drivers:
point64k.sys Fri May 08 04:53:29 2009 - I cannot find anything on this driver.
viahduaa.sys Thu Jul 09 23:07:01 2009 - VIA High Definition Audio Function Driver, VIA Technologies, Inc. Try to update this one from the Via Technologies website.
I suggest that you test your RAM. 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. If Memtest finds errors with your RAM, they will show up on your screen in red. Report back with the results of Memtest.
The dump does not tell us very much.
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa80009122d0, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041790, The subtype of the bugcheck. Arg2: fffffa80009122d0 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: MsMpEng.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002cf5f9e to fffff80002c82740 STACK_TEXT: fffff880`06df8828 fffff800`02cf5f9e : 00000000`0000001a 00000000`00041790 fffffa80`009122d0 00000000`0000ffff : nt!KeBugCheckEx fffff880`06df8830 fffff800`02cb5df9 : 00000000`00000000 00000000`1da9ffff fffff880`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33906 fffff880`06df89f0 fffff800`02f9b1d0 : fffffa80`073aff80 0007ffff`00000000 fffffa80`08ba5d90 fffffa80`08ba5d90 : nt!MiRemoveMappedView+0xd9 fffff880`06df8b10 fffff800`02f9b5db : 00000980`00000000 00000000`1d6a0000 fffffa80`00000001 00000000`00001001 : nt!MiUnmapViewOfSection+0x1b0 fffff880`06df8bd0 fffff800`02c81993 : 00000000`00000000 00000000`74dee818 fffffa80`08c24350 00000000`0204e7d8 : nt!NtUnmapViewOfSection+0x5f fffff880`06df8c20 00000000`7732fffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0204e428 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7732fffa STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+33906 fffff800`02cf5f9e cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33906 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906 BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906 Followup: MachineOwner --------- point64k.sys Fri May 08 04:53:29 2009 - I cannot find anything on this driver.
viahduaa.sys Thu Jul 09 23:07:01 2009 - VIA High Definition Audio Function Driver, VIA Technologies, Inc. Try to update this one from the Via Technologies website.
I suggest that you test your RAM. 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. If Memtest finds errors with your RAM, they will show up on your screen in red. Report back with the results of Memtest.
The Memtest86+ - Advanced Memory Diagnostic Tool is which?.there is many link.and how to burn into cd?
�� Quote: Originally Posted by samlp 
The Memtest86+ - Advanced Memory Diagnostic Tool is which?.there is many link.and how to burn into cd?
Go to the website and drag to the download section. You can choose either Memtest4.1 or 4.0 (I prefer 4.0 more). Then you use the cd burning tool that Carl listed in the previous post, open that problem and navigate to the memtest file you downloaded, follow the instruction.
Download this: http://memtest.org/download/4.10/mem...+-4.10.iso.zip
Then right-click on it, and select "Burn Disc Image". Insert a blank CD into your CD drive, and after it has detected it, click Burn.
Then right-click on it, and select "Burn Disc Image". Insert a blank CD into your CD drive, and after it has detected it, click Burn.
Dont have Burn Disc Image there
Sorry, I should have clarified.
Double-click on the folder you downloaded, and inside you will see a .ISO file. Drag that to the desktop, and THEN right-click on the ISO file, and select Burn Disc Image.
Double-click on the folder you downloaded, and inside you will see a .ISO file. Drag that to the desktop, and THEN right-click on the ISO file, and select Burn Disc Image.
need to tick verift disce after burning?
Its usually not necessary to verify the disc, but you can if you want to...
alright burn already.what to do now?
Now insert the CD into your computer, and then shut down. Turn it back on, and hopefully Memtest will boot up.
If Windows loads as usual, then press F2 during the initial boot screen, and change the boot priority to have the CD drive boot first.
If Windows loads as usual, then press F2 during the initial boot screen, and change the boot priority to have the CD drive boot first.
What do u mean by*If Windows loads as usual, then press F2 during the initial boot screen, and change the boot priority to have the CD drive boot first*
Put it in your CD ROM, restart your computer. At start up press F2 or Del key to go to BIOS, then change the boot order to your CD ROM-->save change & restart-->your computer will be ready to boot from the CD then
Just hope that the CD drive is set to boot first already.
Reboot the computer while the disc is in the drive, and hopefully it will boot up fine.
Reboot the computer while the disc is in the drive, and hopefully it will boot up fine.
Why when 97% then it will reboot from pass 1% again?
What version of Memtestx86 did you download? Make sure to download 4.0 or 4.1 version
It sounds like you have a bad module(s) there somewhere, do you have 2*2GB? Test them one at a time to see if you can isolate the culprit
It sounds like you have a bad module(s) there somewhere, do you have 2*2GB? Test them one at a time to see if you can isolate the culprit
yups version 4.10 i using 4 x 2gb memory.How to i check whether which faulty?each memory must have 100% pass?
Test individually stick on different slots. It can be bad ram stick or bad motherboard slots. And because you said that testing all of them together go to 97% and restart right? Therefore I suggested to test them individually rightnow instead of together.
cannot be ram slot.because i just 1to 1 exchange for new motherboard last few weeks.Probebly is ram problems i think.1by1 check must be 100% pass isit?
Yep, when you test RAM stick individually, each stick must go through 5 or 6 pass. Everytime it goes through 100%, that means 1 pass is done.
wa which mean its takes alot time.
Không có nhận xét nào:
Đăng nhận xét