BSOD and freezes W7 64 bit

derrickburns said:

I am getting BSOD and freezes on my custom built W7 64 system. Any help would be greatly appreciated!

Attached are 4 recent minidumps in a rar file.

Thanks in advance!

Hi and welcome

Well Im going to have to go out on a limb. You have memory corruption in at least to of the crashes. in teh other two it cuold alos be memory but it is not specified

I would downlaod and run memetestx86 for several hour at least

then run a system file check to verify and fix system files
type cmd in search>right click and run as admin>sfc /scannow
if you are overclocking STOP
if you have a rais update its driver

Ken J++


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\112709-31340-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e5ae50
Debug session time: Fri Nov 27 20:52:01.963 2009 (GMT-5)
System Uptime: 2 days 6:59:50.539
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffff8b49105c, 1, fffff88002578447, 5}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: 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: ffffffff8b49105c, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88002578447, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec50e0
ffffffff8b49105c

FAULTING_IP:
bowser!BowserSecurityCheck+c3
fffff880`02578447 008b5b10498b add byte ptr [rbx-74B6EFA5h],cl

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x50

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880062eb680 -- (.trap 0xfffff880062eb680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0025c0001 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8a0025c0060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002578447 rsp=fffff880062eb810 rbp=fffff880062ebca0
r8=fffff8a0025c006c r9=fffffa800477a268 r10=fffff8a0025c0060
r11=fffff880062eb880 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
bowser!BowserSecurityCheck+0xc3:
fffff880`02578447 008b5b10498b add byte ptr [rbx-74B6EFA5h],cl ds:00e4:ffffffff`8b49105b=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002d0cb91 to fffff80002c8ef00

STACK_TEXT:
fffff880`062eb518 fffff800`02d0cb91 : 00000000`00000050 ffffffff`8b49105c 00000000`00000001 fffff880`062eb680 : nt!KeBugCheckEx
fffff880`062eb520 fffff800`02c8cfee : 00000000`00000001 00000000`00000001 fffff880`062eb800 00000000`001901ff : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`062eb680 fffff880`02578447 : fffff880`062ebca0 00000000`00000001 fffffa80`047c99e8 00000000`0b5bc2f0 : nt!KiPageFault+0x16e
fffff880`062eb810 fffff880`02584a60 : 00000000`00000000 fffffa80`001f01ff fffff8a0`0c72e280 fffffa80`001f01ff : bowser!BowserSecurityCheck+0xc3
fffff880`062eb890 fffff880`02576130 : fffffa80`04923690 00000000`00000000 00000000`00000001 00000000`00000003 : bowser!BowserCommonDeviceIoControlFile+0x9c8
fffff880`062eb9e0 fffff800`02fa73a7 : fffffa80`04d7c3d0 fffffa80`04d7c3d0 fffffa80`047c9a30 fffffa80`047c9840 : bowser!BowserFsdDispatch+0xa8
fffff880`062eba10 fffff800`02fa7c06 : 00000000`02d5fae8 00000000`000011c4 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`062ebb40 fffff800`02c8e153 : fffffa80`04cc3780 00000000`02d5fac8 fffff880`062ebbc8 00000000`02d5fc10 : nt!NtDeviceIoControlFile+0x56
fffff880`062ebbb0 00000000`7773ff2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02d5fb38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7773ff2a


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !bowser
8 errors : !bowser (fffff88002578447-fffff8800257847f)
fffff88002578440 4c 8d 5c 24 70 8a c3 *00 8b 5b 10 49 8b 73 20 *30 L.\$p....[.I.s 0
fffff88002578450 8b e3 5f c3 cc cc cc *00 cc cc cc cc 48 89 5c *00 .._.........H.\.
fffff88002578460 08 48 89 6c 24 18 56 *00 41 54 48 83 ec 20 48 *00 .H.l$.V.ATH.. H.
fffff88002578470 f1 c7 44 24 48 03 00 *00 00 ff 15 91 0c 00 00 *00 ..D$H...........

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Looking at the your board manual you should be able to tweak ram voltage. Have you updated bios? It looks like ver. 0212 fix the problem you're having.

Luck-

Here's 2 older drivers on the system. The second one is known to cause BSOD's (in the 2005 version) in Win7. Please update either the AISuite or PCProbe programs from the Asus website to fix it.

Code:

ltmdm64.sys  Wed Mar 08 09:28:58 2006
ASACPI.sys   Sun Mar 27 22:30:36 2005

Because of the involvement (in the stack) of bowser.sys - and that there's user-mode involvement in the stack also - I'd suspect an internet/network aware program that's issuing bad requests.

In order to narrow it down, I'd suggest using Driver Verifier according to the following instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.


So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).


Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.


Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.


Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users