BSOD on start up. part 1

Lulubop

Usually happens 1 or 2 times, then it won't happen for the rest of the day. Though the problems returns the next day. I've updated my video card drivers, as well as diagnosed any issues with my memory and Hard Drive, finding no issues. This seems to be effecting my Desktop Windows Manager as well.


Dump File 072810-20826-01.dmp
Crash Time 7/28/2010 1:23:43 PM
Bug Check String MEMORY_MANAGEMENT
Bug Check Code 0x0000001a
Parameter 1 00000000`00003452
Parameter 2 000007fe`fdc93000
Parameter 3 fffff700`01081170
Parameter 4 99d00001`2aab5024
Caused By Driver ntoskrnl.exe
Caused By Address ntoskrnl.exe+70600
File Description NT Kernel & System
Product Name Microsoft� Windows� Operating System
Company Microsoft Corporation
File Version 6.1.7600.16539 (win7_gdr.100226-1909)
Processor x64
Computer Name
Full Path C:\Windows\Minidump\072810-20826-01.dmp
Processors Count 4
Major Version 15
Minor Version 7600

Is it possible this can be related to an outdated Network adapter driver?

Jonathan_King

It is certainly possible.

Please follow these directions: http://www.sevenforums.com/crashes-d...tructions.html

Lulubop

After updating the drivers on my network card using the auto update my computer crashes anytime I try to open a browser. I am on my phone at the moment.

Tews

We really need the .dmp files... can you boot into safe mode and upload them?

Lulubop

Sorry.

Jonathan_King

Please enable driver verifier: Using Driver Verifier to identify issues with Drivers

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 1 for bsod.zip\bsod\Windows7_BSOD_jcgriff2\072710-22947-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`0280b000 PsLoadedModuleList = 0xfffff800`02a48e50 Debug session time: Tue Jul 27 13:26:20.831 2010 (GMT-4) System Uptime: 0 days 0:13:08.236 Loading Kernel Symbols ............................................................... ................................................................ ..... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck 1A, {3452, 940b000, fffff700010ae220, bb3000005466f866}  Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a23 )  Followup: MachineOwner ---------  1: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  MEMORY_MANAGEMENT (1a)     # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000003452, The subtype of the bugcheck. Arg2: 000000000940b000 Arg3: fffff700010ae220 Arg4: bb3000005466f866  Debugging Details: ------------------   BUGCHECK_STR:  0x1a_3452  CUSTOMER_CRASH_COUNT:  1  DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT  PROCESS_NAME:  svchost.exe  CURRENT_IRQL:  0  LAST_CONTROL_TRANSFER:  from fffff800028eefb3 to fffff8000287b600  STACK_TEXT:   fffff880`0832cff8 fffff800`028eefb3 : 00000000`0000001a 00000000`00003452 00000000`0940b000 fffff700`010ae220 : nt!KeBugCheckEx fffff880`0832d000 fffff800`0284e5a2 : fffffa80`05e33060 fffffa80`00001f05 fffff8a0`00001dd0 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x33a23 fffff880`0832d8b0 fffff800`02b61c4f : fffff8a0`02480a70 fffff880`0832dc20 00000000`00000000 fffffa80`03dfeb60 : nt!MmCleanProcessAddressSpace+0x96 fffff880`0832d900 fffff800`02b3a4d1 : 00000000`c0000005 fffff800`02898f01 000007ff`fffac000 fffffa80`05e9cb60 : nt!PspExitThread+0x92f fffff880`0832d9c0 fffff800`028580e3 : 00000000`00000000 fffff880`0832db40 00000000`00000000 fffff800`02876df0 : nt!PsExitSpecialApc+0x1d fffff880`0832d9f0 fffff800`02858520 : 00000000`08f5fa10 fffff880`0832da70 fffff800`02b3a5dc 00000000`00000001 : nt!KiDeliverApc+0x2eb fffff880`0832da70 fffff800`0287a8f7 : fffffa80`03dfeb60 00000000`08f5f8f8 fffff880`0832dbc8 0000007f`ffffffff : nt!KiInitiateUserApc+0x70 fffff880`0832dbb0 00000000`7767030a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c 00000000`08f5f8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7767030a   STACK_COMMAND:  kb  FOLLOWUP_IP:  nt! ?? ::FNODOBFM::`string'+33a23 fffff800`028eefb3 cc              int     3  SYMBOL_STACK_INDEX:  1  SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33a23  FOLLOWUP_NAME:  MachineOwner  MODULE_NAME: nt  IMAGE_NAME:  ntkrnlmp.exe  DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb  FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+33a23  BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+33a23  Followup: MachineOwner ---------

