Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD on Win 7 startup- trying to pinpoint cause

23 Sep 2011   #1

Win 7 32b Ultimate
 
 
BSOD on Win 7 startup- trying to pinpoint cause

Hi guys/girls,

I am at my wits end with this thing. I have tried a number of approaches following instructions on the net but unable to pin point the error. I am considering using the tower to practise my shotput. I am in no way an expert but Im not a caveman with a keyboard either.

Before it is suggested, I tried to follow the steps on the "Blue Screen of Death (BSOD) Posting Instructions " thread but when I attempted to download the exe file it threw out this:

Malware Detected
The transferred file contained a virus and was therefore blocked.
URL: jcgriff2.com/0x2/Windows_NT6_BSOD_v3.03_jcgriff2_.exe
Media Type: application/executable
Virus Name: McAfeeGW: Artemis!566F01BB4EF2
generated 2011-09-24 11:26:26 by McAfee Web Gateway

So I left that well alone.


Brief desription of problem:
About 1/5 cold boots results on a blue screen. It usually has a ntdll.dll error but there has been others such as win32k and "process1_fail_to_initialise". A restart comes to the "start normally or windows repair" screen. Starting normally results in the windows loading screen, followed by black desktop. Curiously the mouse pointer is there and responds but nothing else (eg. alt+ctrl+del) responds. Windows repair just loops with a few more blue screens and eventually it comes good.

I've found if I just turn the whole sytem off at the first blue screen, it works fine on the next cold boot when I select "start windows normally".

I suspect its a driver issue. I have the latest drivers for my ATI Radeon HD 5550 card and its never missed a beat playing games like Fallout 3 etc. It might be something on the ASUS M4A89GTD Pro/usb3 mb but I have the most updated drivers for that too. I have had crashes to desktop on Adobe Premiere CS4 but I understand that program has more holes than swiss cheese, so I don't give it too much thought. All other programs/games are rock-solid stable.

