I have a brand new CyberPower computer having multiple BSOD issues since it arrived last week. Typically at cold boot after a few reboots seems to run ok for a few hours ............extremely frustrated as you can imagine hopefully you guys can help!!!!!
Windows 7 64 Bit OEM
All Windows 7 Updates
Intel I7 960 3.2 ghz
Asus P6T SE X58 Quad Crossfire Triple Channel DDR3
Latest Bios 0808
12 Gig DDR3 / 1600mhz memory
Nvidia 470 GTX
Latest NVidia Drivers 258.96
Creative Soundblaster Xfi Xtreme
Latest Creative Drivers
950 Watt Power Supply
Asetek 510LC 120mm Watercooler
Windows 7 64 Bit OEM
All Windows 7 Updates
Intel I7 960 3.2 ghz
Asus P6T SE X58 Quad Crossfire Triple Channel DDR3
Latest Bios 0808
12 Gig DDR3 / 1600mhz memory
Nvidia 470 GTX
Latest NVidia Drivers 258.96
Creative Soundblaster Xfi Xtreme
Latest Creative Drivers
950 Watt Power Supply
Asetek 510LC 120mm Watercooler
Forgot the mini dump files
�� Quote: Originally Posted by tktk88 
I have a brand new CyberPower computer having multiple BSOD issues since it arrived last week. Typically at cold boot after a few reboots seems to run ok for a few hours ............extremely frustrated as you can imagine hopefully you guys can help!!!!!
Windows 7 64 Bit OEM
All Windows 7 Updates
Intel I7 960 3.2 ghz
Asus P6T SE X58 Quad Crossfire Triple Channel DDR3
Latest Bios 0808
12 Gig DDR3 / 1600mhz memory
Nvidia 470 GTX
Latest NVidia Drivers 258.96
Creative Soundblaster Xfi Xtreme
Latest Creative Drivers
950 Watt Power Supply
Asetek 510LC 120mm Watercooler
Windows 7 64 Bit OEM
All Windows 7 Updates
Intel I7 960 3.2 ghz
Asus P6T SE X58 Quad Crossfire Triple Channel DDR3
Latest Bios 0808
12 Gig DDR3 / 1600mhz memory
Nvidia 470 GTX
Latest NVidia Drivers 258.96
Creative Soundblaster Xfi Xtreme
Latest Creative Drivers
950 Watt Power Supply
Asetek 510LC 120mm Watercooler
These are pretty straight forward. They were caused by memory corruptiom.
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
Let us know if you need further assistance
Ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\New folder\072510-18735-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;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`03099e50 Debug session time: Sun Jul 25 07:48:47.536 2010 (GMT-4) System Uptime: 0 days 0:00:27.660 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ ................................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff880043b2680, fffff88008f17c30, 0} Probably caused by : memory_corruption Followup: memory_corruption --------- 0: 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: fffff880043b2680, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88008f17c30, 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: HdAudio!CMiniportHelper::PropertyHandlerPinProposeFormat+38 fffff880`043b2680 f6412c40 test byte ptr [rcx+2Ch],40h CONTEXT: fffff88008f17c30 -- (.cxr 0xfffff88008f17c30) rax=fffff88004396e50 rbx=0000000000000000 rcx=0000000000000004 rdx=fffffa800db2b570 rsi=fffffa800db2b570 rdi=0000000000000000 rip=fffff880043b2680 rsp=fffff88008f18600 rbp=fffffa800c623628 r8=fffffa800c623628 r9=11d06e1b45ffaaa0 r10=fffff88004394808 r11=fffff88004389000 r12=fffffa800ca9c470 r13=fffff88004394638 r14=fffff8800439b1a8 r15=fffff88004394638 iopl=0 nv up ei pl nz ac po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010217 HdAudio!CMiniportHelper::PropertyHandlerPinProposeFormat+0x38: fffff880`043b2680 f6412c40 test byte ptr [rcx+2Ch],40h ds:002b:00000000`00000030=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x3B PROCESS_NAME: audiodg.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880043b2680 STACK_TEXT: fffff880`08f18600 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : HdAudio!CMiniportHelper::PropertyHandlerPinProposeFormat+0x38 CHKIMG_EXTENSION: !chkimg -lo 50 -d !HdAudio fffff880043b2669 - HdAudio!CMiniportHelper::PropertyHandlerPinProposeFormat+21 [ 3b:33 ] 1 error : !HdAudio (fffff880043b2669) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT STACK_COMMAND: .cxr 0xfffff88008f17c30 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption --------- 0: 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: fffff880043b2680, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88008f17c30, 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: HdAudio!CMiniportHelper::PropertyHandlerPinProposeFormat+38 fffff880`043b2680 f6412c40 test byte ptr [rcx+2Ch],40h CONTEXT: fffff88008f17c30 -- (.cxr 0xfffff88008f17c30) rax=fffff88004396e50 rbx=0000000000000000 rcx=0000000000000004 rdx=fffffa800db2b570 rsi=fffffa800db2b570 rdi=0000000000000000 rip=fffff880043b2680 rsp=fffff88008f18600 rbp=fffffa800c623628 r8=fffffa800c623628 r9=11d06e1b45ffaaa0 r10=fffff88004394808 r11=fffff88004389000 r12=fffffa800ca9c470 r13=fffff88004394638 r14=fffff8800439b1a8 r15=fffff88004394638 iopl=0 nv up ei pl nz ac po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010217 HdAudio!CMiniportHelper::PropertyHandlerPinProposeFormat+0x38: fffff880`043b2680 f6412c40 test byte ptr [rcx+2Ch],40h ds:002b:00000000`00000030=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x3B PROCESS_NAME: audiodg.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880043b2680 STACK_TEXT: fffff880`08f18600 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : HdAudio!CMiniportHelper::PropertyHandlerPinProposeFormat+0x38 CHKIMG_EXTENSION: !chkimg -lo 50 -d !HdAudio fffff880043b2669 - HdAudio!CMiniportHelper::PropertyHandlerPinProposeFormat+21 [ 3b:33 ] 1 error : !HdAudio (fffff880043b2669) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT STACK_COMMAND: .cxr 0xfffff88008f17c30 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption --------- Code:
ASACPI.sys fffff880`04c3d000 fffff880`04c45000 0x00008000 0x42476c4c 3/27/2005 22:30:36 P17.sys fffff880`04c56000 fffff880`04dd5000 0x0017f000 0x49ed63df 4/21/2009 02:12:47 spldr.sys fffff880`0193c000 fffff880`01944000 0x00008000 0x4a0858bb 5/11/2009 12:56:27 spsys.sys fffff880`0757f000 fffff880`075f0000 0x00071000 0x4a085e7a 5/11/2009 13:20:58 amdxata.sys fffff880`00c54000 fffff880`00c5f000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59
EDIT: Also of note the audiodg service was mentioned and is sometimes the cause.
Thanks for the fast respnse I will give that a run!
I downloaded and ran memtest let it make several passes it shows no errors. Is there a specific test you recommnend to run? Also should I run it as a cold boot after the computer has sat overnight to be as close to the normal conditions for the BSOD??
Let your memtestx86 run for at least 5,6 passes as Ken suggested.
The next step is updating drivers, among the drivers that Ken suggested you to update, I want to emphasize to one driver, which is guaranteed to cause BSODs because it is date from 2005:
Following this article to update it:
http://www.sevenforums.com/787431-post2.html
Instead of 8th item down, now it's about 11th or 12th, double check the name of driver to make sure you download the right one.
Regard,
Tuan
The next step is updating drivers, among the drivers that Ken suggested you to update, I want to emphasize to one driver, which is guaranteed to cause BSODs because it is date from 2005:
Code:
ASACPI.sys fffff880`04c3d000 fffff880`04c45000 0x00008000 0x42476c4c 3/27/2005 22:30:36
http://www.sevenforums.com/787431-post2.html
Instead of 8th item down, now it's about 11th or 12th, double check the name of driver to make sure you download the right one.
Regard,
Tuan
Thanks I will download the file now do you suggest updating all the files mentioned in the previous post or just this one for now??
Just that one for now, if you have more trouble thus updating the rest of them 
Ok updated the ASACPI.sys file and verified its now dated 5/09. Back to the memtestx86 do you recommend running it overnight maybe? Or waiting and doing a cold boot after the computer has been off all night say running it before booting to windows the first time for the day?? It ran for a few hours and gave me no errors....
It's ok either way. You can do that if you feel tired now! You can let it run overnight while you sleeping. It usually take about 9 or 10 hours average to do 5,6 pass.
Thanks I will let it run........you guys are great!
Update to Memtest86.................I let it run for 16 hours to midway through pass7 no errors............Since Memory appeared to be the issue in your findings and Memtest found no errors.... do we think that the old ASACPI.sys file was causing a memory error??? Or should I be looking at or trying something else??
There is a very good chance that was the cause or one of the causes. Run your system and see how it does.
The problem was persistant at cold boot after a few reboots the system would run typically fine...........
Be sure to post back in two or three days and give us an update. If you have another BSOD, upload it ASAP. I hope your troubles are behind you. 
By the way, I see you are a fellow Floridian.
By the way, I see you are a fellow Floridian.
Will do I am hoping that the cold boot in the morning goes well thats typically when it rears its ugly head.........
Yes I am a true Floridian born and raised................
Thanks for all the help so far I am keeping my fingers crossed that we have it beat!
Yes I am a true Floridian born and raised................
Thanks for all the help so far I am keeping my fingers crossed that we have it beat!
Welll not so lucky this morning at cold boot immediate BSOD.....here's the latest files.......
Mini Dump Files
Please remove Norton/Symantec antivirus. Stop code is 50, which suggest antivirus is potential cause.
Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support
If you need an alternative AV that is BSODs free, try Microsoft security essential
http://www.microsoft.com/security_essentials <---MSE
Also, update your networking driver if you can
Let us know if you need help
Tuan
Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support
If you need an alternative AV that is BSODs free, try Microsoft security essential
http://www.microsoft.com/security_essentials <---MSE
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$DI01.746\080110-16068-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e51000 PsLoadedModuleList = 0xfffff800`0308ee50 Debug session time: Sun Aug 1 18:48:56.697 2010 (UTC + 7:00) System Uptime: 0 days 0:00:29.821 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8800f331960, 0, fffff880047065a2, 2} Could not read faulting driver name Probably caused by : HTTP.sys ( HTTP!UlCopyRequestToBuffer+486 ) Followup: MachineOwner --------- Let us know if you need help
Tuan
I will give that a try..........thanks for your patience helping me work through this! It sure is frustrating............you guys are great......
Out of curiosity in the most recent BSOD files you looked at for me today does the memory now appear to be ok? If so, do we think it was the old ASACPI.sys file that was causing the memory issues?? Also, any theories as to why Norton would cause the BSOD just on cold boot??
Quote:
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
personally, I think ASACPI.sys cause memory issue and as you update it, you longer have to worry about it.
It's possible that Norton service was started when computer start and cause crash. Hopefully removing antivirus with updating networking driver will solve the issue
Ttran is right. I missed that on my review. Thanks, Ttran. Norton is a known cause of crashes on some Win 7 systems as are many third party antitrust and firewall programs. Troubleshooting is frustrating because it is a process of elimination many times. You will get there.
Thanks for all your help guys........I updated my NIC driver directly from Realtek and will uninstall Norton I guess I wont know until tomorrow's cold boot if we made any progress................Any word on the Norton 2011 Beta and how it is with Windows7 X64 I looked through the posts on the forum here out of curiousity........I have always used Norotn with no issues so I am hoping that the 2011 version will work until then I will be using what you suggested........
Ok I have removed Norton Internet Security 2010 with the Norton removal tool and installed Microsoft Security Essentials..............keeping my fingers crossed for tomorrows cold boot!!
Let us know; we are waiting, too.
Thanks for the follow up. I have been at work since early this am have not turned on my computer at home yet. I will be keeping my fingers crossed for when I get home and give it a try in the next few hours........I will let you know.......
Well not so lucky on cold boot today I got another BSOD..here's the latest files...I am getting really good at collecting the files and zipping them up LOL
Try this. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Leave the computer off overnight, and then immediately boot from the CD. See if errors are reported within 5-10 minutes.
Will do there are alot of different versions of memtest86 can you link me to the version you suggest to run? Thanks...I am assuming that the latest files are indicating a memory issue???
This is the version I used......... do you suggest this one or a different version?
Yep, 4.10 is the correct version.
Ok thanks I will run it in the morning..........Just out of curiosty did the latest BSOD files indicate a memory issue??
By not pointing to another cause, the dumps merely support the theory of bad RAM. Very rarely, if ever, do dumps actually point to RAM as the culprit.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 4 for Minidump.zip\Minidump\080210-22370-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304ae50 Debug session time: Mon Aug 2 17:17:51.031 2010 (GMT-4) System Uptime: 0 days 0:02:07.060 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa80071d3480, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 ) Followup: MachineOwner --------- Ok thanks back to doing the memtest in the morning at first boot......hopefully we find something................
Sorry I menat to mention this as well.............I looked at the Ram on the board it is ADATA DDR1600 Gaming Series it calls for 1.55 to 1.75 volts since this is at cold boot should we check the voltage to the Ram?? If so can you give me some guidance on how to accomplish that on my Motherboard............Asus P6T SE
Ok as planned I booted directly to Memtest86 this morning before booting to windows I definately got error messages from memtest. The question is how do you determine which ram dimm is causing the issue I dont see a way to print the memtest screen or capture it............Here are the latest files as well..........how do I proceed form here????
Remove all of your RAM except one stick. Run Memtest on that stick for at least seven passes. If it passes, remove that stick and test another in that same slot repeating this sequence until you have tested all of your RAM individually. If the first stick fails, move it to another slot and test it again. You want to make sure it is not the slot that is bad.
If all of your RAM passes, or even if it doesn't, take a stick that test good and test that stick in each RAM slot to make sure all of your slots are good. I know this is time consuming; but it is the only way to isolate the problem.
Post back with the results.
If all of your RAM passes, or even if it doesn't, take a stick that test good and test that stick in each RAM slot to make sure all of your slots are good. I know this is time consuming; but it is the only way to isolate the problem.
Post back with the results.
These are your last two dumps.
You have two older drivers showing in the dumps. Older drivers can cause memory corruption. Try to update these drivers to ones with dates of July 13, 2009 or later. Update them from the manufacturers' sites.
ASACPI.sys Wed May 13 21:25:17 2009 - ATK0110 ACPI Utility or ATK0100 ACPI Utility belongs to the software ATK0110 ACPI UTILITY, ASUS-Motherboard.
P17.sys Tue Apr 21 02:12:47 2009 - WDM Audio Miniport belongs to the software Creative SB Audigy LS or SB Live! 24-bit by Creative Technology Ltd (www.creative.com).
Quote:
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
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\Temp2_Minidump.zip\Minidump\080210-22370-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304ae50 Debug session time: Mon Aug 2 17:17:51.031 2010 (GMT-4) System Uptime: 0 days 0:02:07.060 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa80071d3480, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 ) Followup: MachineOwner --------- 7: 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: fffffa80071d3480 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: wermgr.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002ef0ede to fffff80002e7d600 STACK_TEXT: fffff880`072ca8c8 fffff800`02ef0ede : 00000000`0000001a 00000000`00041790 fffffa80`071d3480 00000000`0000ffff : nt!KeBugCheckEx fffff880`072ca8d0 fffff800`02e50b3b : ffffffff`00000000 00000000`02baffff fffffa80`00000000 fffffa80`0cf38060 : nt! ?? ::FNODOBFM::`string'+0x33946 fffff880`072caa90 fffff800`03163c4f : fffff8a0`02f25a50 00000000`00000001 00000000`00000000 fffffa80`0cf38060 : nt!MmCleanProcessAddressSpace+0x62f fffff880`072caae0 fffff800`0313b6eb : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x92f fffff880`072caba0 fffff800`02e7c853 : fffffa80`0d07b9b0 fffff880`00000000 00000000`002c3e90 fffffa80`0cf38060 : nt!NtTerminateProcess+0x25b fffff880`072cac20 00000000`777f001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0012fa98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777f001a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+33946 fffff800`02ef0ede cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33946 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946 BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946 Followup: MachineOwner --------- 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\Temp2_Minidump.zip\Minidump\080310-22230-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e4c000 PsLoadedModuleList = 0xfffff800`03089e50 Debug session time: Tue Aug 3 07:17:54.422 2010 (GMT-4) System Uptime: 0 days 0:01:04.562 Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff1000b7c94c0, 1, fffff880062d6a26, 7} Could not read faulting driver name *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff1000b7c94c0, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff880062d6a26, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f40e0 fffff1000b7c94c0 FAULTING_IP: HTTP!UxpWskOpenListenSocket+146 fffff880`062d6a26 4c89642440 mov qword ptr [rsp+40h],r12 MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff88005533800 -- (.trap 0xfffff88005533800) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880062d6a26 rsp=fffff88005533990 rbp=fffff88006295af0 r8=fffff78000000008 r9=0000000000000000 r10=0000000000000000 r11=fffff88005533980 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc HTTP!UxpWskOpenListenSocket+0x146: fffff880`062d6a26 4c89642440 mov qword ptr [rsp+40h],r12 ss:0018:fffff880`055339d0=fffffa800c638d60 Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002f3b789 to fffff80002ebc600 STACK_TEXT: fffff880`05533698 fffff800`02f3b789 : 00000000`00000050 fffff100`0b7c94c0 00000000`00000001 fffff880`05533800 : nt!KeBugCheckEx fffff880`055336a0 fffff800`02eba6ee : 00000000`00000001 00000000`00000000 00000000`98000000 fffffa80`0baf6010 : nt! ?? ::FNODOBFM::`string'+0x40e4b fffff880`05533800 fffff880`062d6a26 : 00000000`00000000 fffff880`06295af0 fffffa80`0baf6028 fffffa80`0c53af40 : nt!KiPageFault+0x16e fffff880`05533990 fffff880`062709e6 : fffff880`05533b58 fffffa80`0c53af40 fffff880`06295af0 fffff880`030f9180 : HTTP!UxpWskOpenListenSocket+0x146 fffff880`05533ab0 fffff880`06272d7f : fffffa80`0ba81350 00000000`00000000 fffff880`05533b50 00000000`00000000 : HTTP!UxTlProviderCreateListenEndpoint+0x36 fffff880`05533ae0 fffff880`062dc06e : fffffa80`0ba81350 00000000`00000000 fffffa80`0ba813e0 00000000`00000000 : HTTP!UxpTlCreateListenEndpoint+0x11f fffff880`05533b30 fffff880`06278309 : 00000000`00000000 00000000`00000002 fffff880`05533c30 fffff880`05533bf0 : HTTP!UxpTlAssociateListenEndpoints+0x11e fffff880`05533ba0 fffff880`062788bd : 00000000`c0000225 fffff880`05533c30 fffff880`05533ca8 fffff880`0552c720 : HTTP!UxpTlCreateAddressEndpoint+0xa9 fffff880`05533bd0 fffff880`062789b0 : fffff880`0552c720 00000000`00000000 00000000`00000003 fffff880`05533ca8 : HTTP!UxTlCreateEndpointRequest+0xbd fffff880`05533c10 fffff880`062ef1a1 : fffffa80`0baf4190 fffff880`06291890 00000000`00000003 00000000`00000000 : HTTP!UlAddSiteToEndpointList+0x90 fffff880`05533c70 fffff880`0629f289 : fffffa80`09d40000 00000000`00000000 fffffa80`0bae6300 00000000`00000000 : HTTP!UlpDeferredAddSiteWorker+0x21 fffff880`05533ca0 fffff800`03161a86 : 00000000`03888e2d fffffa80`0bae6370 00000000`00000080 fffffa80`09d40040 : HTTP!UlpThreadPoolWorker+0x279 fffff880`05533d40 fffff800`02e9ab06 : fffff800`03036e80 fffffa80`0bae6370 fffff800`03044c40 fffff880`01217a90 : nt!PspSystemThreadStartup+0x5a fffff880`05533d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !HTTP fffff880062d6d29 - HTTP!UlpExclusiveNamespaceAccessCheck+149 [ 08:00 ] 1 error : !HTTP (fffff880062d6d29) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption --------- 6: kd> lmtsmn start end module name fffff880`04271000 fffff880`042af000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`00f9b000 fffff880`00ff2000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02c17000 fffff880`02ca1000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`042f2000 fffff880`04308000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`00c4d000 fffff880`00c58000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`0483d000 fffff880`04845000 ASACPI ASACPI.sys Wed May 13 21:25:17 2009 (4A0B72FD) fffff880`00c1a000 fffff880`00c23000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00c23000 fffff880`00c4d000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`019cd000 fffff880`019d4000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`03d96000 fffff880`03da7000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`06316000 fffff880`06334000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00780000 fffff960`007a7000 cdd cdd.dll unavailable (00000000) fffff880`04d81000 fffff880`04d9e000 cdfs cdfs.sys Mon Jul 13 19:19:46 2009 (4A5BC112) fffff880`0196d000 fffff880`01997000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00d36000 fffff880`00df6000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`01907000 fffff880`01937000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00cd8000 fffff880`00d36000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01000000 fffff880`01073000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`04845000 fffff880`04855000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`04c69000 fffff880`04c77000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03cf5000 fffff880`03d78000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`03d78000 fffff880`03d96000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`02dbb000 fffff880`02dca000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`018f1000 fffff880`01907000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`04c1c000 fffff880`04c44000 Dot4 Dot4.sys Mon Jul 13 20:00:16 2009 (4A5BCA90) fffff880`04c51000 fffff880`04c5b000 Dot4Prt Dot4Prt.sys Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`04c0c000 fffff880`04c1c000 dot4usb dot4usb.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`049d6000 fffff880`049f8000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`04c83000 fffff880`04c8c000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`04c77000 fffff880`04c83000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`04c8c000 fffff880`04c9f000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`04d75000 fffff880`04d81000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`03c00000 fffff880`03cf4000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`10b44000 fffff880`10b8a000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`01125000 fffff880`01139000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`010d9000 fffff880`01125000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`013d4000 fffff880`013de000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`018b7000 fffff880`018f1000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`01592000 fffff880`015dc000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`02e03000 fffff800`02e4c000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`10b8a000 fffff880`10bae000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`04dc9000 fffff880`04de2000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`04de2000 fffff880`04dea080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`04dbb000 fffff880`04dc9000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`0624e000 fffff880`06316000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`015f4000 fffff880`015fd000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`03dcd000 fffff880`03de3000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`043c8000 fffff880`043d7000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`04c5b000 fffff880`04c69000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00b9b000 fffff800`00ba5000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`042af000 fffff880`042f2000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`013a9000 fffff880`013c3000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01567000 fffff880`01592000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`049f8000 fffff880`049fd200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`04cd0000 fffff880`04ce5000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04cad000 fffff880`04cd0000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c80000 fffff880`00cc4000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66) fffff880`04c9f000 fffff880`04cad000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`043d7000 fffff880`043e6000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`04c44000 fffff880`04c51000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00c00000 fffff880`00c1a000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`01997000 fffff880`019c4000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`06334000 fffff880`0634c000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`0634c000 fffff880`06379000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`06379000 fffff880`063c7000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`063c7000 fffff880`063ea000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`01850000 fffff880`0185b000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e00000 fffff880`00e0a000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01139000 fffff880`01197000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`02db0000 fffff880`02dbb000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`01400000 fffff880`01412000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`01415000 fffff880`01507000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`0432c000 fffff880`04338000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`04338000 fffff880`04367000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`04d43000 fffff880`04d58000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`02d15000 fffff880`02d24000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02ca1000 fffff880`02ce6000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01507000 fffff880`01567000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`0185b000 fffff880`0186c000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`02da4000 fffff880`02db0000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02e4c000 fffff800`03428000 nt ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB) fffff880`01206000 fffff880`013a9000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`019c4000 fffff880`019cd000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`10b42000 fffff880`10b43180 nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA) fffff880`0feb0000 fffff880`10b41e00 nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E) fffff880`04857000 fffff880`049d6000 P17 P17.sys Tue Apr 21 02:12:47 2009 (49ED63DF) fffff880`02cef000 fffff880`02d15000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`00e4a000 fffff880`00e5f000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00e0a000 fffff880`00e3d000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00ed0000 fffff880`00ed7000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00ed7000 fffff880`00ee7000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`013c3000 fffff880`013d4000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`06675000 fffff880`0671b000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`04800000 fffff880`0483d000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00cc4000 fffff880`00cd8000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`04308000 fffff880`0432c000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`04367000 fffff880`04382000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`04382000 fffff880`043a3000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`043a3000 fffff880`043bd000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`02d53000 fffff880`02da4000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`043bd000 fffff880`043c8000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`01835000 fffff880`0183e000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`0183e000 fffff880`01847000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`01847000 fffff880`01850000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`01197000 fffff880`011d1000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`04200000 fffff880`04218000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`0421b000 fffff880`04271000 Rt64win7 Rt64win7.sys Wed Jun 23 05:10:45 2010 (4C21CF95) fffff880`0671b000 fffff880`06726000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`015ec000 fffff880`015f4000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`06aee000 fffff880`06b86000 srv srv.sys Tue Dec 08 03:32:55 2009 (4B1E0F37) fffff880`06765000 fffff880`067ce000 srv2 srv2.sys Mon Jul 13 19:25:02 2009 (4A5BC24E) fffff880`06726000 fffff880`06753000 srvnet srvnet.sys Tue Dec 08 03:32:26 2009 (4B1E0F1A) fffff880`04855000 fffff880`04856480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys Mon Jul 13 19:25:34 2009 (4A5BC26E) fffff880`06753000 fffff880`06765000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`0188a000 fffff880`01897000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`0186c000 fffff880`0188a000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`02d3f000 fffff880`02d53000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00450000 fffff960`0045a000 TSDDD TSDDD.dll unavailable (00000000) fffff880`03da7000 fffff880`03dcd000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`043e6000 fffff880`043f8000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`04d9e000 fffff880`04dbb000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`04d73000 fffff880`04d74f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`0fe56000 fffff880`0fe67000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04ce9000 fffff880`04d43000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`0fe00000 fffff880`0fe56000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`04c00000 fffff880`04c0c000 usbprint usbprint.sys Mon Jul 13 20:38:18 2009 (4A5BD37A) fffff880`04deb000 fffff880`04dfc000 usbscan usbscan.sys Mon Jul 13 20:35:32 2009 (4A5BD2D4) fffff880`04d58000 fffff880`04d73000 USBSTOR USBSTOR.SYS Mon Jul 13 20:06:34 2009 (4A5BCC0A) fffff880`10bae000 fffff880`10bbb000 usbuhci usbuhci.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00e3d000 fffff880`00e4a000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`019d4000 fffff880`019e2000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`01800000 fffff880`01825000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`015dc000 fffff880`015ec000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E) fffff880`00e5f000 fffff880`00e74000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00e74000 fffff880`00ed0000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01073000 fffff880`010bf000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`02d24000 fffff880`02d3f000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`01825000 fffff880`01835000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00ee8000 fffff880`00f8c000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f8c000 fffff880`00f9b000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02ce6000 fffff880`02cef000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`000b0000 fffff960`003bf000 win32k win32k.sys unavailable (00000000) fffff880`00ff2000 fffff880`00ffb000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`0fe67000 fffff880`0fe88000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`01937000 fffff880`01945000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01945000 fffff880`01951000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01951000 fffff880`0195a000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0195a000 fffff880`0196d000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
ASACPI.sys Wed May 13 21:25:17 2009 - ATK0110 ACPI Utility or ATK0100 ACPI Utility belongs to the software ATK0110 ACPI UTILITY, ASUS-Motherboard.
P17.sys Tue Apr 21 02:12:47 2009 - WDM Audio Miniport belongs to the software Creative SB Audigy LS or SB Live! 24-bit by Creative Technology Ltd (www.creative.com).
Thanks for the update.......according to the note on the first page I updated the ASACPI.sys file the other day the original file was dated 3/27/05 the current file I downloaded from ASUS and installed it is dated 5/14/09..........Ironically I had installed the latest file for my soundcard from Creative, however, windows update had a newer file available than on the Creative site so I downloaded and installed it as well.....now on to the tideous task of checking out the RAM I will let you know what I find...........thanks for your continued support.............
Very good. Post you Memtest results.
Latest update..............I removed all the ram and began booting to memtest have eliminated all but a stick that tested bad on boot to memtest 2 times so for now I am running only 5 of the 6 sims and so far BSOD free the real test will be with the cold boot in the morning lets keep our fingers crossed!!!!! I will update after the cold boot...............
Waiting for your update and hoping to hear no BSOD.
Today's update.....I cold booted directly to memtest this morning with all of the 5 "good" sims installed on the board this morning and let memtest make 3 full passes with no errors....................again today so far no BSOD..........the final test will be the normal cold boot to windows tomorrow.........looking godd so far!
should have said looking good so far!
That is good news; but I recommend that you run memtest for 5-7 passes. Three is many times not enough. I am glad it booted with no problems, though. Looking for your next report - and I hope it is a good one.
Thanks Carl I never got any errors from memtest except at cold boot and they showed up immediately..........with the one sim it failed everytime I booted to it cold.............after tomorrows normal cold boot I plan to follow up with a cold boot to memtest on Monday and let it run for at least 5 passes while I am at work..........but it is encouraging to say the least....also I can't tell you how much I appreciate all the help from you and the guys here..............
Bad RAM can most definitely crash a system. I hope that was the only problem and you are on your way to smooth computing.
Well day 3 of the solution and we are BSOD free so far!! I am beginning to think we have it beat!!!
I am beginning to think we have it beat!!! That is wonderful news!! I surely hope it is history for you. You have done a good job of following suggestions and working this on your own. If you have no problem tomorrow, post back and let us know. Maybe we can mark this one as solved.
Will do and thanks again for all your help and patience with this issue...........
You are certainly welcome. That is what we are here for.
Well the cold boot today went perfectly and memtest made 6 passes with no errors.......CyberPower is sending a replacement for the bad Ram life is good........thanks again for all your help!!!!
I am delighted that you have found the problem and the solution! Great news. I hope the replacement RAM works perfectly! Let us know how your system is doing after you install the new RAM and maybe we can mark this one as solved.
Let us know how your system is doing after you install the new RAM and maybe we can mark this one as solved. Thanks again......I will do a follow up post after getting the new Ram installed most likely by the time it arrives should be towards the end of the week........Its nice to be BSOD free!!!
Just a follow up at this point I have been BSOD free since the last update......the new RAM has been shipped however they sent it UPS Ground from California so it doesn't arrive until the 18th...............will update after it is installed.........
since the last update......the new RAM has been shipped however they sent it UPS Ground from California so it doesn't arrive until the 18th...............will update after it is installed......... I am very glad you are BSOD free; and thank you for keeping us updated. I will wait until you install the new RAM before requesting this thread be marked as solved.
Well all is good here no BSOD since last update computer still running fine.........the replacement RAM arrived today, however, they sent the wrong brand which doesnt match my exisiting Ram...I ahve read that exact matching Ram is important.......... so I have another call into them still waiting..........
I do not recommend mixing brands of RAM. That is asking for problems. But it is certainly good to hear that you haven't had any more crashes.
Latest update still BSOD free however i am experiencing different amounts of Ram being detected off and on typically again at cold boot. I have 10 megs in the computer right now still waiting on the replacement Ram. Sometimes windows and the bios will see 2 or 6 meg of ram and not the whole 10 meg. Typicaly after a reboot or 2 and the computer being warm it detects all of the ram. CPU-z will always see all of the ram even if windows and the bios is showing less than the total of 10 that is installed
I would also add that the computer appears to perform just fine no matter what amount of ram is detected and I am expereinceing no BSOD's
We have some experts with RAM here. I am not one of them. I suggest you start a new thread in Performance and Maintenance Section and post there what you posted here. They can most likely help you solve it.
Sure am glad to hear you are still BSOD free!!!
Sure am glad to hear you are still BSOD free!!!
Thanks Carl will do...................yes this issue is more of an annoyance than the frustration of the BSOD thing.....
Well I guess it was too good to be true another BSOD today any thoughts???
This one is an error code 24, NTFS_FILE_SYSTEM. Usual causes are Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure.
Let's check your hard drive.
Copy/paste your results into you next post.
Next use the diagnosing tool from your hard drive manufacturer and diagnose your hard drive. Post back with those 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_Minidump(2).zip\Minidump\082410-13244-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e15000 PsLoadedModuleList = 0xfffff800`03052e50 Debug session time: Tue Aug 24 18:02:15.777 2010 (GMT-4) System Uptime: 0 days 1:21:12.775 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff880085738a8, fffff88008573110, fffff880012f7b76} Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenAttribute+326 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff880085738a8 Arg3: fffff88008573110 Arg4: fffff880012f7b76 Debugging Details: ------------------ EXCEPTION_RECORD: fffff880085738a8 -- (.exr 0xfffff880085738a8) ExceptionAddress: fffff880012f7b76 (Ntfs!NtfsOpenAttribute+0x0000000000000326) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88008573110 -- (.cxr 0xfffff88008573110) rax=fffef8a00952e888 rbx=fffffa80073cb4c0 rcx=fffff8a009e2bba0 rdx=0000000000000000 rsi=fffffa8006f6a368 rdi=fffff8a00bf8e100 rip=fffff880012f7b76 rsp=fffff88008573ae0 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=fffff880012a2380 r11=fffff8a00bf8e128 r12=fffff88008574420 r13=fffff8a009e2b8f0 r14=0000000000000002 r15=fffff880085743b0 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 Ntfs!NtfsOpenAttribute+0x326: fffff880`012f7b76 4c8918 mov qword ptr [rax],r11 ds:002b:fffef8a0`0952e888=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: rundll32.exe CURRENT_IRQL: 1 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bd0e0 ffffffffffffffff FOLLOWUP_IP: Ntfs!NtfsOpenAttribute+326 fffff880`012f7b76 4c8918 mov qword ptr [rax],r11 FAULTING_IP: Ntfs!NtfsOpenAttribute+326 fffff880`012f7b76 4c8918 mov qword ptr [rax],r11 BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff880012e5e45 to fffff880012f7b76 STACK_TEXT: fffff880`08573ae0 fffff880`012e5e45 : fffffa80`07330970 fffffa80`06f6a368 fffffa80`07ec5180 fffff8a0`09e2bc88 : Ntfs!NtfsOpenAttribute+0x326 fffff880`08573bf0 fffff880`012e278b : fffff880`085743b0 fffffa80`07330970 fffff8a0`09e2bc88 fffff8a0`0000006e : Ntfs!NtfsOpenExistingAttr+0x145 fffff880`08573cb0 fffff880`012e2eff : fffffa80`07330970 fffffa80`06f6a010 fffff8a0`09e2bc88 fffff880`0000006e : Ntfs!NtfsOpenAttributeInExistingFile+0x5ab fffff880`08573e40 fffff880`012f3e76 : fffffa80`07330970 fffffa80`06f6a010 fffff8a0`09e2bc88 00000000`0009e001 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef fffff880`08573f30 fffff880`012ee28d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsFindStartingNode+0x5e6 fffff880`08574000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreate+0x3dd SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Ntfs!NtfsOpenAttribute+326 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f STACK_COMMAND: .cxr 0xfffff88008573110 ; kb FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsOpenAttribute+326 BUCKET_ID: X64_0x24_Ntfs!NtfsOpenAttribute+326 Followup: MachineOwner ---------
Quote:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP)
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP)
Copy/paste your results into you next post.
Next use the diagnosing tool from your hard drive manufacturer and diagnose your hard drive. Post back with those results.
I ran the CHKDSK/R/F now I am having trouble finding the results file........In the meantime today yet another BSOD here are the files.............
A new day and yet another BSOD............hopefully between these files and yesterdays file you find something we can fix.........
�� Quote: Originally Posted by tktk88 I ran the CHKDSK/R/F now I am having trouble finding the results file........In the meantime today yet another BSOD here are the files.............
�� Quote: Originally Posted by tktk88 A new day and yet another BSOD............hopefully between these files and yesterdays file you find something we can fix.........
Both of these dumps are error code 3B, SYSTEM_SERVICE_EXCEPTION - usual causes are system service, Device driver, graphics driver, ?memory.
Code:
Kernel base = 0xfffff800`02e68000 PsLoadedModuleList = 0xfffff800`030a5e50 Debug session time: Sat Aug 28 14:04:58.630 2010 (GMT-4) System Uptime: 0 days 0:16:06.832 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800031d4c0b, fffff8800a0a91d0, 0} Probably caused by : ntkrnlmp.exe ( nt!NtWaitForMultipleObjects+fe ) Followup: MachineOwner --------- 4: 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: fffff800031d4c0b, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800a0a91d0, 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!NtWaitForMultipleObjects+fe fffff800`031d4c0b c3 ret CONTEXT: fffff8800a0a91d0 -- (.cxr 0xfffff8800a0a91d0) rax=0000000000000000 rbx=fffffa8008991660 rcx=fffffa8009a96be0 rdx=00000000000007ff rsi=000000000205f5d8 rdi=fffff8800a0a9bc8 rip=fffff800031d4c0b rsp=fffff8800a0a9ba8 rbp=fffff8800a0a9ca0 r8=fffffa8009338618 r9=0000000000000000 r10=ffffffffffffffef r11=fffff8800a0a9ba0 r12=0000000000000000 r13=000000000205f660 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!NtWaitForMultipleObjects+0xfe: fffff800`031d4c0b c3 ret Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: audiodg.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffef80002ed7993 to fffff800031d4c0b STACK_TEXT: fffff880`0a0a9ba8 fffef800`02ed7993 : fffffa80`08991660 00000000`0205f5d8 fffff880`0a0a9bc8 fffff800`031ee3f0 : nt!NtWaitForMultipleObjects+0xfe fffff880`0a0a9bb0 fffffa80`08991660 : 00000000`0205f5d8 fffff880`0a0a9bc8 fffff800`031ee3f0 00000000`00000000 : 0xfffef800`02ed7993 fffff880`0a0a9bb8 00000000`0205f5d8 : fffff880`0a0a9bc8 fffff800`031ee3f0 00000000`00000000 ffffdbb0`198c312c : 0xfffffa80`08991660 fffff880`0a0a9bc0 fffff880`0a0a9bc8 : fffff800`031ee3f0 00000000`00000000 ffffdbb0`198c312c 00000000`00000000 : 0x205f5d8 fffff880`0a0a9bc8 fffff800`031ee3f0 : 00000000`00000000 ffffdbb0`198c312c 00000000`00000000 00000000`00000000 : 0xfffff880`0a0a9bc8 fffff880`0a0a9bd0 fffff800`02ed7993 : fffffa80`08991660 fffff880`0a0a9ca0 00000000`0205f490 00000000`00000000 : nt!ObpCloseHandle+0x70 fffff880`0a0a9c20 00000000`77cd030a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0205f5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cd030a FOLLOWUP_IP: nt!NtWaitForMultipleObjects+fe fffff800`031d4c0b c3 ret SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!NtWaitForMultipleObjects+fe FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff8800a0a91d0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!NtWaitForMultipleObjects+fe BUCKET_ID: X64_0x3B_nt!NtWaitForMultipleObjects+fe Followup: MachineOwner --------- Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`03098e50 Debug session time: Sun Aug 29 08:01:21.342 2010 (GMT-4) System Uptime: 0 days 0:16:39.545 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800031c7c0b, fffff880062071d0, 0} Probably caused by : ntkrnlmp.exe ( nt!NtWaitForMultipleObjects+fe ) Followup: MachineOwner --------- 4: 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: fffff800031c7c0b, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880062071d0, 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!NtWaitForMultipleObjects+fe fffff800`031c7c0b c3 ret CONTEXT: fffff880062071d0 -- (.cxr 0xfffff880062071d0) rax=0000000000000102 rbx=fffffa8008d98960 rcx=fffffa8008dc6690 rdx=00000000000007ff rsi=000000000ac5f768 rdi=fffff88006207bc8 rip=fffff800031c7c0b rsp=fffff88006207ba8 rbp=fffff88006207ca0 r8=fffffa80080f8a58 r9=0000000000000000 r10=ffffffffffffffef r11=fffff88006207ba0 r12=000000000ac5f798 r13=000000000ac5f7f0 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!NtWaitForMultipleObjects+0xfe: fffff800`031c7c0b c3 ret Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffef80002eca993 to fffff800031c7c0b STACK_TEXT: fffff880`06207ba8 fffef800`02eca993 : fffffa80`08d98960 00000000`0ac5f768 fffff880`06207bc8 00000000`00000000 : nt!NtWaitForMultipleObjects+0xfe fffff880`06207bb0 fffffa80`08d98960 : 00000000`0ac5f768 fffff880`06207bc8 00000000`00000000 fffff880`06207990 : 0xfffef800`02eca993 fffff880`06207bb8 00000000`0ac5f768 : fffff880`06207bc8 00000000`00000000 fffff880`06207990 fffffa80`080f89d0 : 0xfffffa80`08d98960 fffff880`06207bc0 fffff880`06207bc8 : 00000000`00000000 fffff880`06207990 fffffa80`080f89d0 00000000`0000002a : 0xac5f768 fffff880`06207bc8 00000000`00000000 : fffff880`06207990 fffffa80`080f89d0 00000000`0000002a fffff960`00133dd6 : 0xfffff880`06207bc8 FOLLOWUP_IP: nt!NtWaitForMultipleObjects+fe fffff800`031c7c0b c3 ret SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!NtWaitForMultipleObjects+fe FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880062071d0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!NtWaitForMultipleObjects+fe BUCKET_ID: X64_0x3B_nt!NtWaitForMultipleObjects+fe Followup: MachineOwner --------- RAM - Test with Memtest86+
Post back with the results.
The next step will be to enable Driver Verifier. Read this tutorial. Upload any dumps generated by Driver Verifier.
Driver Verifier - Enable and Disable
Ok the new motherboard and ram arrived this afternoon It is installed and up and running all is good so far keeping my fingers crossed
Thank you for the update. My fingers are crossed to. Let us know.
you are very welcome...I will keep you updated....I elected to try it without a reinstall of windows same motherboard and bios version so far so good
Wonderful news!!! I surely hope it stays that way and your problems are solved. Be sure to let us know in a couple of days.
Well day 3 and all is still good keeping my fingers crossed......no BSOD and recognizes the correct amount of Ram everytime!
Congratualtions! I think we can mark this one as solved. Happy computing!
Không có nhận xét nào:
Đăng nhận xét