Lulubop

I have it enable following all the steps, but I'm curious as to how I find the memory dump file if/when the blue screen does occur. Or is it the same process I already posted.

Thanks.

Jonathan_King

It's the same process you used to upload the other dumps.

Lulubop

Well, since starting the Verifier I have yet to have a BSOD. I like it's safe to rule out any drivers being the issue and I believe the issue is actually with the Memory. Browsing around the board, I ran into a topic where the poster had a similar issue of only getting BSOD on start up and only in the morning after hours of not using there computer. I used the Memok feature that comes with the Mobo and no BSOD for the first time in a few days. I have no idea if this is nothing more than a quick fix, but it seems to be fine for now. Though my desktop windows manager still enables and disables itself during the first few minutes of start up with out warning. Weather that's related to the BSOD I don't know.

Guest

It looks like, according to the dump that JK posted, the MmCleanProcessAddressSpace function was actually called by MiDeleteAllHashMappings:

Code:

1: kd> kn  # Child-SP          RetAddr           Call Site 00 fffff880`0832cff8 fffff800`028eefb3 nt!KeBugCheckEx 01 fffff880`0832d000 fffff800`0284e5a2 nt! ?? ::FNODOBFM::`string'+0x33a23 02 fffff880`0832d8b0 fffff800`02b61c4f nt!MmCleanProcessAddressSpace+0x96 03 fffff880`0832d900 fffff800`02b3a4d1 nt!PspExitThread+0x92f 04 fffff880`0832d9c0 fffff800`028580e3 nt!PsExitSpecialApc+0x1d 05 fffff880`0832d9f0 fffff800`02858520 nt!KiDeliverApc+0x2eb 06 fffff880`0832da70 fffff800`0287a8f7 nt!KiInitiateUserApc+0x70 07 fffff880`0832dbb0 00000000`7767030a nt!KiSystemServiceExit+0x9c 08 00000000`08f5f8d8 00000000`00000000 0x7767030a  1: kd> u fffff800`0284e5a2 nt!MmCleanProcessAddressSpace+0x96: fffff800`0284e5a2 488d8e98030000  lea     rcx,[rsi+398h] fffff800`0284e5a9 e8920c0000      call    nt!MiDeleteAllHashMappings (fffff800`0284f240) fffff800`0284e5ae 488bc3          mov     rax,rbx fffff800`0284e5b1 f0480fc18698030000 lock xadd qword ptr [rsi+398h],rax fffff800`0284e5ba a802            test    al,2 fffff800`0284e5bc 0f853e990a00    jne     nt! ?? ::FNODOBFM::`string'+0x3db00 (fffff800`028f7f00) fffff800`0284e5c2 80a750040000f7  and     byte ptr [rdi+450h],0F7h fffff800`0284e5c9 664401afc6010000 add     word ptr [rdi+1C6h],r13w

It looks like, ultimately, cleaning up process space is causing issues on this box. Most of the dumps are exactly the same in exactly the same spot in svchost.exe code, so I'd say it's not very likely this is a hardware or RAM issue, but perhaps a refcount issue in svchost or one of your kernel filter drivers. I'd be taking these to Microsoft PSS, honestly, and getting them to work with you on this.

Lulubop

BSOD again upon start up today.

Jonathan_King

I suspect the issue is caused by your outdated ASACPI.sys file. Please install the latest ATK0110 Utility for Windows 7/Vista from here: ASUSTeK Computer Inc.-Support-

...Summary of the Dumps:

Code:

 Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Fri Jul 30 14:00:36.069 2010 (UTC - 4:00) System Uptime: 0 days 0:02:15.146 BugCheck C1, {fffff9800bab4fe0, fffff9800bab4018, 9b001c, 23} Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+9a ) BUGCHECK_STR:  0xC1_23 DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME:  aim.exe �������������������������������������������������������������������������������������� 