I am using on-board sound, but have noticed two occasions where windows starts up with no sound. I checked the device manager and saw there were two "windows standard audio devices". I suspect one of these was the onboard HD audio so I disabled one of these (the one that didn't shut off my sound) but that hasn't worked.

Ive had this PC for about 18 months now. I have attempted upgrading drivers, disabling different periphials, running without the cheapo wireless network card. I've tried memtest86 with no problems, prime95 for about 4 hours with no issue. I've got no virus scanning software, and Ive checked out everything with malwarebytes. I don't overclock, don't use google chrome (firefox all the way baby!) and don't want to cry!

Specs:
AMD Phenom 2 x4 955 3.5Ghz quad core
AT Radeon HD 5550
Asus M4A89GTD Pro/Usb3
x4 GB DDR3
Win 7 x32 bit (think Ultimate) retail
1tb HDD

Minidumps:
I got hold of the windows debugger tool and pasted the results for my last few crashes.

Code:
 
11/09/11 
 
Loading Dump File [C:\Windows\Minidump\091111-16785-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x83456000 PsLoadedModuleList = 0x835a0850
Debug session time: Sun Sep 11 14:31:37.387 2011 (GMT+8)
System Uptime: 0 days 0:00:13.620
Loading Kernel Symbols
...............................................................
.....................
Loading User Symbols
0: kd> !analyze -v 
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
PROCESS1_INITIALIZATION_FAILED (6b)
Arguments:
Arg1: 00000000, Indicates the NT status code that caused the failure.
Arg2: 00000000, (reserved)
Arg3: 00000000
Arg4: 00000000
 
Debugging Details:
------------------
 
 
CUSTOMER_CRASH_COUNT: 1
 
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
 
BUGCHECK_STR: 0x6B
 
PROCESS_NAME: System
 
CURRENT_IRQL: 0
 
LAST_CONTROL_TRANSFER: from 8380a583 to 83534ef7
 
STACK_TEXT: 
80786c6c 8380a583 0000006b 85d02af8 85d02788 nt!KeBugCheck+0x14
80786d48 835e3440 80786d90 8365ff5e 8080a500 nt!Phase1InitializationDiscard+0x4e
80786d50 8365ff5e 8080a500 ac3b0ca2 00000000 nt!Phase1Initialization+0xd
80786d90 83507219 835e3433 8080a500 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
STACK_COMMAND: kb
 
FOLLOWUP_IP: 
nt!Phase1InitializationDiscard+4e
8380a583 cc int 3
 
SYMBOL_STACK_INDEX: 1
 
SYMBOL_NAME: nt!Phase1InitializationDiscard+4e
 
FOLLOWUP_NAME: MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME: ntkrpamp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09
 
FAILURE_BUCKET_ID: 0x6B_nt!Phase1InitializationDiscard+4e
 
BUCKET_ID: 0x6B_nt!Phase1InitializationDiscard+4e
 
Followup: MachineOwner
---------
 
 
12/09/11 
 
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\091211-27471-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x83437000 PsLoadedModuleList = 0x83581850
Debug session time: Mon Sep 12 15:01:29.244 2011 (GMT+8)
System Uptime: 0 days 0:00:23.852
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1000008E, {c0000005, 82b69ceb, 82354af4, 0}
 
Probably caused by : memory_corruption
 
Followup: memory_corruption
---------
 
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82b69ceb, The address that the exception occurred at
Arg3: 82354af4, Trap Frame
Arg4: 00000000
 
Debugging Details:
------------------
 
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
 
FAULTING_IP: 
win32k!zzzBltValidBits+49
82b69ceb 0300 add eax,dword ptr [eax]
 
TRAP_FRAME: 82354af4 -- (.trap 0xffffffff82354af4)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=00010004 edx=000000cd esi=ffbbd198 edi=82cff560
eip=82b69ceb esp=82354b68 ebp=82354bd4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!zzzBltValidBits+0x49:
82b69ceb 0300 add eax,dword ptr [eax] ds:0023:00000000=????????
Resetting default scope
 
CUSTOMER_CRASH_COUNT: 1
 
DEFAULT_BUCKET_ID: CODE_CORRUPTION
 
BUGCHECK_STR: 0x8E
 
PROCESS_NAME: csrss.exe
 
CURRENT_IRQL: 0
 
LAST_CONTROL_TRANSFER: from 82b7e1a3 to 82b69ceb
 
STACK_TEXT: 
82354bd4 82b7e1a3 82cff560 00000000 ff660618 win32k!zzzBltValidBits+0x49
82354c2c 82b7e56a ffbbd478 ff660618 00000001 win32k!xxxEndDeferWindowPosEx+0x14e
82354c4c 82b00789 ff660618 00000000 00000000 win32k!xxxSetWindowPos+0xf6
82354cbc 82aed1ee 00000000 87f5fd48 00000000 win32k!xxxSwitchDesktop+0x309
82354d04 82afd7c7 82322400 00000002 82322400 win32k!RawInputThread+0x3fe
82354d18 82bb2b5d 00000004 00befdf8 82354d34 win32k!xxxCreateSystemThreads+0x4a
82354d28 834751ea 00000004 00befe38 76eb70b4 win32k!NtUserCallNoParam+0x1b
82354d28 76eb70b4 00000004 00befe38 76eb70b4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00befe38 00000000 00000000 00000000 00000000 0x76eb70b4
 
 
STACK_COMMAND: kb
 
CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
82b69ce8 - win32k!zzzBltValidBits+46
[ e8:ec ]
1 error : !win32k (82b69ce8)
 
MODULE_NAME: memory_corruption
 
IMAGE_NAME: memory_corruption
 
FOLLOWUP_NAME: memory_corruption
 
DEBUG_FLR_IMAGE_TIMESTAMP: 0
 
MEMORY_CORRUPTOR: ONE_BIT
 
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
 
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
 
Followup: memory_corruption
 
 
12/09/11 
 
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\091211-15678-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x83439000 PsLoadedModuleList = 0x83583850
Debug session time: Mon Sep 12 19:00:40.580 2011 (GMT+8)
System Uptime: 0 days 0:00:09.188
Loading Kernel Symbols
.....................................................
Loading User Symbols
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
Unknown bugcheck code (c0000221)
Unknown bugcheck description
Arguments:
Arg1: 8d0645f0
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
 
Debugging Details:
------------------
 
 
BUGCHECK_STR: 0xc0000221
 
ERROR_CODE: (NTSTATUS) 0xc0000221 - {Bad Image Checksum} The image %hs is possibly corrupt. The header checksum does not match the computed checksum.
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000221 - {Bad Image Checksum} The image %hs is possibly corrupt. The header checksum does not match the computed checksum.
 
EXCEPTION_PARAMETER1: 8d0645f0
 
EXCEPTION_PARAMETER2: 00000000
 
EXCEPTION_PARAMETER3: 00000000
 
EXCEPTION_PARAMETER4: 0
 
MODULE_NAME: nt
 
IMAGE_NAME: ntkrpamp.exe
 
CUSTOMER_CRASH_COUNT: 1
 
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
 
PROCESS_NAME: System
 
CURRENT_IRQL: 0
 
LAST_CONTROL_TRANSFER: from 8376492f to 83517f20
 
STACK_TEXT: 
807866f4 8376492f 0000004c c0000221 80786728 nt!KeBugCheckEx+0x1e
807868b0 83612d2e c0000221 00000001 00000001 nt!ExpSystemErrorHandler+0x56c
80786a60 8373e2b3 c0000221 00000001 00000001 nt!ExpRaiseHardError+0xbf
80786ae8 8361221d c0000221 00000001 00000001 nt!ExRaiseHardError+0x151
80786b58 835b4fde c0000221 00000001 00000001 nt!NtRaiseHardError+0x179
80786bc0 835b4f26 00000000 837a4f3c 8080a500 nt!PspLocateSystemDll+0x83
80786be4 837ea14f 00000000 8080f888 8080a500 nt!PsLocateSystemDlls+0x55
80786c6c 837ee224 0080a500 85d02af8 85d02788 nt!IoInitSystem+0x607
80786d48 835c6440 80786d90 83642f5e 8080a500 nt!Phase1InitializationDiscard+0xced
80786d50 83642f5e 8080a500 ac3a7f54 00000000 nt!Phase1Initialization+0xd
80786d90 834ea219 835c6433 8080a500 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
STACK_COMMAND: kb
 
FOLLOWUP_IP: 
nt!ExRaiseHardError+151
8373e2b3 8bf0 mov esi,eax
 
SYMBOL_STACK_INDEX: 3
 
SYMBOL_NAME: nt!ExRaiseHardError+151
 
FOLLOWUP_NAME: MachineOwner
 
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09
 
FAILURE_BUCKET_ID: 0xc0000221_nt!ExRaiseHardError+151
 
BUCKET_ID: 0xc0000221_nt!ExRaiseHardError+151
 
Followup: MachineOwner
 
 
17/09/11 
 
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\091711-15288-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8280d000 PsLoadedModuleList = 0x82957850
Debug session time: Sat Sep 17 14:35:55.093 2011 (GMT+8)
System Uptime: 0 days 0:00:19.968
Loading Kernel Symbols
....................................................
Loading User Symbols
Loading unloaded module list
.
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
PROCESS1_INITIALIZATION_FAILED (6b)
Arguments:
Arg1: c0000428, Indicates the NT status code that caused the failure.
Arg2: 00000003, (reserved)
Arg3: 00000000
Arg4: 00000000
 
Debugging Details:
------------------
 
 
CUSTOMER_CRASH_COUNT: 1
 
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
 
BUGCHECK_STR: 0x6B
 
PROCESS_NAME: System
 
CURRENT_IRQL: 0
 
LAST_CONTROL_TRANSFER: from 82989038 to 828ebf20
 
STACK_TEXT: 
80786b5c 82989038 0000006b c0000428 00000003 nt!KeBugCheckEx+0x1e
80786bc0 82988f26 00000000 00000000 8080a4f0 nt!PspLocateSystemDll+0xdd
80786be4 82bbe14f 00000000 80817310 8080a4f0 nt!PsLocateSystemDlls+0x55
80786c6c 82bc2224 0080a4f0 85106b80 85106810 nt!IoInitSystem+0x607
80786d48 8299a440 80786d90 82a16f5e 8080a4f0 nt!Phase1InitializationDiscard+0xced
80786d50 82a16f5e 8080a4f0 acab3c0e 00000000 nt!Phase1Initialization+0xd
80786d90 828be219 8299a433 8080a4f0 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
STACK_COMMAND: kb
 
FOLLOWUP_IP: 
nt!PspLocateSystemDll+dd
82989038 cc int 3
 
SYMBOL_STACK_INDEX: 1
 
SYMBOL_NAME: nt!PspLocateSystemDll+dd
 
FOLLOWUP_NAME: MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME: ntkrpamp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09
 
FAILURE_BUCKET_ID: 0x6B_nt!PspLocateSystemDll+dd
 
BUCKET_ID: 0x6B_nt!PspLocateSystemDll+dd
 
Followup: MachineOwner
---------
 
 
22/09/11 
 
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
 
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x83441000 PsLoadedModuleList = 0x8358b850
Debug session time: Thu Sep 22 19:34:04.251 2011 (GMT+8)
System Uptime: 0 days 0:00:09.859
Loading Kernel Symbols
.....................................................
Loading User Symbols
 
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
Unknown bugcheck code (c0000221)
Unknown bugcheck description
Arguments:
Arg1: 8d0667b0
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
 
Debugging Details:
------------------
 
 
BUGCHECK_STR: 0xc0000221
 
ERROR_CODE: (NTSTATUS) 0xc0000221 - {Bad Image Checksum} The image %hs is possibly corrupt. The header checksum does not match the computed checksum.
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000221 - {Bad Image Checksum} The image %hs is possibly corrupt. The header checksum does not match the computed checksum.
 
EXCEPTION_PARAMETER1: 8d0667b0
 
EXCEPTION_PARAMETER2: 00000000
 
EXCEPTION_PARAMETER3: 00000000
 
EXCEPTION_PARAMETER4: 0
 
MODULE_NAME: nt
 
IMAGE_NAME: ntkrpamp.exe
 
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
 
PROCESS_NAME: System
 
CURRENT_IRQL: 0
 
LAST_CONTROL_TRANSFER: from 8376c92f to 8351ff20
 
STACK_TEXT: 
807866f4 8376c92f 0000004c c0000221 80786728 nt!KeBugCheckEx+0x1e
807868b0 8361ad2e c0000221 00000001 00000001 nt!ExpSystemErrorHandler+0x56c
80786a60 837462b3 c0000221 00000001 00000001 nt!ExpRaiseHardError+0xbf
80786ae8 8361a21d c0000221 00000001 00000001 nt!ExRaiseHardError+0x151
80786b58 835bcfde c0000221 00000001 00000001 nt!NtRaiseHardError+0x179
80786bc0 835bcf26 00000000 837acf3c 8080a500 nt!PspLocateSystemDll+0x83
80786be4 837f214f 00000000 8080f888 8080a500 nt!PsLocateSystemDlls+0x55
80786c6c 837f6224 0080a500 85d02af8 85d02788 nt!IoInitSystem+0x607
80786d48 835ce440 80786d90 8364af5e 8080a500 nt!Phase1InitializationDiscard+0xced
80786d50 8364af5e 8080a500 ac34f33b 00000000 nt!Phase1Initialization+0xd
80786d90 834f2219 835ce433 8080a500 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
STACK_COMMAND: kb
 
FOLLOWUP_IP: 
nt!ExRaiseHardError+151
837462b3 8bf0 mov esi,eax
 
SYMBOL_STACK_INDEX: 3
 
SYMBOL_NAME: nt!ExRaiseHardError+151
 
FOLLOWUP_NAME: MachineOwner
 
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09
 
FAILURE_BUCKET_ID: 0xc0000221_nt!ExRaiseHardError+151
 
BUCKET_ID: 0xc0000221_nt!ExRaiseHardError+151
 
Followup: MachineOwner
 
 
 
 
 
23/09/11 
 
(****1935 fail to boot
restarted to windows loading screen, then black screen instead of desktop, however cursor is present and responsive
 
Bluescreen was c0000221 Unknown hard error = ntdll.dll*******
 

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\092311-17628-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x83412000 PsLoadedModuleList = 0x8355c850
Debug session time: Fri Sep 23 19:06:16.468 2011 (GMT+8)
System Uptime: 0 days 0:00:11.701
Loading Kernel Symbols
.....................................................
Loading User Symbols
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
Unknown bugcheck code (c0000221)
Unknown bugcheck description
Arguments:
Arg1: 8d15a538
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
 
Debugging Details:
------------------
 
 
BUGCHECK_STR: 0xc0000221
 
ERROR_CODE: (NTSTATUS) 0xc0000221 - {Bad Image Checksum} The image %hs is possibly corrupt. The header checksum does not match the computed checksum.
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000221 - {Bad Image Checksum} The image %hs is possibly corrupt. The header checksum does not match the computed checksum.
 
EXCEPTION_PARAMETER1: 8d15a538
 
EXCEPTION_PARAMETER2: 00000000
 
EXCEPTION_PARAMETER3: 00000000
 
EXCEPTION_PARAMETER4: 0
 
MODULE_NAME: nt
 
IMAGE_NAME: ntkrpamp.exe
 
CUSTOMER_CRASH_COUNT: 1
 
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
 
PROCESS_NAME: System
 
CURRENT_IRQL: 0
 
LAST_CONTROL_TRANSFER: from 8373d92f to 834f0f20
 
STACK_TEXT: 
807866f4 8373d92f 0000004c c0000221 80786728 nt!KeBugCheckEx+0x1e
807868b0 835ebd2e c0000221 00000001 00000001 nt!ExpSystemErrorHandler+0x56c
80786a60 837172b3 c0000221 00000001 00000001 nt!ExpRaiseHardError+0xbf
80786ae8 835eb21d c0000221 00000001 00000001 nt!ExRaiseHardError+0x151
80786b58 8358dfde c0000221 00000001 00000001 nt!NtRaiseHardError+0x179
80786bc0 8358df26 00000000 8377df3c 8080a500 nt!PspLocateSystemDll+0x83
80786be4 837c314f 00000000 8080f888 8080a500 nt!PsLocateSystemDlls+0x55
80786c6c 837c7224 0080a500 85d02af8 85d02788 nt!IoInitSystem+0x607
80786d48 8359f440 80786d90 8361bf5e 8080a500 nt!Phase1InitializationDiscard+0xced
80786d50 8361bf5e 8080a500 ac31f37a 00000000 nt!Phase1Initialization+0xd
80786d90 834c3219 8359f433 8080a500 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
STACK_COMMAND: kb
 
FOLLOWUP_IP: 
nt!ExRaiseHardError+151
837172b3 8bf0 mov esi,eax
 
SYMBOL_STACK_INDEX: 3
 
SYMBOL_NAME: nt!ExRaiseHardError+151
 
FOLLOWUP_NAME: MachineOwner
 
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09
 
FAILURE_BUCKET_ID: 0xc0000221_nt!ExRaiseHardError+151
 
BUCKET_ID: 0xc0000221_nt!ExRaiseHardError+151
 
Followup: MachineOwner
---------

Like I said, I think its a driver fault. "VISTA_DRIVER_FAULT" is a good clue hehe.

Have you any suggestions how I can narrow this down? Want to get it sorted once and for all. Pretty sure windows is starting to get corrupted from it, so once we figure it out might try a reinstall over or clean install and sort the problem from scratch.

Any help you can offer will be appreciated!

Cheers.

My System SpecsSystem Spec
.

24 Sep 2011   #2

Win 7 32b Ultimate
 
 

Not one brave soul up for the challenge? Or are you all just not U2 fans?

I spent some time doing some research last night. I'm starting to think my problem is memory related, despite memtest not finding any errors.

I pulled out one of my mem dimms last night and got the details of it:
Apacer DDR3
2GB UNB PC3-12800 CL9
S/N 201002525328
P/N 78.AAGDA.9K1


I then looked at the asus website and checked my mobo specs:
ASUSTeK Computer Inc. - Motherboards- ASUS M4A89GTD PRO/USB3
4 x DIMM, Max. 16 GB, DDR3 2000(O.C.)/1333/1066 ECC,Non-ECC,Un-buffered Memory
Dual Channel memory architecture
*AMD AM3 100 and 200 series CPU support up to DDR3 1066MHz
**Due to OS limitation, when installing total memory of 4GB capacity or more, Windows® 32-bit operation system may only recognize less than 3GB. Hence, a total installed memory of less than 3GB is recommended.
***Refer to www.asus.com for the memory QVL (Qualified Vendors Lists).


The QVL lists only one Apacer type mem chip:
Apacer 78.A1GC6.9L1 2GB DS Apacer AM5D5808DEWSBG - very different to what I have.

I'm guessing my current chips aren't supported? Im also guessing 'PC3' is the type, '12800' is speed and 'CL9' is the port type?

Do you think this might be what is causing my errors?

This thread also seems to back up my suspicions:
http://www.sevenforums.com/crashes-d...uild-bsod.html

I have found some chips locally that are supported and will only cost me $40 AUS.

Kingston 2GB DD3 PC-10600 (1333MHz) Non-ECC CL9 DIMM (KVR1333D3N9/2G)

Thinking I might try these unless any of you have better suggestions?
My System SpecsSystem Spec
27 Sep 2011   #3

Win 7 32b Ultimate
 
 

Come on! Not one?

Latest crash info:


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


Loading Dump File [C:\Windows\Minidump\092711-19765-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x83437000 PsLoadedModuleList = 0x83581850
Debug session time: Tue Sep 27 19:03:42.792 2011 (GMT+8)
System Uptime: 0 days 0:00:52.400
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
....
3: kd>
3: kd>
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 8784ad40, Terminating object
Arg3: 8784aeac, Process image file name
Arg4: 83650cf0, Explanatory message (ascii)

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


PROCESS_OBJECT: 8784ad40

IMAGE_NAME: wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 00000000

PROCESS_NAME: wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000374 - A heap has been corrupted.

BUGCHECK_STR: 0xF4_C0000374

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
9017bc9c 83716067 000000f4 00000003 8784ad40 nt!KeBugCheckEx+0x1e
9017bcc0 83693c1e 83650cf0 8784aeac 8784afb0 nt!PspCatchCriticalBreak+0x71
9017bcf0 83693b61 8784ad40 87e03030 c0000374 nt!PspTerminateAllThreads+0x2d
9017bd24 834751ea ffffffff c0000374 0014eb7c nt!NtTerminateProcess+0x1a2
9017bd24 777070b4 ffffffff c0000374 0014eb7c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0014eb7c 00000000 00000000 00000000 00000000 0x777070b4


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xF4_C0000374_IMAGE_wininit.exe

BUCKET_ID: 0xF4_C0000374_IMAGE_wininit.exe

Followup: MachineOwner
---------
My System SpecsSystem Spec
.


16 Oct 2011   #4

Win 7 32b Ultimate
 
 

So in the end I bought the two Kingston memory chips and replaced the old ones.

Hey presto! No more problems. Booted at least a dozen times since and not a hiccup.

Disappointed with all the views and not one person replied, despite me trying my best to stick to forum guidelines.

Still, wanted to post this if someone else has similar problems. There is hope!
My System SpecsSystem Spec
Reply

 BSOD on Win 7 startup- trying to pinpoint cause




Thread Tools



Similar help and support threads for2: BSOD on Win 7 startup- trying to pinpoint cause
Thread Forum
BSOD Unable to pinpoint cause BSOD Help and Support
Solved Multiple BSoD strings - Unable to pinpoint BSOD Help and Support
BSOD can't pinpoint what is triggering it BSOD Help and Support
BSOD- Persistent for months, cannot pinpoint problem. Different codes BSOD Help and Support
Can't pinpoint these wipes Im getting Software
BSOD problems...can't pinpoint...help!? BSOD Help and Support
Various Random BSOD - Can't Pinpoint the exact error! BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 01:37 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33