hi, sorry if i'm not posting right. i saw the sticky at the top of this forum that give guidelines for posting, however, the app you are supposed to download and wait for up to 10mins to create a report and a new folder doesnt work. i waited for an hour and got nothing but another bsod in that time.
i did run a sys health report and will attach that.
so i've been upgrading my computer a bit recently, new ram, new graphics card, new processor, new psu, new cooling fan.
i'm having frequent system reboots and BSODs. ive read a lot of this may be solved by installing new drivers or checking for updates, but i'm unfamiliar with all of that stuff or how to do it.
i just need some help as this is getting really annoying as frequent as it is.
i did run a sys health report and will attach that.
so i've been upgrading my computer a bit recently, new ram, new graphics card, new processor, new psu, new cooling fan.
i'm having frequent system reboots and BSODs. ive read a lot of this may be solved by installing new drivers or checking for updates, but i'm unfamiliar with all of that stuff or how to do it.
i just need some help as this is getting really annoying as frequent as it is.
Have you run it as administrator? Otherwise you can try this:
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.
yea i tried running as administrator :/ that was what i was doing when nothing happened. i found the minidump folder and i've attached the files.
I suspect that BitDefender is the cause for these BSODs, third party antivirus are notorious BSOD causes. Please remove Bitdefender/Bull Guard for testing
How to uninstall BitDefender
BullGuard Antivirus, Antispyware, Firewall, Spamfilter, Backup and Support - all the security you need in one package!
There are exception codes that indicate memory corruption, Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
BUGCHECK SUMMARY:
If you need alternative protection while not having Bitdefender or Bull guard, you can try MSE, it is known for BSODs free
http://www.microsoft.com/security_essentials
Regard,
Tuan
How to uninstall BitDefender
BullGuard Antivirus, Antispyware, Firewall, Spamfilter, Backup and Support - all the security you need in one package!
There are exception codes that indicate memory corruption, Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
BUGCHECK SUMMARY:
Code:
BugCheck 1, {773802aa, 0, ffff0000, fffff88008e48ca0} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 ) Followup: MachineOwner --------- PROCESS_NAME: vsserv.exe <---Bitdefender/Bull guard BugCheck 1000007E, {ffffffffc0000005, fffff80002f7c4fc, fffff880031b6988, fffff880031b61f0} Probably caused by : ntkrnlmp.exe ( nt!CmpRemoveKeyHash+4c ) Followup: MachineOwner --------- BugCheck 3B, {c0000005, fffff80002fb256d, fffff880057d4750, 0} Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd ) Followup: MachineOwner --------- BugCheck A, {28, 2, 0, fffff80002cc5410} Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 ) Followup: MachineOwner --------- BugCheck 24, {1904fb, fffff88006846bc8, fffff88006846430, fffff80002dab000} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+174 ) Followup: Pool_corruption --------- If you need alternative protection while not having Bitdefender or Bull guard, you can try MSE, it is known for BSODs free
http://www.microsoft.com/security_essentials
Regard,
Tuan
thanks tuan. ill get right on to this and let ya know how it goes
i don't have bit defender. that links says to uninstall using the control panel/add-remove programs. it doesnt show up for me and ive never heard of the program before
i am using AusLogics antivirus. it's always popping up with some error report message and restarting its self
i am using AusLogics antivirus. it's always popping up with some error report message and restarting its self
Yes, the file I indicated in the bugcheck can be the same for many antivirus program and if it belong to AusLogic, then please remove it. Stop code 7E which you see above, as well as exception code c00005 with stop code 3B, are potentially caused by third party antivirus software. Please safely remove it from your system
Removing Software - Tips on How to Uninstall Programs Properly
Removing Software - Tips on How to Uninstall Programs Properly
so which program will not cause bsod's if i cannot use auslogics, bullguard? or MSE?
Please use Microsoft Security Essential, it is free and known for BSODs free. I'm using it and It's great. You can other use AVs later in the future, but for now, we have to get it done so that we can get to different issue
ive deleted auslogics antivirus and installed MSE. while running the first scan with MSE i got another bsod...which turned into 2 back to back. the second happend as i was about to log onto windows after the first. im attaching all files from the minidump again as it has happened several more times.
also i havent yet been able to run the memtest. ill have to get to it when i come back from work.
also i havent yet been able to run the memtest. ill have to get to it when i come back from work.
i talked to a buddy of mine at work. he reminded me that i recently installed a new processor and may need to check on driver information. could this be the problem? i google searched and managed to remove the drivers for my old processor.
i apologize for forgetting this until now. i had originally posted about it, but forgot when i reposted a new thread after seeing the posting guidelines.
i apologize for forgetting this until now. i had originally posted about it, but forgot when i reposted a new thread after seeing the posting guidelines.
ok, so i have had more crashes since i came home. i'm attaching the latest ones. i was able to run the sfc /scannow and i'm including a snippet of that as well. the folder the scan refers to should also be in the zipped folder with the dump files.
the amount of bsods is getting rediculous. i really need help
the amount of bsods is getting rediculous. i really need help
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Please do that, the stop code 50, hardware was blamed
Where do you get the copy of window 7? Did you download it or buy it from store? If window is unable to fix the file, the only option is to do a repair install or might be a clean install. But If the problem is due to hardware, perform repair install or clean install will not help. So let's test the ram first
Please do that, the stop code 50, hardware was blamed
Where do you get the copy of window 7? Did you download it or buy it from store? If window is unable to fix the file, the only option is to do a repair install or might be a clean install. But If the problem is due to hardware, perform repair install or clean install will not help. So let's test the ram first
Code:
BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- BugCheck 3B, {c0000005, fffff80002def90d, fffff88007e241d0, 0} Probably caused by : win32k.sys ( win32k!AllocThreadBufferWithTag+24 ) Followup: MachineOwner --------- BugCheck 3B, {c0000005, fffff80002cccb16, fffff88007a4cb60, 0} Probably caused by : ntkrnlmp.exe ( nt!ExAcquireRundownProtectionCacheAwareEx+26 ) Followup: MachineOwner --------- BugCheck 50, {fffff5000d99e8e6, 0, fffff80002c84995, 7} Could not read faulting driver name Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+40e4b ) Followup: MachineOwner --------- Hmm...the dumps do not point to a specific cause, unfortunately. However, I wonder if is your graphics card causing the problem. Please update your out-dated ATI drivers: Graphics Drivers & Software
Also, remove AVG with this tool: http://download.avg.com/filedir/util...removerx64.exe
Replace it with MSE: http://www.microsoft.com/security_essentials
...Summary of the Dumps:
Also, remove AVG with this tool: http://download.avg.com/filedir/util...removerx64.exe
Replace it with MSE: http://www.microsoft.com/security_essentials
...Summary of the Dumps:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Thu Aug 5 06:39:57.471 2010 (UTC - 4:00) System Uptime: 0 days 0:34:11.172 BugCheck 3B, {c0000005, fffff80002cccb16, fffff88007a4cb60, 0} Probably caused by : ntkrnlmp.exe ( nt!ExAcquireRundownProtectionCacheAwareEx+26 ) BUGCHECK_STR: 0x3B PROCESS_NAME: explorer.exe �������������������������������������������������������������������������������������� Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Thu Aug 5 06:05:04.588 2010 (UTC - 4:00) System Uptime: 0 days 0:07:38.899 BugCheck 50, {fffff5000d99e8e6, 0, fffff80002c84995, 7} Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+40e4b ) BUGCHECK_STR: 0x50 PROCESS_NAME: explorer.exe �������������������������������������������������������������������������������������� Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Thu Aug 5 05:56:28.605 2010 (UTC - 4:00) System Uptime: 0 days 0:11:36.917 BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) BUGCHECK_STR: 0x1E_0 PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Thu Aug 5 06:47:12.103 2010 (UTC - 4:00) System Uptime: 0 days 0:06:26.804 BugCheck 3B, {c0000005, fffff80002def90d, fffff88007e241d0, 0} Probably caused by : win32k.sys ( win32k!AllocThreadBufferWithTag+24 ) BUGCHECK_STR: 0x3B PROCESS_NAME: sidebar.exe �������������������������������������������������������������������������������������� the copy of windows 7 was preinstalled on a prebuilt system i bought from the store. i've since been upgrading hardware - psu, graphics card, ram, cpu.
i tried the iso program and file, but the program would install and then i couldnt find it.
i tried the iso program and file, but the program would install and then i couldnt find it.
Quote:
i tried the iso program and file, but the program would install and then i couldnt find it.
Also, please uninstall AVG as JK suggested, I forgot to mention it earlier (Not sure If I saw it first time, did you just installed it).
how do i remove the old driver before i install the new one for the graphics card?
Use driver sweeper to remove the old driver
ok, thanks everyone for help thus far. i installed avg cuz several buddies at work reminded me of it and i've used it before.
i removed AVG the way recommended.
i installed MSE.
i removed the old ati graphics card drivers and installed the new ones.
i ran memtest successfully finally. - on that note, i only ran through 2 passes, both without errors, but i have other work to do and needed my computer. i highly doubt my ram is the problem. my system is only 2 months old and my ram is only 1 month old within the 2 that i've had the system. 2x4gb sticks takes roughly 2&1/2 hrs to complete 2 passes. but i'm pretty sure thats not the problem.
the graphics drivers seem to be helping lessen the frequency of bsod so far, i will post if more come around.
still if anyone can gather anything from those dump files i'd really appreciate it.
thanks for all help so far. ill be sure to rep when problem is fixed
***sorry, i keep forgetting to mention that i recently replaced the processor. all my system specs are up to date. i think i removed the drivers from the old processor, not sure tho. but the new processor didnt come with any software so i don't know if i have the right drivers for that or if i need to download something else***
i removed AVG the way recommended.
i installed MSE.
i removed the old ati graphics card drivers and installed the new ones.
i ran memtest successfully finally. - on that note, i only ran through 2 passes, both without errors, but i have other work to do and needed my computer. i highly doubt my ram is the problem. my system is only 2 months old and my ram is only 1 month old within the 2 that i've had the system. 2x4gb sticks takes roughly 2&1/2 hrs to complete 2 passes. but i'm pretty sure thats not the problem.
the graphics drivers seem to be helping lessen the frequency of bsod so far, i will post if more come around.
still if anyone can gather anything from those dump files i'd really appreciate it.
thanks for all help so far. ill be sure to rep when problem is fixed
***sorry, i keep forgetting to mention that i recently replaced the processor. all my system specs are up to date. i think i removed the drivers from the old processor, not sure tho. but the new processor didnt come with any software so i don't know if i have the right drivers for that or if i need to download something else***
had another BSOD. they are becoming less frequent since i updated graphics driver. ill attach dump file from most recent since the last one.
had another one right after last post. attached dump file
had another one right after last post. attached dump file
bump; for anyone who knows about this stuff
You don't need to bump. Please be patient. It takes a little time to look through a dump and research drivers. 
Unfortunately, this dump does not tell us much; but it points to a device driver.
I find the following outdated drivers:
ALSysIO64.sys Sun Apr 19 15:41:04 2009 - driver file used to run Core Temp on Vista x64. it is from the company Arthur Liberman belonging to product ALSysIO64.
GEARAspiWDM.sys Mon May 18 08:17:04 2009 - CDRom Class Filter Driver or Filter Driver for 2k and XP or CD/DVD Class Filter Driver or CD DVD Filter or GEAR ASPI Filter Driver belongs to the software GEAR.wrks or GEAR CDRom Filter or GEARAspi or GEARAspiWDM or Norton Ghost or MixMeister Studio Demo or MixMeister Pro or GEAR 32bit Driver Installer or MixMeister CD-R Drivers or Drive Image or Norton Save and Restore or CD DVD Filter or GearDrvs or iTunes or GEAR ASPI Filter Driver or GEAR driver installer for x by GEAR Software Inc (www.gearsoftware.com).
LHidFilt.Sys Wed Jun 17 12:49:39 2009 - Logitech mouse driver Downloads
LMouFilt.Sys Wed Jun 17 12:49:43 2009 - Logitech mouse driver Downloads
Update these drivers from the manufacturers' websites. If you need help, let us know. After you update these drivers, please enable Driver Verifier: Driver Verifier - Enable and Disable Driver Verifier will cause BSOD's when it finds a faulty driver.
Unfortunately, this dump does not tell us much; but it points to a device driver.
Quote:
STOP 0x00000019: BAD_POOL_HEADER
Usual causes: Device driver
Usual causes: Device driver
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {22, fffffa800787c000, 0, 0} GetPointerFromAddress: unable to read from fffff80002eb90e0 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 ) Followup: MachineOwner ALSysIO64.sys Sun Apr 19 15:41:04 2009 - driver file used to run Core Temp on Vista x64. it is from the company Arthur Liberman belonging to product ALSysIO64.
GEARAspiWDM.sys Mon May 18 08:17:04 2009 - CDRom Class Filter Driver or Filter Driver for 2k and XP or CD/DVD Class Filter Driver or CD DVD Filter or GEAR ASPI Filter Driver belongs to the software GEAR.wrks or GEAR CDRom Filter or GEARAspi or GEARAspiWDM or Norton Ghost or MixMeister Studio Demo or MixMeister Pro or GEAR 32bit Driver Installer or MixMeister CD-R Drivers or Drive Image or Norton Save and Restore or CD DVD Filter or GearDrvs or iTunes or GEAR ASPI Filter Driver or GEAR driver installer for x by GEAR Software Inc (www.gearsoftware.com).
LHidFilt.Sys Wed Jun 17 12:49:39 2009 - Logitech mouse driver Downloads
LMouFilt.Sys Wed Jun 17 12:49:43 2009 - Logitech mouse driver Downloads
Update these drivers from the manufacturers' websites. If you need help, let us know. After you update these drivers, please enable Driver Verifier: Driver Verifier - Enable and Disable Driver Verifier will cause BSOD's when it finds a faulty driver.
so sorry about the bump. i just know theres a lot of bsod threads and things get overlooked. especially when its late at night like it is where i am.
i'm not really familiar with updating drivers and removing old ones and am going to need some help please
i'm not really familiar with updating drivers and removing old ones and am going to need some help please
First you go to the websites and search for the drivers for your particular hardware or software. Download the latest drivers to your desktop. Open device manager, locate your mouse, and uninstall the current driver. Go to your desktop and install the new driver.
For the software drivers, go the the website and see if there is a newer version of the software or an update available. Download and install it. Let me know if you cannot find the drivers or software.
I suggest creating a system restore point before updating. If something goes wrong in the installation, you can roll back to that restore point.
For the software drivers, go the the website and see if there is a newer version of the software or an update available. Download and install it. Let me know if you cannot find the drivers or software.
I suggest creating a system restore point before updating. If something goes wrong in the installation, you can roll back to that restore point.
ok, i deleted core temp.
i found an update for the software for the mouse. uninstalled the setpoint software and installed new after reboot. not sure if that updates the driver for the mouse.
and the "gear" list you have up there...nothing is familiar except itunes. i found the driver on the website and downloaded it, but havent installed yet because i don't know what that driver is for or where i would go to look for and uninstall the old one.
i found an update for the software for the mouse. uninstalled the setpoint software and installed new after reboot. not sure if that updates the driver for the mouse.
and the "gear" list you have up there...nothing is familiar except itunes. i found the driver on the website and downloaded it, but havent installed yet because i don't know what that driver is for or where i would go to look for and uninstall the old one.
ok so i went ahead and installed the driver from the gear software website. i just got done running driver verifier for the first time. i didnt even get to logon before it bsod'd. i'm including the latest dump file
Good job on updating the drivers. Well done.
The Driver Verifier dumps blames HIDCLASS.SYS as the problem driver. This is an Microsoft driver and it is up to date; but it could be corrupt. I am going to ask for help on this one from a fresh pair of eyes.
I still see the gear driver showing up in the dump as an outdated driver: GEARAspiWDM.sys Mon May 18 08:17:04 2009
And i must have missed this one before: nvmf6264.sys Thu Jul 30 19:48:18 2009 Thu Jul 30 19:48:18 2009. This is an NVidia network adapter driver. This could well be causing problems. Update this driver from Drivers - Download NVIDIA Drivers
Turn off Driver Verifier and update the Nvidia driver. Reboot leaving Driver Verifier off and lets see what your system does.
The Driver Verifier dumps blames HIDCLASS.SYS as the problem driver. This is an Microsoft driver and it is up to date; but it could be corrupt. I am going to ask for help on this one from a fresh pair of eyes.
I still see the gear driver showing up in the dump as an outdated driver: GEARAspiWDM.sys Mon May 18 08:17:04 2009
And i must have missed this one before: nvmf6264.sys Thu Jul 30 19:48:18 2009 Thu Jul 30 19:48:18 2009. This is an NVidia network adapter driver. This could well be causing problems. Update this driver from Drivers - Download NVIDIA Drivers
Turn off Driver Verifier and update the Nvidia driver. Reboot leaving Driver Verifier off and lets see what your system does.
driver verifier is off and i've rebooted since then. i honestly don't know what that gear driver is because i didnt buy my computer until June of 2010 this year.
problem with the Nvidia driver. i looked up what i have online which is the motherboard chipset NVIDIA GeForce 6150SE nForce 430. i found the driver for that on the nvidia website you gave me. during setup i get an error message when installshield starts saying something to the effect of,
"nvidia setup could not locate any drivers that are compatible with your current hardware" and then setup exits.
problem with the Nvidia driver. i looked up what i have online which is the motherboard chipset NVIDIA GeForce 6150SE nForce 430. i found the driver for that on the nvidia website you gave me. during setup i get an error message when installshield starts saying something to the effect of,
"nvidia setup could not locate any drivers that are compatible with your current hardware" and then setup exits.
Try installing it in the safe mode.
For the Gear driver, navigate to c:\Windows\System32\Drivers. Find GEARAspiWDM.sys and rename it to GEARAspiWDM.old. This way it will be easy to recover if you need it.
For the Gear driver, navigate to c:\Windows\System32\Drivers. Find GEARAspiWDM.sys and rename it to GEARAspiWDM.old. This way it will be easy to recover if you need it.
had another bsod. they're few and far between now. i'm attaching the latest dump file
This dump is error code 3B. Unfortunately, it does not tell us much.
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
I did put out a request for help with your NVidia drivers. Someone will be along with suggestions.
While I still think it is a driver issue, let's 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. Errors, if any, will show up in red. Post back with the results.
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
I did put out a request for help with your NVidia drivers. Someone will be along with suggestions.
While I still think it is a driver issue, let's 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. Errors, if any, will show up in red. Post back with the results.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_080610-15568-01.zip\080610-15568-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 Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e4ce50 Debug session time: Thu Aug 5 19:32:40.706 2010 (GMT-4) System Uptime: 0 days 1:12:48.017 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002c82805, fffff880081816d0, 0} Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002c82805, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880081816d0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!ExpInterlockedPopEntrySListFault16+0 fffff800`02c82805 498b08 mov rcx,qword ptr [r8] CONTEXT: fffff880081816d0 -- (.cxr 0xfffff880081816d0) rax=00000003e998002c rbx=0000000000000000 rcx=fffff88002fd66c0 rdx=ff7ff8a010ab8601 rsi=fffff88002fd66c0 rdi=0000000000000001 rip=fffff80002c82805 rsp=fffff880081820a0 rbp=fffffa8006696000 r8=ff7ff8a010ab8600 r9=fffff80002c0f000 r10=fffff88002fd66c0 r11=0000000000000000 r12=0000000000000003 r13=0000000000000000 r14=0000000000000002 r15=000000004b466650 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!ExpInterlockedPopEntrySListFault16: fffff800`02c82805 498b08 mov rcx,qword ptr [r8] ds:002b:ff7ff8a0`10ab8600=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: MsMpEng.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002c82805 STACK_TEXT: fffff880`081820a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16 FOLLOWUP_IP: nt!ExpInterlockedPopEntrySListFault16+0 fffff800`02c82805 498b08 mov rcx,qword ptr [r8] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ExpInterlockedPopEntrySListFault16+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb STACK_COMMAND: .cxr 0xfffff880081816d0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0 BUCKET_ID: X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0 Followup: MachineOwner --------- This dump is error code 3B
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
While I still think it is a driver issue, let's 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. Errors, if any, will show up in red. Post back with the results.
Good news, you did successfully update the NVidia drivers. nvmf6264.sys Thu Jul 30 19:48:18 2009. This is up to date.
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
While I still think it is a driver issue, let's 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. Errors, if any, will show up in red. Post back with the results.
Good news, you did successfully update the NVidia drivers. nvmf6264.sys Thu Jul 30 19:48:18 2009. This is up to date.
it seems to happen when i leave the computer alone for a time while i try to get some sleep. i come back to check on it and it has rebooted. ill attach the dump file again, but it keeps doing it for sure. again, my ram is only a month old and my system is only 2 months old. so i agree, i think its a driver issue, but ill run memtest for a while an see what we come up with.
***hold up***
so i went to go do the memtest right? well, my dvd-rw drive isnt listed on my computer any more and its like it just disappeared from the system?
edit: i went back to the gear software website from earlier and tried redownloading and installing the drivers again. i rebooted afterwards and still nothing
so i went to go do the memtest right? well, my dvd-rw drive isnt listed on my computer any more and its like it just disappeared from the system?
edit: i went back to the gear software website from earlier and tried redownloading and installing the drivers again. i rebooted afterwards and still nothing
Check to see if the DVD drive is displayed in the BIOS. If not, make sure that the drive is plugged in securely.
ok so i checked the bios and the dvd drive is still showing up. in the bios it calls it "HP DDVDW-TS-H653R". i'm sure its still connected well. i upgraded hardware only 4 days ago and havent done anything that would have made the plug come loose. plus i made sure everything was connected right.
when i was logging back on to windows i got 2 bsod's back to back. i'm attaching the dump files.
also, if there are any other reports or files to upload that could help i'm more than willing to go find what needs to be found.
when i was logging back on to windows i got 2 bsod's back to back. i'm attaching the dump files.
also, if there are any other reports or files to upload that could help i'm more than willing to go find what needs to be found.
another one happened just randomly while i was surfing the web.
Please follow these directions: http://www.sevenforums.com/crashes-d...tructions.html
No need to start a new thread, just attach the output folder to your next post.
No need to start a new thread, just attach the output folder to your next post.
sorry. i tried to follow those instructions when i started the thread, but the program wouldnt run properly.
it worked this time, thanks. i'm attaching those files
-64bit windows 7 home premium
-it is the original installed OS
-its an OEM version. i have a retail version on hand that i installed on a previous laptop. that laptop died. (RIP sony vaio LoL)
-system is 2 months old since i bought it from the store. (pre built, box system) however, i've installed new psu, cpu, cpu fan, graphics card, and ram. the new cpu fan doesn't plug into the motherboard which causes it not to boot. so i plugged the old heatsink into the mobo as well and just set it down inside the case.
*hardware age is all 1month or less
-OS age is 2 months. never re-installed since purchase
it worked this time, thanks. i'm attaching those files
-64bit windows 7 home premium
-it is the original installed OS
-its an OEM version. i have a retail version on hand that i installed on a previous laptop. that laptop died. (RIP sony vaio LoL)
-system is 2 months old since i bought it from the store. (pre built, box system) however, i've installed new psu, cpu, cpu fan, graphics card, and ram. the new cpu fan doesn't plug into the motherboard which causes it not to boot. so i plugged the old heatsink into the mobo as well and just set it down inside the case.
*hardware age is all 1month or less
-OS age is 2 months. never re-installed since purchase
i went out for a while and left the computer on so i'm assuming the system was idle. i came back to find that it had crashed again. i'll attach the dump file.
anyone get anything from the files in the last post possibly?
anyone get anything from the files in the last post possibly?
my dvd-rw drive is still missing in "my computer." the bios called it an "HP DDVDW-TS-H653R."
See if the drive shows up in Disk Management. Enter diskmgmt.msc into the start menu.
Also, make sure it has a unique drive letter: http://www.sevenforums.com/tutorials...ndows-7-a.html
Also, make sure it has a unique drive letter: http://www.sevenforums.com/tutorials...ndows-7-a.html
True - if you don't see it there, open a cmd prompt and run diskpart, then list disk.
when i change it back and reboot, its there again, working fine, able to be used. its also back under my computer with a drive letter assigned to it (E: ).
also still wondering if anyone knows anything from those reports 4 and 5 posts ago?
edit: nearly all bsod's are gone, or havent had one in a while. i changed the file back to use my dvd drive for memtest. made it through 7 passes with no problems. also ran chkdsk and everything came back ok.
ok so this morning, roughly 10 hours ago, i changed that file back to the way it was originally. i havent had any BSOD's untill just a moment ago.
i was playing flight sim X and i landed a helicopter on a tree and thats when the bsod happened (LoL).
let me know if anyone requires more info. i will attach the most recent minidump file.
i was playing flight sim X and i landed a helicopter on a tree and thats when the bsod happened (LoL).
let me know if anyone requires more info. i will attach the most recent minidump file.
LOL - maybe the system is just trying to help your flying skills? 
It still appears your graphics card is the cause. Since we have just about eliminated the possibility of a driver issue, we are left with hardware.
Monitor your temps with Speedfan while you game.
If you have another GFX card to try, please do. If you can borrow one from a friend's computer, great.
Let's get that Memtest out of the way too. Use this download to create a bootable USB thumb drive: http://memtest.org/download/4.10/mem....installer.zip
Monitor your temps with Speedfan while you game.
If you have another GFX card to try, please do. If you can borrow one from a friend's computer, great.
Let's get that Memtest out of the way too. Use this download to create a bootable USB thumb drive: http://memtest.org/download/4.10/mem....installer.zip
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff88004375ffb, fffff88002131698, fffff88002130f00} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab ) �������������������������������������������������������������������������������������� I am glad that memtest found no errors. That lets you know that your RAM is fine. Good news with checkdsk, also. You now now that Gear driver is necessary for your dvd drive. So for the time being, we will leave that alon.
Your latest dump is another error code 7E and it directly blames direct X. Corrupted memory is involved.
Your video adapter (drivers) can cause this; but your drivers are now up to date. I am going to call for more help. I am out of ideas. Excellent, Jonathan picked it up while I was typing. Thanks, Jonathan.
Your latest dump is another error code 7E and it directly blames direct X. Corrupted memory is involved.
Quote:
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_080810-18766-01.zip\080810-18766-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e96e50 Debug session time: Sat Aug 7 11:48:46.123 2010 (GMT-4) System Uptime: 0 days 3:01:51.434 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff88004375ffb, fffff88002131698, fffff88002130f00} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88004375ffb, The address that the exception occurred at Arg3: fffff88002131698, Exception Record Address Arg4: fffff88002130f00, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab fffff880`04375ffb 488b4108 mov rax,qword ptr [rcx+8] EXCEPTION_RECORD: fffff88002131698 -- (.exr 0xfffff88002131698) ExceptionAddress: fffff88004375ffb (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x00000000000000ab) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000088 Attempt to read from address 0000000000000088 CONTEXT: fffff88002130f00 -- (.cxr 0xfffff88002130f00) rax=fffffa800a7de1d0 rbx=fffff8a00f5a57b0 rcx=0000000000000080 rdx=0000000000000060 rsi=fffffa8006a84c40 rdi=fffffa8008b0c000 rip=fffff88004375ffb rsp=fffff880021318d0 rbp=0000000000000000 r8=fffffa8006a84c90 r9=fffff88002131901 r10=0000000000000000 r11=fffffa8008a6f410 r12=0000000000000060 r13=0000000000000000 r14=fffffa800a915490 r15=0000000000000a2d iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xab: fffff880`04375ffb 488b4108 mov rax,qword ptr [rcx+8] ds:002b:00000000`00000088=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000088 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f010e0 0000000000000088 FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab fffff880`04375ffb 488b4108 mov rax,qword ptr [rcx+8] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff880043738af to fffff88004375ffb STACK_TEXT: fffff880`021318d0 fffff880`043738af : 00000000`00000000 fffffa80`0a807300 00000000`0000008b fffffa80`0a9d8908 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xab fffff880`02131910 fffff880`0438d65d : 00000000`00000000 fffff8a0`0a8ea210 fffffa80`00000000 fffffa80`0a915490 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b fffff880`02131ae0 fffff880`0438d398 : fffff880`009ecf40 fffff880`0438cd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`02131cd0 fffff880`0438ce96 : 00000000`00000000 fffffa80`0901d4a0 00000000`00000080 fffffa80`08a6f410 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`02131d00 fffff800`02f6ea86 : 00000000`024b2590 fffffa80`08728b60 fffffa80`066e3b30 fffffa80`08728b60 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`02131d40 fffff800`02ca7b06 : fffff880`009e8180 fffffa80`08728b60 fffff880`009f2fc0 fffff880`01218534 : nt!PspSystemThreadStartup+0x5a fffff880`02131d80 00000000`00000000 : fffff880`02132000 fffff880`0212c000 fffff880`02131690 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578 STACK_COMMAND: .cxr 0xfffff88002130f00 ; kb FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab Followup: MachineOwner ---------
well, i don't have another gfx card and i don't think most of my buddies use desktops.
i'd like to note that at the time of that crash i was running flight sim x, i had gone into the ati catalyst control center and bumped all the advanced settings up to highest quality.
i downloaded speedfan and figured out how to "log" and minimize to tray. ill leave it up during next gaming.
i got the flash drive done and i'm about to reboot.
also a short while ago the system crashed again. ill include the minidump file
i'd like to note that at the time of that crash i was running flight sim x, i had gone into the ati catalyst control center and bumped all the advanced settings up to highest quality.
i downloaded speedfan and figured out how to "log" and minimize to tray. ill leave it up during next gaming.
i got the flash drive done and i'm about to reboot.
also a short while ago the system crashed again. ill include the minidump file
That still might be a heat issue. Be sure to leave the Catalyst setting on Highest Quality, and test them.
ok
i've already done the memtest for a full night. 7 passes, no probs.
ill try again tomorrow with ati and flight sim, see if it happens.
i'm hittin the sack now. ill keep you guys posted.
i've already done the memtest for a full night. 7 passes, no probs.
ill try again tomorrow with ati and flight sim, see if it happens.
i'm hittin the sack now. ill keep you guys posted.
See you tomorrow and we will work on it some more.
i havent been able to replicate the crash while gaming yet. but i did wake up this morning and found it had crashed during the night. but the computer has been fine all day. ill attach the latest dump file
Stop code 19, which usually caused by device driver
To know what exactly driver causing this, I suggest to enable Driver Verifier:
Driver Verifier - Enable and Disable
Did you just leave it on during the night or leave something running at the night (games ??)
To know what exactly driver causing this, I suggest to enable Driver Verifier:
Driver Verifier - Enable and Disable
Did you just leave it on during the night or leave something running at the night (games ??)
Code:
BugCheck 19, {3, fffff8a00affac40, fffff8a00affac40, ff7ff8a00affac40} Probably caused by : Pool_Corruption ( nt!ExFreePool+75b ) Followup: Pool_corruption --------- PROCESS_NAME: System yea, i just left it running. no programs open, nothing. thats what i usually do.
i ran the device verifier. it went through 2 blue screens each before i could log on to windows. finally got back to normal. i'll attach those dump files.
also, since i updated my logitech setpoint softwar and driver for my mouse, the software update icon is always in the system tray saying there's a new update. its always the same size file, and as soon as i supposedly download and install it, its there again, like nothing happened.
any thoughts? could this be the problem?
also, i've had to use my dvd drive since the gear driver renaming...so i've since changed it back and just left it so i can use my dvd drive.
i ran the device verifier. it went through 2 blue screens each before i could log on to windows. finally got back to normal. i'll attach those dump files.
also, since i updated my logitech setpoint softwar and driver for my mouse, the software update icon is always in the system tray saying there's a new update. its always the same size file, and as soon as i supposedly download and install it, its there again, like nothing happened.
any thoughts? could this be the problem?
also, i've had to use my dvd drive since the gear driver renaming...so i've since changed it back and just left it so i can use my dvd drive.
Just leave the Gear driver for the time being and don't worry about it.
Continue to let Driver Verifier run for another 12 hours or so. One of the dumps blamed HIDCLASS.SYS which is a Microsoft USB driver. It is not like to be a faulty driver. The second dump blamed hardware and did not give us a driver.
Continue to let Driver Verifier run for another 12 hours or so. One of the dumps blamed HIDCLASS.SYS which is a Microsoft USB driver. It is not like to be a faulty driver. The second dump blamed hardware and did not give us a driver.
ok ill give it a try. i would like to let you know, my computer's been on all day without 1 crash. i think we might have taken care of the bulk of the problems.
ill let you guys know about leavin the driver verifier on.
ill let you guys know about leavin the driver verifier on.
well, sorry...work has gotten busy. tropical storm coming up towards Korea. anyways,
i never did run driver verifier all night long. every time i would leave it, the computer would just sit at the log on screen not doing anything. so i tried logging on a handful of times, and every time it would never finish logging on before going to blue screen.
i managed to see at the bottom nearly every time some reference about HIDCLASS.sys
i never did run driver verifier all night long. every time i would leave it, the computer would just sit at the log on screen not doing anything. so i tried logging on a handful of times, and every time it would never finish logging on before going to blue screen.
i managed to see at the bottom nearly every time some reference about HIDCLASS.sys
I suspect your Logitech Setpoint drivers are the cause. Are your mice/keyboard batteries fresh? Could you possibly remove them and try a different set?
...Summary of the Dumps:
...Summary of the Dumps:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Tue Aug 10 10:32:30.635 2010 (UTC - 4:00) System Uptime: 0 days 0:00:38.978 BugCheck C9, {23b, fffff88005967818, fffff980099fadc0, 0} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 ) BUGCHECK_STR: 0xc9_23b DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Tue Aug 10 10:37:21.500 2010 (UTC - 4:00) System Uptime: 0 days 0:01:16.232 BugCheck C9, {23b, fffff88005938818, fffff9800dfa4dc0, 0} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 ) BUGCHECK_STR: 0xc9_23b DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Tue Aug 10 10:35:03.268 2010 (UTC - 4:00) System Uptime: 0 days 0:00:41.001 BugCheck C9, {23b, fffff88005967818, fffff98009c48dc0, 0} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 ) BUGCHECK_STR: 0xc9_23b DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Mon Aug 9 13:55:55.052 2010 (UTC - 4:00) System Uptime: 0 days 4:30:15.753 BugCheck 3B, {c0000005, fffff80002db50bf, fffff88008633770, 0} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 ) BUGCHECK_STR: 0x3B PROCESS_NAME: rundll32.exe �������������������������������������������������������������������������������������� i hate to be the bearer of bad news, but i use wired mice and keyboard. no batteries :/
and i had another crash.
and i had another crash.
This one shows an AFD callback trying to retrieve data from a pointer in the RDX register via AfdFastConnectionReceive, but that of course is invalid (and given it's a kernel-mode driver, you get a bugcheck). Given history (I've seen many of these before) and the fact it's crashing in a network application that would be stressing some of these features (azureus), the most likely culprit is the network driver not handling offload well. I would update it to the latest version if you've not done so already, and then you would want to run the commands below to disable the tcp chimney / offloading feature to see if that helps.
Commands to run:
netsh interface tcp set global rss=disabled
netsh interface tcp set global chimney=disabled
netsh interface tcp set global netdma=disabled
netsh interface tcp set global autotuninglevel=disabled
You may also wish to reset your winsock provider to it's defaults, although this one can potentially break applications with LSPs installed on the system:
netsh winsock reset
Code:
// network driver from 2009, probably old considering it's nvidia: 1: kd> lmvm nvmf6264 start end module name fffff880`04178000 fffff880`041c9500 nvmf6264 (deferred) Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys Image name: nvmf6264.sys Timestamp: Thu Jul 30 19:48:18 2009 (4A723142) CheckSum: 0005B9A8 ImageSize: 00051500 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
netsh interface tcp set global rss=disabled
netsh interface tcp set global chimney=disabled
netsh interface tcp set global netdma=disabled
netsh interface tcp set global autotuninglevel=disabled
You may also wish to reset your winsock provider to it's defaults, although this one can potentially break applications with LSPs installed on the system:
netsh winsock reset
ok, where would i go to update that network driver? i'm not very familiar with crash dumps and this stuff.
ok, do i need to remove the old ones as well? and what cluberti said about those commands to run...what do they do and do you mean just type those into cmd.exe?
Run cmd.exe as an administrator and type those commands in at the prompt.
Download the updated drivers to your desktop. Through device manager, uninstall the old driver(s). Install the new ones. Reboot.
Download the updated drivers to your desktop. Through device manager, uninstall the old driver(s). Install the new ones. Reboot.
ok, i got the command prompts done and the network drivers updated. haven't had any crashes yet, but that was only 30 mins ago roughly.
before i got those done, there were 2 bsod's today, but now after doing those things the crash dumps from earlier are gone...?
thanks again everyone for your continued support
before i got those done, there were 2 bsod's today, but now after doing those things the crash dumps from earlier are gone...?
thanks again everyone for your continued support
Very good and thanks for the update and for following suggestions. Good job. We hope your BSOD problems are gone, Make sure your system is still configured for mini dumps and keep us updated.
thanks, i hope they're gone too.
how do i make sure my system is still configured for minidumps?
how do i make sure my system is still configured for minidumps?
SET MINIDUMPS:
Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Is that what you asked for?
Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Is that what you asked for?
yes that is! thanks ttran
socrgy, post back tomorrow and update us. If you are still running without crashes, we will ask the mods to mark this thread as solved.
And by the way, thank you for your service!
And by the way, thank you for your service!
well, i had a few when i customized the ati catalyst control center 3d graphics back up to their highest, but there's no files in the minidump folder. i canned the custom settings in CCC and went with just highest quality on the slider bar and everything is running fine. no bsod's since then.
your welcome. i love my job
your welcome. i love my job
ok. i've downloaded a trial of WoW for craps and giggles and everytime i start playing, roughly 15-20 mins in the system crashes to bsod.
i realized i'd done something wrong which was why i wasnt getting any minidump files. i got that fixed and im attaching the latest.
i realized i'd done something wrong which was why i wasnt getting any minidump files. i got that fixed and im attaching the latest.
It blamed your graphic card with little mentioning to your memory with exception code fffffc0000005, which is memory access violation.
I haven't turned back to previous pages to see if any one ever told you to re-install the graphic card driver yet, but it looks like the graphic card is having problem. The best way to check it is to try if you can borrow another graphic card adapter and try on yours system.
If you want to try re-install graphic card driver again. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Check you RAM again if you wants.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
BUGCHECK SUMMARY:
Regard,
Tuan
I haven't turned back to previous pages to see if any one ever told you to re-install the graphic card driver yet, but it looks like the graphic card is having problem. The best way to check it is to try if you can borrow another graphic card adapter and try on yours system.
If you want to try re-install graphic card driver again. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Check you RAM again if you wants.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
BUGCHECK SUMMARY:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.700\081410-12776-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*e:\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 Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e96e50 Debug session time: Sat Aug 14 11:07:33.097 2010 (UTC + 7:00) System Uptime: 0 days 0:13:04.798 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff880043efd38, fffff88002137858, fffff880021370c0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+1c ) Followup: MachineOwner --------- Tuan
ok. i downloaded that program, removed all drivers and re downloaded and installed the new drivers.
still having bsods, ill attach all the latest.
bsods only while gaming. playing free trial of WoW
i can start a new thread if it will help. i believe the original problem has been fixed. i'm looking into getting a new graphics card. possibly two since the new mobo i just ordered can handle it
still having bsods, ill attach all the latest.
bsods only while gaming. playing free trial of WoW
i can start a new thread if it will help. i believe the original problem has been fixed. i'm looking into getting a new graphics card. possibly two since the new mobo i just ordered can handle it
Definitely the graphic card, Let's try different graphic card then Same stop code as the previous one with dxgmms1.sys (Directx) as well as your graphic card driver were blamed.
BUGCHECK SUMMARY:
Same stop code as the previous one with dxgmms1.sys (Directx) as well as your graphic card driver were blamed.BUGCHECK SUMMARY:
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff88004578ce5, fffff880021306a8, fffff8800212ff10} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 ) Followup: MachineOwner --------- BugCheck 3B, {c0000005, fffff88004bef70e, fffff88006c9f7e0, 0} Unable to load image atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+35e70e ) Followup: MachineOwner --------- BugCheck 3B, {c0000005, fffff80002cb8863, fffff8800824b0b0, 0} Probably caused by : ntkrnlmp.exe ( nt!EtwpFindGuidEntryByGuid+73 ) Followup: MachineOwner --------- BugCheck C2, {b, fffffa80085f9070, c, fffffa80085f9e00} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 ) Followup: MachineOwner --------- BugCheck 1E, {0, 0, 0, 0} Unable to load image atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d ) Followup: MachineOwner --------- dang!! well, i've got a new case and mobo on the way. i've actually had so much trouble with this wow trial that i've ordered 2 new vid cards the mobo can handle. thanks tran! ill let eveyone know when i get the new gfx card and mobo installed.
so i got tired of having my computer bsod in mid gaming and took out my graphics card and have been just using the integrated mobo graphics. still having random reboots. not always bsod, but the computer will black screen and reboot.
i'm going to include all minidumps from the past 2 days, i'm pretty sure most of them will be about the graphics card since i just took it out last night.
i'm going to include all minidumps from the past 2 days, i'm pretty sure most of them will be about the graphics card since i just took it out last night.
Did you mess with the page file at all? I see a PF date of 2010/08/01 (the first of this month). Original OS install date is 6/12/2010. The latter number agrees with the date you bought the computer.
Page File is allocated 8191 MB. You have 8192 MB RAM. The recommended page file size for your amount of RAM (3x) is 24GB.
Is the page file set to System Managed? If not, you should set it that way.
We suspect your outdated nForce networking drivers are the cause, but no updates can be found for your chipset.
I suggest giving these drivers a try: http://us.download.nvidia.com/Window...ional_whql.exe
No guarantees, those are for the nForce 5 series, and you have the nForce 4 chipset.
You may contact HP for support here. Is the computer still under warranty? You may see if they will replace your motherboard with a newer one.
...Summary of the Dumps:
Page File is allocated 8191 MB. You have 8192 MB RAM. The recommended page file size for your amount of RAM (3x) is 24GB.
Is the page file set to System Managed? If not, you should set it that way.
We suspect your outdated nForce networking drivers are the cause, but no updates can be found for your chipset.
I suggest giving these drivers a try: http://us.download.nvidia.com/Window...ional_whql.exe
No guarantees, those are for the nForce 5 series, and you have the nForce 4 chipset.
You may contact HP for support here. Is the computer still under warranty? You may see if they will replace your motherboard with a newer one.
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Wed Aug 18 05:14:40.364 2010 (UTC - 4:00) System Uptime: 0 days 5:59:55.722 BugCheck 3B, {c0000005, fffff80002f9574d, fffff88004d11770, 0} Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd ) BUGCHECK_STR: 0x3B PROCESS_NAME: MsMpEng.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Wed Aug 18 05:23:55.044 2010 (UTC - 4:00) System Uptime: 0 days 0:08:43.777 BugCheck 3B, {c0000005, fffff80002f44304, fffff88005679cb0, 0} Probably caused by : ntkrnlmp.exe ( nt!CmpDeleteKeyObject+184 ) BUGCHECK_STR: 0x3B PROCESS_NAME: chrome.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 23:14:09.938 2010 (UTC - 4:00) System Uptime: 0 days 13:41:54.670 BugCheck 1E, {0, 0, 0, 0} Probably caused by : storport.sys ( storport!RaidpAdapterTimerDpcRoutine+38 ) BUGCHECK_STR: 0x1E_0 PROCESS_NAME: System �������������������������������������������������������������������������������������� well, i remember messing with the page filing to try and solve a computer issue some weeks ago in a different thread, although i don't remember exactly when. at the end of it all, i reset the page filing to system managed and then checked the check box at the top that says "automatically manage paging file size for all drives."
as of now it says its set at 7935mb
i installed the driver you posted and ill change the paging file to 24Gb
as of now it says its set at 7935mb
i installed the driver you posted and ill change the paging file to 24Gb
Very good. Let us know what happens.
�� Quote: Originally Posted by Jonathan_King 
Page File is allocated 8191 MB. You have 8192 MB RAM. The recommended page file size for your amount of RAM (3x) is 24GB.
The more RAM you have in Windows 7, the smaller the paging file needed - you want to base your paging file based on workload and usage of committed virtual memory, rather than use the old NT4 algorithms. I've posted here the ways to determine this, but basically, these old paging file algorithm recommendation are nonsense, especially on x64 systems with 6GB+ RAM. Run your box as you would at it's hardest, and check your peak system commit in process explorer, and see how high it is. If it's less than total RAM, you could probably run without a paging file entirely, although having at least a smallish one (512MB, 1GB) can be a nice safety net for crash dumps or to back modified private memory as necessary (files on disk, images, mapped files, etc).
If you have 8GB of RAM, you really do NOT want to create a 24GB paging file, but follow some of Mark Russinovich's guidelines - test the system's load, and pad if you need it. Don't just pick an algorithm from forever ago and blindly use it.
ok so either way on the paging file i still have random shutdowns while gaming.
i've got paging file set as system managed size without the checkbox checked at the top to auto manage size for all drives.
its still currently allocated at 7935mb
i'm still running my integrated graphics nvidia geforce 6150 SE nforce 430.
attaching dump files, let me know if theres anything else to try.
as of now just waiting on new mobo, gfx cards and case to arrive. <-- will those new parts solve the problems possibly?
ive also been considering just re-installing windows 7 from the ground up and then restoring my system image from backup...could that do any good?
i've got paging file set as system managed size without the checkbox checked at the top to auto manage size for all drives.
its still currently allocated at 7935mb
i'm still running my integrated graphics nvidia geforce 6150 SE nforce 430.
attaching dump files, let me know if theres anything else to try.
as of now just waiting on new mobo, gfx cards and case to arrive. <-- will those new parts solve the problems possibly?
ive also been considering just re-installing windows 7 from the ground up and then restoring my system image from backup...could that do any good?
Well, these are all over the place. The first dump is a nvidia timer crash (DirectX timed out waiting for the driver to respond, causing an expected crash), the second is a pool corruption crash (the kernel was told to ExAllocatePoolWithTag, but the memory address in pool that was attempted to be allocated was invalid or corrupt), and the third is a register fail caused either by a filter driver or a pool allocation failure. Given we have one known pool alloc failure and a second suspected one, along with a third failure that appears unrelated, I'd say you perhaps have two separate issues with this install. One, the nvidia driver (or the card underneath) is misbehaving, and two, you have a filter driver corrupting pool. In that second case, if it was memory corruption and not the same type of potential pool alloc failure I'd say potentially bad RAM. However, in this case it's more likely a filter driver issue given the apparent consistency of the failure. With that said, you *should* be checking your system RAM for faults just in case. It might also be useful to enable driver verifier if your RAM checks out ok to see if the pool alloc faults can be captured.
ill run driver verifier again. through working with this problem i've checked ram roughly 10 times total with no problems.
thanks!! ill let ya know what driver verifier says.
thanks!! ill let ya know what driver verifier says.
ok, i was finally able to run driver verifier. i let it bsod 3 times before ending it. i'm including those 3 dumps, plus the handful more in the past day or so before i could get to driver verifier.
I wonder if your Logitech keyboard is causing the problem. Could you try a different one?
I see your CD drive is reported as a "Problem Device". Try disconnecting it, and see what happens.
...Summary of the Dumps:
I see your CD drive is reported as a "Problem Device". Try disconnecting it, and see what happens.
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Aug 22 06:42:27.260 2010 (UTC - 4:00) System Uptime: 0 days 0:00:14.650 BugCheck 1000007E, {ffffffffc0000005, fffff80002f464bd, fffff880031aeda8, fffff880031ae610} *** WARNING: Unable to verify timestamp for fvevol.sys *** ERROR: Module load completed but symbols could not be loaded for fvevol.sys Probably caused by : volmgr.sys ( volmgr!VmpApplyHotplugProtection+3fc ) PROCESS_NAME: System BUGCHECK_STR: 0x7E �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Aug 22 06:41:33.059 2010 (UTC - 4:00) System Uptime: 0 days 0:00:48.432 BugCheck C9, {23b, fffff88004810818, fffff9800bd8adc0, 0} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 ) BUGCHECK_STR: 0xc9_23b PROCESS_NAME: System �������������������������������������������������������������������������������������� �� Quote: Originally Posted by socrgy9 ok so either way on the paging file i still have random shutdowns while gaming.
i've got paging file set as system managed size without the checkbox checked at the top to auto manage size for all drives.
its still currently allocated at 7935mb
i'm still running my integrated graphics nvidia geforce 6150 SE nforce 430.
attaching dump files, let me know if theres anything else to try.
as of now just waiting on new mobo, gfx cards and case to arrive. <-- will those new parts solve the problems possibly?
ive also been considering just re-installing windows 7 from the ground up and then restoring my system image from backup...could that do any good?
i've got paging file set as system managed size without the checkbox checked at the top to auto manage size for all drives.
its still currently allocated at 7935mb
i'm still running my integrated graphics nvidia geforce 6150 SE nforce 430.
attaching dump files, let me know if theres anything else to try.
as of now just waiting on new mobo, gfx cards and case to arrive. <-- will those new parts solve the problems possibly?
ive also been considering just re-installing windows 7 from the ground up and then restoring my system image from backup...could that do any good?
You reminded me of this: "Random freezes"
Quote:
�A computer that is running Windows Server 2008 R2 or Windows 7 stops responding randomly,� Microsoft stated.
�Applications or services that are running on the computer stop working correctly. Additionally, you cannot log on to the computer by using the remote desktop connection utility,� the company explained.
Microsoft noted that it has identified the problem, but offered very little information to customers.
�This issue occurs because of a deadlock condition between the Lsass.exe process, the Redirected Drive Buffering Subsystem (Rdbss.sys) driver, and the Winsock kernel,� the company said.
�Applications or services that are running on the computer stop working correctly. Additionally, you cannot log on to the computer by using the remote desktop connection utility,� the company explained.
Microsoft noted that it has identified the problem, but offered very little information to customers.
�This issue occurs because of a deadlock condition between the Lsass.exe process, the Redirected Drive Buffering Subsystem (Rdbss.sys) driver, and the Winsock kernel,� the company said.
>Windows 7 Random Freezes Fix Available
It's a network-related hang, given the components that are updated because of the hang as per the KB (name resolution proxy and netbios helper for TCP/IP). Not a bad idea to install though, just in case.
well, once again i'd like to thank everyone for their help. my new mobo, gfx cards and case arrived in the mail today and i will be putting that all together right away. however this thread needs to be closed please do
thanks again!
colin
thanks again!
colin
Congratulations on your new hardware and thank for reporting back. You will soon have a brand new computer.
Let us know when it is up and running.
To mark a thread as solved, you click on the triangle in the upper right and ask the moderators to mark the treas as solved. I will do so.
And again, I thank you for your service.
Let us know when it is up and running. To mark a thread as solved, you click on the triangle in the upper right and ask the moderators to mark the treas as solved. I will do so.
And again, I thank you for your service.
well, i'm up and running again! my first PC build from scratch was a success and took forever LoL! i finally got most of my software loaded back on and i don't have any bsod problems!
thanks again for everyone's support and knowledge. ill never buy a pre-packaged pc again hahaha.
ill update all my system specs shortly.
colin
thanks again for everyone's support and knowledge. ill never buy a pre-packaged pc again hahaha.
ill update all my system specs shortly.
colin
Excellent, Colin; and very good news. Thanks for reporting back. Happy computing and don't be a stranger to the forum.
Không có nhận xét nào:
Đăng nhận xét