Lulubop

I BSOD trying to install the new driver.

Jonathan_King

Did you clean out the Minidump folder after the last one? There are no dumps in that folder for some reason...not even old ones.

Lulubop

wELL


Dump File 073010-20576-01.dmp
Crash Time 7/30/2010 4:37:17 PM
Bug Check String DRIVER_VERIFIER_IOMANAGER_VIOLATION
Bug Check Code 0x000000c9
Parameter 1 00000000`0000022f
Parameter 2 fffff880`03ff09a0
Parameter 3 fffff980`1aaf2cf0
Parameter 4 00000000`00000000
Caused By Driver ASACPI.sys
Caused By Address ASACPI.sys+19a0
File Description
Product Name
Company
File Version
Processor x64
Computer Name
Full Path C:\Windows\MiniDump\073010-20576-01.dmp
Processors Count 4
Major Version 15
Minor Version 7600

Jonathan_King

Keep trying to install that driver...you may try using Safe Mode.

Safe Mode

Lulubop

I'll try again, but I did have the Driver Verifier running, and it seems to have caused it when I tried to install the new driver.


Dump File 073010-20576-01.dmp
Crash Time 7/30/2010 4:37:17 PM
Bug Check String DRIVER_VERIFIER_IOMANAGER_VIOLATION
Bug Check Code 0x000000c9
Parameter 1 00000000`0000022f
Parameter 2 fffff880`03ff09a0
Parameter 3 fffff980`1aaf2cf0
Parameter 4 00000000`00000000
Caused By Driver ASACPI.sys
Caused By Address ASACPI.sys+19a0
File Description
Product Name
Company
File Version
Processor x64
Computer Name
Full Path C:\Windows\MiniDump\073010-20576-01.dmp
Processors Count 4
Major Version 15
Minor Version 7600

Jonathan_King

Turn off driver verifier, by running verifier.exe and selecting "delete existing setting".

Then try to update that driver, using Safe Mode if necessary.

Lulubop

Still can't, all I get is a black box that disappears immediately when I try and install. I try to look for the latest driver updates on for ATTK0110 on the device manager but it says I'm up to date. Is ok to remove it completely?

Jonathan_King

That black box is what is installing the drivers. Check in C:\Windows\System32\Drivers and right-click on the ASACPI.sys file. See if the date is now 2009 or 2010.

Lulubop

I see, sorry. It reads 5/14/2009.

Jonathan_King

Great, let's hope the BSODs stop now.

Lulubop

No BSOD yesterday, but here we go again. *sigh*

Jonathan_King

�� Quote: Originally Posted by Lulubop

I see, sorry. It reads 5/14/2009.

And it still does in the most recent BSOD.

Lulubop

Time to test hardware.

�� Quote: Originally Posted by JK

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.

Test hard drive: HD Diagnostic

See this tutorial on testing CPU: http://www.sevenforums.com/tutorials...t-prime95.html

...Summary of the Dumps:

Code:

 Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sun Aug  1 13:28:31.814 2010 (UTC - 4:00) System Uptime: 0 days 0:03:47.844 BugCheck 1A, {41284, 1c93001, 0, fffff70001080000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 ) BUGCHECK_STR:  0x1a_41284 PROCESS_NAME:  WerFault.exe �������������������������������������������������������������������������������������� Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sun Aug  1 13:23:42.607 2010 (UTC - 4:00) System Uptime: 0 days 0:30:33.012 BugCheck 34, {50830, fffff8800317e4b8, fffff8800317dd20, fffff8000289588c} Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+17c ) PROCESS_NAME:  System BUGCHECK_STR:  0x34 �������������������������������������������������������������������������������������� 

Jonathan_King

I stressed tested my CPU with the Intel Burn test and it was said to be unstable. Not sure what to do now.

Lulubop

Test with Prime95, just to get a second opinion: http://www.sevenforums.com/tutorials...t-prime95.html

Are you overclocking at all? If so, restore to defaults. If not, make sure the BIOS settings are set to "Auto".

Lulubop

According to the dumps, the CPU isn't overclocked:

Code:

3: kd> !sysinfo cpuinfo [CPU Information] ~MHz = REG_DWORD 2666 Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0 Identifier = REG_SZ Intel64 Family 6 Model 30 Stepping 5 ProcessorNameString = REG_SZ Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz Update Signature = REG_BINARY 0,0,0,0,3,0,0,0 Update Status = REG_DWORD 2 VendorIdentifier = REG_SZ GenuineIntel MSR8B = REG_QWORD 300000000

However, I would have to second JK's suggestion of using Prime95 as a "second opinion" (I like that wording too). However, if you flunk out of Prime95, that would confirm the CPU is bad, or you have poor cooling, or a bum PSU, etc. You'll have to focus on your hardware at that point and determine for yourself how you want to proceed in attempting to fix it.

Guest

I will try Prime 95, I'm assuming I'll have to leave my computer on for the as long as the test take? No overclocking, and all the setting on BIOS are auto/default.

Guest

Sorry for the double post. I'm using Core Temp to see how hot the temperatures get, will the test stop automatically when it's becoming to hot, or should I stop when It gets to a certain temperature?

Jonathan_King

The Prime95 test will run indefinitely, until it errors out or you stop it. Let it run for at least 6 hours, unless it stops on its own sooner.

Use Speedfan to monitor your temps as you do.

SpeedFan - Access temperature sensor in your computer

Lulubop

Using Prime 95, the Temperatures were immediately in the Mid 90s c Which caused me to stop. They're about high twenties- Mid thirties when just browsing.

Jonathan_King

I wonder if that is the problem, then. Open up the side of your case, and first, clean out any dust. Then blow a fan inside.

Lulubop

Well this computer is about 2 weeks old, I opened it up no real dust or anything.

Lulubop

I did some research, and it seems others have seen their i5 750s get up around the 91-92C mark under Prime95 load as well with the stock Intel cooler. If it runs that hot under load, unless they've done some massive engineering that processor is going to have a very short life if you ride it hard. According to Intel's docs on the part, the Tcase (maximum safe operating temperature) is ~72C, so 90C under load would indicate a very poor cooling solution (I'm guessing you're using the stock Intel cooler). There are folks out there who run the same CPU overclocked to 3+GHz and stay under 50C running Prime95, to give you an idea of how poor Intel's cooling solutions are.

Lulubop

I see, well yea I'm using the stock cooler. I will try to buy some Paste tomorrow and see if that helps, but I don't understand how that would be the cause of BS under a relatively light load since it usually only occurs around start up.

Jonathan_King

You do realize that startup and shutdown are the busiest time for the CPU, with drivers causing interrupts as they load or unload, clearing the DPC queue backlog, handling all of the events and start (or shutdown) of apps and services, etc...? Assuming a relatively even (and minimal) CPU load during normal usage, startup and shutdown are the hardest times your CPU will face.

Lulubop

More BSOD. They're becoming more frequent. This is becoming quiet the headache.

Guest

Have you addressed the heat issue yet? Make sure you have plenty of ventilation in the case.

Open the side and blow a fan inside while you work.

Guest

Well my computer did not crash from any stress test, and during the intel burn test using the standard memory size opition my computer passed, though it did get very hot.

The first time this problem occurred about two weeks ago, I thought it was because of the memory so I used the Memok feature not realizing that ASUS advises to upgrade your BIOS after. So I'm wondering if this could be BIOS related? Also I feel the need to try and uninstall and reinstall the drivers for my GPU. I'll also look into the temperature situation. It seems as if I'm getting a BSOD every time now.

Lulubop

Hmmm, so I've tried using just 1 memory stick and I've yet to BSOD. It doesn't matter which stick it is, which is weird. Any possible reasoning for this? I'd obviously like to to use both and have a stable computer. Also lately the Mouse has been randomly not working, no matter what USB port it's plugged into. Plugging it out than in fixes it, but it's just odd.

Jonathan_King

Sounds like a compatibility issue. Are the sticks the same brand/model?

Lulubop

Yea, they both are the same RAM.

Lulubop

So I got a BSOD trying to uninstall and reinstall the drivers for the GPU. I managed to finish the process, but I'm not sure I did it correctly and I'm still having an the issue of the DWM disabling itself for a few minutes with no warning or reason and then enabling itself again. I don't think the BSOD is related to the others however.

Lulubop

�� Quote: Originally Posted by Lulubop

Yea, they both are the same RAM.

Hate to tell you but 14 of 16 crashes were caused by memory management. You need to test each stick by itself, and each mobo slot as well. I assume you are using memtest but in case.

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.

Code:

080610-22230-01.dmp    8/6/2010 22:46:54    SYSTEM_SERVICE_EXCEPTION     0x0000003b    00000000`c0000005    fffff960`0001da1a     fffff880`0734a3f0    00000000`00000000    win32k.sys     win32k.sys+1da1a                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080610-22230-01.dmp    4     15    7600     080210-22557-01.dmp    8/2/2010 14:27:00    MEMORY_MANAGEMENT     0x0000001a    00000000`00005003    fffff700`01080000     00000000`00001fe1    00001fe3`00003fc3    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080210-22557-01.dmp    4     15    7600     080310-18252-01.dmp    8/3/2010 14:40:20    MEMORY_MANAGEMENT     0x0000001a    00000000`00041284    00000000`6d40b001     00000000`00000000    fffff700`01080000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080310-18252-01.dmp    4     15    7600     080410-17877-01.dmp    8/4/2010 14:07:36    MEMORY_MANAGEMENT     0x0000001a    00000000`00041284    00000000`6d223001     00000000`00000000    fffff700`01080000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080410-17877-01.dmp    4     15    7600     080410-20217-01.dmp    8/4/2010 19:00:36    MEMORY_MANAGEMENT     0x0000001a    00000000`00005100    fffff6fc`80621258     00000000`00000707    00000000`00000001    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080410-20217-01.dmp    4     15    7600     080410-20763-01.dmp    8/4/2010 14:12:54    MEMORY_MANAGEMENT     0x0000001a    00000000`00041790    fffffa80`016bf360     00000000`0000ffff    00000000`00000000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080410-20763-01.dmp    4     15    7600     080510-18033-01.dmp    8/5/2010 17:59:58    MEMORY_MANAGEMENT     0x0000001a    00000000`00041201    fffff680`00091058     00000000`00000001    fffffa80`05c3d470    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-18033-01.dmp    4     15    7600     080510-18174-01.dmp    8/5/2010 16:58:10    MEMORY_MANAGEMENT     0x0000001a    00000000`00005100    fffff6fc`80628058     00000000`00000077    00000000`00000001    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-18174-01.dmp    4     15    7600     080510-18267-01.dmp    8/5/2010 20:57:52    MEMORY_MANAGEMENT     0x0000001a    00000000`00041790    fffffa80`016fc9e0     00000000`0000ffff    00000000`00000000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-18267-01.dmp    4     15    7600     080510-20108-01.dmp    8/5/2010 16:51:32    MEMORY_MANAGEMENT     0x0000001a    00000000`00041201    fffff680`00007758     00000000`00000001    fffffa80`041cf5c0    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-20108-01.dmp    4     15    7600     080510-20202-01.dmp    8/5/2010 21:36:16    MEMORY_MANAGEMENT     0x0000001a    00000000`00041790    fffffa80`0172c410     00000000`0000ffff    00000000`00000000    win32k.sys     win32k.sys+5ae8d                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-20202-01.dmp    4     15    7600     080510-20545-01.dmp    8/5/2010 16:46:46    MEMORY_MANAGEMENT     0x0000001a    00000000`00041284    00000000`ff213001     00000000`00000000    fffff700`01080000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-20545-01.dmp    4     15    7600     080510-21184-01.dmp    8/5/2010 17:11:12    MEMORY_MANAGEMENT     0x0000001a    00000000`00005003    fffff700`01080000     00000000`00000839    0000083b`00001073    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-21184-01.dmp    4     15    7600     080610-17581-01.dmp    8/6/2010 23:04:02    MEMORY_MANAGEMENT     0x0000001a    00000000`00041284    00000000`ff42b001     00000000`00000000    fffff700`01080000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080610-17581-01.dmp    4     15    7600     080610-19188-01.dmp    8/6/2010 22:42:02     CRITICAL_OBJECT_TERMINATION    0x000000f4    00000000`00000003     fffffa80`058a5b30    fffffa80`058a5e10    fffff800`02dcc540     ntoskrnl.exe    ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080610-19188-01.dmp    4     15    7600     080810-30092-01.dmp    8/8/2010 19:15:18        0x00000116     fffffa80`03f06010    fffff880`0481e694    00000000`00000000     00000000`00000002    dxgkrnl.sys    dxgkrnl.sys+5cef8                     x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080810-30092-01.dmp    4     15    7600

Lulubop

�� Quote: Originally Posted by Lulubop

So I got a BSOD trying to uninstall and reinstall the drivers for the GPU. I managed to finish the process, but I'm not sure I did it correctly and I'm still having an the issue of the DWM disabling itself for a few minutes with no warning or reason and then enabling itself again. I don't think the BSOD is related to the others however.

Hate to tell you but 14 of 16 crashes were caused by memory management. You need to test each stick by itself, and each mobo slot as well. I assume you are using memtest but in case.

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.

Code:

080610-22230-01.dmp    8/6/2010 22:46:54    SYSTEM_SERVICE_EXCEPTION     0x0000003b    00000000`c0000005    fffff960`0001da1a     fffff880`0734a3f0    00000000`00000000    win32k.sys     win32k.sys+1da1a                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080610-22230-01.dmp    4     15    7600     080210-22557-01.dmp    8/2/2010 14:27:00    MEMORY_MANAGEMENT     0x0000001a    00000000`00005003    fffff700`01080000     00000000`00001fe1    00001fe3`00003fc3    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080210-22557-01.dmp    4     15    7600     080310-18252-01.dmp    8/3/2010 14:40:20    MEMORY_MANAGEMENT     0x0000001a    00000000`00041284    00000000`6d40b001     00000000`00000000    fffff700`01080000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080310-18252-01.dmp    4     15    7600     080410-17877-01.dmp    8/4/2010 14:07:36    MEMORY_MANAGEMENT     0x0000001a    00000000`00041284    00000000`6d223001     00000000`00000000    fffff700`01080000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080410-17877-01.dmp    4     15    7600     080410-20217-01.dmp    8/4/2010 19:00:36    MEMORY_MANAGEMENT     0x0000001a    00000000`00005100    fffff6fc`80621258     00000000`00000707    00000000`00000001    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080410-20217-01.dmp    4     15    7600     080410-20763-01.dmp    8/4/2010 14:12:54    MEMORY_MANAGEMENT     0x0000001a    00000000`00041790    fffffa80`016bf360     00000000`0000ffff    00000000`00000000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080410-20763-01.dmp    4     15    7600     080510-18033-01.dmp    8/5/2010 17:59:58    MEMORY_MANAGEMENT     0x0000001a    00000000`00041201    fffff680`00091058     00000000`00000001    fffffa80`05c3d470    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-18033-01.dmp    4     15    7600     080510-18174-01.dmp    8/5/2010 16:58:10    MEMORY_MANAGEMENT     0x0000001a    00000000`00005100    fffff6fc`80628058     00000000`00000077    00000000`00000001    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-18174-01.dmp    4     15    7600     080510-18267-01.dmp    8/5/2010 20:57:52    MEMORY_MANAGEMENT     0x0000001a    00000000`00041790    fffffa80`016fc9e0     00000000`0000ffff    00000000`00000000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-18267-01.dmp    4     15    7600     080510-20108-01.dmp    8/5/2010 16:51:32    MEMORY_MANAGEMENT     0x0000001a    00000000`00041201    fffff680`00007758     00000000`00000001    fffffa80`041cf5c0    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-20108-01.dmp    4     15    7600     080510-20202-01.dmp    8/5/2010 21:36:16    MEMORY_MANAGEMENT     0x0000001a    00000000`00041790    fffffa80`0172c410     00000000`0000ffff    00000000`00000000    win32k.sys     win32k.sys+5ae8d                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-20202-01.dmp    4     15    7600     080510-20545-01.dmp    8/5/2010 16:46:46    MEMORY_MANAGEMENT     0x0000001a    00000000`00041284    00000000`ff213001     00000000`00000000    fffff700`01080000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-20545-01.dmp    4     15    7600     080510-21184-01.dmp    8/5/2010 17:11:12    MEMORY_MANAGEMENT     0x0000001a    00000000`00005003    fffff700`01080000     00000000`00000839    0000083b`00001073    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080510-21184-01.dmp    4     15    7600     080610-17581-01.dmp    8/6/2010 23:04:02    MEMORY_MANAGEMENT     0x0000001a    00000000`00041284    00000000`ff42b001     00000000`00000000    fffff700`01080000    ntoskrnl.exe     ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080610-17581-01.dmp    4     15    7600     080610-19188-01.dmp    8/6/2010 22:42:02     CRITICAL_OBJECT_TERMINATION    0x000000f4    00000000`00000003     fffffa80`058a5b30    fffffa80`058a5e10    fffff800`02dcc540     ntoskrnl.exe    ntoskrnl.exe+70600                    x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080610-19188-01.dmp    4     15    7600     080810-30092-01.dmp    8/8/2010 19:15:18        0x00000116     fffffa80`03f06010    fffff880`0481e694    00000000`00000000     00000000`00000002    dxgkrnl.sys    dxgkrnl.sys+5cef8                     x64         C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\080810-30092-01.dmp    4     15    7600

Jonathan_King

Well yea, I'm assuming the Memory is in fact the issue. I've been using 1 Stick the last two days and have only BSOD once and I explained that in my previous post. I have tested both sticks multiple times, as well as tried different slots. The only thing that seems to not cause any BSOD is using one stick. I have no idea why that is.

Also I believe my GPU is also giving me problems, and I posted the Blue Screen I got during the installing and reinstalling of it's drivers. I'm not sure why I got BSOD during that either. I'm not sure I uninstalled it correctly, since I also have to uninstall the CCC it comes with

DoDoENT

Alright, so I thought it was a problem on the HD since I apparently had some corrupt files. I couldn't complete a sfc/scannow and the system maintenance kept saying I had disc volume errors. So I decided to reinstall windows, which I had been playing to do and today it's back to crashing. Though the probably with the HD seem to be fixed, sine I have no errors and sfc/scannow sees no problems.

Guest

Please update your Realtek network drivers:

Code:

Rt64win7.sys Thu Feb 26 04:04:13 2009

Look on your computer manufacturer's site, or go here: Realtek

...Summary of the Dumps:

Code:

 Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Wed Aug 11 13:16:16.163 2010 (UTC - 4:00) System Uptime: 0 days 0:06:23.709 BugCheck 1A, {41790, fffffa80016a74e0, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 ) BUGCHECK_STR:  0x1a_41790 PROCESS_NAME:  mscorsvw.exe �������������������������������������������������������������������������������������� 

Guest

Lulubop, looks like we may have the same problem and same motherboards. If so, then maybe my temporary solution will help you:

0) put back your memory sticks as they were on the beginning of this discussion
1) boot your computer, it should crash on boot
2) restart, enter the BIOS, go to the tab that has 'CPU configuration' section
3) open the 'CPU Configuration' section
4) if your CPU supports Virtualization Technology, disable it; if your CPU supports Hyperthreading, disable it; if nothing of these aren't supported in your CPU, find a place in BIOS where you can change your RAM frequency and change it (no matter to which value)
5) save you BIOS settings, your computer should automatically turn off and then turn on in a few seconds (this kind of reset is important)
6) now enter BIOS again and restore all settings to the values prior doing step 4
7) after saving settings and restarting your computer should be stable until the end of the day
*) the next day your windows will crash again on boot, but the same procedure should make it stable again. If you want to have your computer stable for more than one day, do not turn it off, use 'sleep' instead.

This procedure helps me, and it's not windows-related problem - it also happens on linux.
I thought it was a hardware malfunction, so I brought my computer to the service, as it's only few weeks old and under warranty.

If this procedure helps you too, then it means that our computers are not malfunctioned, but instead there is some kind of incompatibility between motherboard, processor and memory that should be reported to Asus.

Lulubop

Well my computer hadn't bsod when I put just stick in the a2 dimm slot. However there were other issues with windows. These problems included windows not saving the changes I made as well as files corruption. But now I have another major problem, after performing another chkdsk scan windows will not start up at all. After the windows start up screen the computer just restarts. No bsod just a restart, it then says I should run the windows repair program and it find an unfixable issue. I can't system restore, nor do I think it'll be much help and even trying to start up in safe mode results in this.