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: random BSOD brand new g73jw win 7 ultimate 64bit fresh install

23 Oct 2010   #11
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by homamkeh View Post
here it is
These were caused by memory corruption but

WERE NOT VERIFIER ENABLED.

I would run memtest

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.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.


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\bsod ver\Windows_NT6_BSOD_jcgriff2\102010-40529-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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`03095e50
Debug session time: Wed Oct 20 16:48:30.745 2010 (GMT-4)
System Uptime: 0 days 15:20:43.807
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 D1, {558, 2, 0, fffff88004201120}

*** 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
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000558, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004201120, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031000e0
 0000000000000558 

CURRENT_IRQL:  2

FAULTING_IP: 
netbt!RemoteHashTimeout+16a
fffff880`04201120 498b6d00        mov     rbp,qword ptr [r13]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c320 -- (.trap 0xfffff80000b9c320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000008493730
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004201120 rsp=fffff80000b9c4b0 rbp=0000000000000100
 r8=fffffa801092ad00  r9=0000000000000000 r10=fffffa800a247850
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
netbt!RemoteHashTimeout+0x16a:
fffff880`04201120 498b6d00        mov     rbp,qword ptr [r13] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec7ca9 to fffff80002ec8740

STACK_TEXT:  
fffff800`00b9c1d8 fffff800`02ec7ca9 : 00000000`0000000a 00000000`00000558 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c1e0 fffff800`02ec6920 : 00000000`00000700 00000000`000003e8 fffff800`00b9c398 00000000`ffffffff : nt!KiBugCheckDispatch+0x69
fffff800`00b9c320 fffff880`04201120 : fffffa80`07f0a000 fffff880`04b33a24 fffffa80`10926c68 fffffa80`10926b10 : nt!KiPageFault+0x260
fffff800`00b9c4b0 fffff880`042011f7 : fffffa80`1092adf0 fffff800`00b9c600 fffffa80`1092adf0 fffffa80`1092ad02 : netbt!RemoteHashTimeout+0x16a
fffff800`00b9c540 fffff800`02ed429e : fffff800`00b9c618 00000000`00000000 00000000`40ff0088 00000000`00000000 : netbt!TimerExpiry+0x5b
fffff800`00b9c570 fffff800`02ed3dd6 : fffffa80`1092aeb0 00000000`003608ff 00000000`00000000 00000000`00000001 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ed44be : 00000080`9fe0101c fffff800`00b9cc58 00000000`003608ff fffff800`03047268 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ed3cb7 : 00000015`b7dffac2 00000015`003608ff 00000015`b7dffa08 00000000`000000ff : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02ed0eea : fffff800`03042e80 fffff800`03050c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !netbt
3 errors : !netbt (fffff880042010f9-fffff88004201cf1)
fffff880042010f0  02  00  8b  93  b0  01  00  00  8b *1d  7a  d1  02  00  88  44 ..........z....D
...
fffff88004201be0  83 *eb  20  48  89  41  18  4c  89  51  10  48  8b  44  0a  08 .. H.A.L.Q.H.D..
...
fffff88004201cf0  f6 *51  80  7d  0f  1c  b8  01  00  00  c0  48  89  b4  24  b0 .Q.}.......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
---------
Old drivers

Code:
ISODrv64.sys        fffff880`01bcb000    fffff880`01be7000    0x0001c000    0x472be92e    11/2/2007 23:21:18                        
sncduvc.SYS        fffff880`07611000    fffff880`07619a80    0x00008a80    0x495894f2    12/29/2008 05:14:26                        
spldr.sys        fffff880`01610000    fffff880`01618000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
ATK64AMD.sys        fffff880`05bc6000    fffff880`05bce000    0x00008000    0x4a0a1cb6    5/12/2009 21:04:54                        
GEARAspiWDM.sys        fffff880`05b9e000    fffff880`05bab000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`01260000    fffff880`0126b000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
ASMMAP64.sys        fffff880`04885000    fffff880`0488d000    0x00008000    0x4a4c7a36    7/2/2009 05:13:26
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


My System SpecsSystem Spec
.
23 Oct 2010   #12
homamkeh

windows 7
 
 

i just got this laptop. is it for sure bad memory? I will run memtest and post back.

i ran it while verifier was on. it is still on right now. am i doing something wrong? should i do it again?

i just got this laptop, should i just return it and repurchase? i am worried as i bought it in the states and i am now in canada. I know the warranty covers it but i do not know if i can rma it to the straight to the retailer.

regards
My System SpecsSystem Spec
23 Oct 2010   #13
homamkeh

windows 7
 
 

i just ran the memtest. passed with no errors. what should i do next?

thanks for replying, i really appreciate it
My System SpecsSystem Spec
.

23 Oct 2010   #14
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Make sure you have turned Driver Verifier off and update the drivers ZigZag listed. Out of date drivers can and do cause memory corruption and BSOD's.
My System SpecsSystem Spec
24 Oct 2010   #15
homamkeh

windows 7
 
 

Quote   Quote: Originally Posted by CarlTR6 View Post
Make sure you have turned Driver Verifier off and update the drivers ZigZag listed. Out of date drivers can and do cause memory corruption and BSOD's.
Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by homamkeh View Post
here it is
These were caused by memory corruption but

WERE NOT VERIFIER ENABLED.

I would run memtest

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.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.


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\bsod ver\Windows_NT6_BSOD_jcgriff2\102010-40529-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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`03095e50
Debug session time: Wed Oct 20 16:48:30.745 2010 (GMT-4)
System Uptime: 0 days 15:20:43.807
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 D1, {558, 2, 0, fffff88004201120}

*** 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
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000558, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004201120, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031000e0
 0000000000000558 

CURRENT_IRQL:  2

FAULTING_IP: 
netbt!RemoteHashTimeout+16a
fffff880`04201120 498b6d00        mov     rbp,qword ptr [r13]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c320 -- (.trap 0xfffff80000b9c320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000008493730
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004201120 rsp=fffff80000b9c4b0 rbp=0000000000000100
 r8=fffffa801092ad00  r9=0000000000000000 r10=fffffa800a247850
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
netbt!RemoteHashTimeout+0x16a:
fffff880`04201120 498b6d00        mov     rbp,qword ptr [r13] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec7ca9 to fffff80002ec8740

STACK_TEXT:  
fffff800`00b9c1d8 fffff800`02ec7ca9 : 00000000`0000000a 00000000`00000558 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c1e0 fffff800`02ec6920 : 00000000`00000700 00000000`000003e8 fffff800`00b9c398 00000000`ffffffff : nt!KiBugCheckDispatch+0x69
fffff800`00b9c320 fffff880`04201120 : fffffa80`07f0a000 fffff880`04b33a24 fffffa80`10926c68 fffffa80`10926b10 : nt!KiPageFault+0x260
fffff800`00b9c4b0 fffff880`042011f7 : fffffa80`1092adf0 fffff800`00b9c600 fffffa80`1092adf0 fffffa80`1092ad02 : netbt!RemoteHashTimeout+0x16a
fffff800`00b9c540 fffff800`02ed429e : fffff800`00b9c618 00000000`00000000 00000000`40ff0088 00000000`00000000 : netbt!TimerExpiry+0x5b
fffff800`00b9c570 fffff800`02ed3dd6 : fffffa80`1092aeb0 00000000`003608ff 00000000`00000000 00000000`00000001 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ed44be : 00000080`9fe0101c fffff800`00b9cc58 00000000`003608ff fffff800`03047268 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ed3cb7 : 00000015`b7dffac2 00000015`003608ff 00000015`b7dffa08 00000000`000000ff : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02ed0eea : fffff800`03042e80 fffff800`03050c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !netbt
3 errors : !netbt (fffff880042010f9-fffff88004201cf1)
fffff880042010f0  02  00  8b  93  b0  01  00  00  8b *1d  7a  d1  02  00  88  44 ..........z....D
...
fffff88004201be0  83 *eb  20  48  89  41  18  4c  89  51  10  48  8b  44  0a  08 .. H.A.L.Q.H.D..
...
fffff88004201cf0  f6 *51  80  7d  0f  1c  b8  01  00  00  c0  48  89  b4  24  b0 .Q.}.......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
---------
Old drivers

Code:
ISODrv64.sys        fffff880`01bcb000    fffff880`01be7000    0x0001c000    0x472be92e    11/2/2007 23:21:18                        
sncduvc.SYS        fffff880`07611000    fffff880`07619a80    0x00008a80    0x495894f2    12/29/2008 05:14:26                        
spldr.sys        fffff880`01610000    fffff880`01618000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
ATK64AMD.sys        fffff880`05bc6000    fffff880`05bce000    0x00008000    0x4a0a1cb6    5/12/2009 21:04:54                        
GEARAspiWDM.sys        fffff880`05b9e000    fffff880`05bab000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`01260000    fffff880`0126b000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
ASMMAP64.sys        fffff880`04885000    fffff880`0488d000    0x00008000    0x4a4c7a36    7/2/2009 05:13:26
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
ISODrv64.sys
uninstalled, will upgrade ultra iso



0x472be92e
could not find



sncduvc.SYS
this is the webcam driver, i checked device manager, it says its from 2010. why does it say it i old?



0x495894f2 12/29/2008 05:14:26
could not find





spldr.sys

this has sth to do with microsoft security? at least that is what i found and no clue how to update it.



0x4a0858bb 5/11/2009 12:56:27
could not find



ATK64AMD.sys

mine says 2009, will update from asus website anyway
. UPDATE: i downloaded the latest one. it is the same as what i have

0x4a0a1cb6 5/12/2009 21:04:54

could not find



GEARAspiWDM.sys
sth to do with itunes? i have the latest version though


0x4a1151c0
5/18/2009 08:17:04
could not find






amdxata.sys
Storage Filter Driver from AMD? dont know how to find the latest versoin


0x4a12f2eb 5/19/2009 13:56:59
could not find




ASMMAP64.sys
memory mapping driver from asus could not find


colors: think i found/solved or know how to solve the problem
could not find and need help
could not find and need help but i think i am on the right track

many thanks for all those who are trying to help. it is much appreciated
My System SpecsSystem Spec
24 Oct 2010   #16
usasma
Microsoft MVP

 
 

The 0x4........ things are just memory address' and aren't updateable. (0x4a12f2eb)

The webcam uses several drivers and the one that was involved in the crash is the outdated one (sncduvc.SYS)
Not normally an issue - but you should rename the sncduvc.sys file to sncduvc.BAK (it's in the C:\Windows\System32\drivers folder). That will disable the webcam - but don't worry about it, you can rename it back (to .sys) when we're done)

spldr.sys is a Microsoft driver. As such the only way to update it is through Windows Update. If it doesn't update, then there's no newer version for your system (the version on my 64 bit Win7 system is from 19 Jul 2009)

ATK64AMD.sys - if you have the most recent one from the Asus website it's probably not necessary to update it. BUT, I recommend doing it anyway (in case the current version has an undetected corruption). The "best" way is to uninstall the old version before installing the new version (it gives the greatest chance of replacing all files).

GEARAspiWDM.sys is a CD filter driver that's licensed to many different programs. To figure out which one, rename the file to GEARAspiWDM.BAK and then see which CD/DVD program no longer works properly. FYI - I've never done this myself, so I can't tell you how long or which function of the program won't work. I'd just rename it and leave it at that until we're done troubleshooting.

amdxata.sys is an AMD Storage driver. BUT - your system has an Intel chipset (with Intel storage drivers) and an nVidia video card....very strange! I, personally, would rename the driver to .BAK to see what it does - BUT I am able to get into the hard drive to rename the file to .SYS if the system fails to boot. Can you do this? If not, then don't rename the file!!!

Quote:
EDIT: Asus, it seems, has done the same thing as HP. It loads drivers for the different chipsets/processor that the drive image might encounter (look for AMD and Intel in the MSINFO32 report....Software Environment...System Drivers) While this is more efficient for Asus, it loads extra stuff on boot that may not be needed. And in order to get rid of it, you're forced to experiment with stopping services and removing drivers that might render your system unbootable.
ASMMAP64.sys is in the ATKGFNEX package in the same download as the ATK64AMD.sys was. It's in the ATK category of the download page (ATKACPI driver and hotkey-related utilities). This driver is the same date as the one on your system - but as I discussed earlier, it's a good idea to replace it just in case there's an issue with it.
My System SpecsSystem Spec
24 Oct 2010   #17
usasma
Microsoft MVP

 
 

Once they're all updated, then try the Driver Verifier again.
We'll need the memory dump if the system saves it. If not, then we'll have to make do with the following info:

Make sure that the system stops on the BSOD (so you can copy the needed info down).
Here's an image with the info that we need (the stuff in RED):
My System SpecsSystem Spec
24 Oct 2010   #18
homamkeh

windows 7
 
 

Quote   Quote: Originally Posted by usasma View Post
The 0x4........ things are just memory address' and aren't updateable. (0x4a12f2eb)

The webcam uses several drivers and the one that was involved in the crash is the outdated one (sncduvc.SYS)
Not normally an issue - but you should rename the sncduvc.sys file to sncduvc.BAK (it's in the C:\Windows\System32\drivers folder). That will disable the webcam - but don't worry about it, you can rename it back (to .sys) when we're done)

spldr.sys is a Microsoft driver. As such the only way to update it is through Windows Update. If it doesn't update, then there's no newer version for your system (the version on my 64 bit Win7 system is from 19 Jul 2009)

ATK64AMD.sys - if you have the most recent one from the Asus website it's probably not necessary to update it. BUT, I recommend doing it anyway (in case the current version has an undetected corruption). The "best" way is to uninstall the old version before installing the new version (it gives the greatest chance of replacing all files).

GEARAspiWDM.sys is a CD filter driver that's licensed to many different programs. To figure out which one, rename the file to GEARAspiWDM.BAK and then see which CD/DVD program no longer works properly. FYI - I've never done this myself, so I can't tell you how long or which function of the program won't work. I'd just rename it and leave it at that until we're done troubleshooting.

amdxata.sys is an AMD Storage driver. BUT - your system has an Intel chipset (with Intel storage drivers) and an nVidia video card....very strange! I, personally, would rename the driver to .BAK to see what it does - BUT I am able to get into the hard drive to rename the file to .SYS if the system fails to boot. Can you do this? If not, then don't rename the file!!!

Quote:
EDIT: Asus, it seems, has done the same thing as HP. It loads drivers for the different chipsets/processor that the drive image might encounter (look for AMD and Intel in the MSINFO32 report....Software Environment...System Drivers) While this is more efficient for Asus, it loads extra stuff on boot that may not be needed. And in order to get rid of it, you're forced to experiment with stopping services and removing drivers that might render your system unbootable.
ASMMAP64.sys is in the ATKGFNEX package in the same download as the ATK64AMD.sys was. It's in the ATK category of the download page (ATKACPI driver and hotkey-related utilities). This driver is the same date as the one on your system - but as I discussed earlier, it's a good idea to replace it just in case there's an issue with it.
what about the sound card "ksaud.sys" bsod? my system will not boot with verifier on while the sound card is plugged in, i get a BSOD screen on start up.

i will follow these steps and report back.

many thanks
My System SpecsSystem Spec
24 Oct 2010   #19
usasma
Microsoft MVP

 
 

If the system won't boot without a BSOD when the sound card is plugged in (and verifier is turned on), then it's likely that there's a problem with your sound card drivers or the sound card itself.

To test, turn off Driver Verifier by booting with the sound card out. Then select "Delete existing settings" from the first screen in Driver Verifier. Shut the system down.
Reinstall the sound card, then boot the system up.
Uninstall the sound card software and drivers.
Download and install a fresh copy of the 64 bit Win7 drivers for your sound card (don't use Vista drivers).
Turn Driver Verifier on according to the previous instructions (it tests 3rd party drivers - such as the ksaud.sys driver).

See if it BSOD's again.
If so, the card is probably bad.
If not, then you've probably fixed it
Don't forget to turn Driver Verifier off by selecting "Delete existing settings" in the first screen.
My System SpecsSystem Spec
28 Oct 2010   #20
homamkeh

windows 7
 
 

I havnt had any BSOD in a few days. I have updated my chipset and wireless. reinstalled my sound card. weird thing is, after a restart, the audio icon (w7 native audio icom) sometimes does not show. same thing with the network manager icon. when i go to notification area icons and customize the icons, both are set to "show icon and notifications" when i switch them to sth else then back to "show icon and notifications" it says it is not active and will show the icon once it is. why is this happening? my network is online and i have internet. Sound is also working. the icons are not showing.

when i run driver verifier however, i still get BSOD on startup. Im sure it is the sound card. if i unplug it it does not BSOD on start up. i decided to keep it since the random BSOD stopped. will update if anything changes. will try and reinstall the driver again if that happens.

Many thanks for all your help. It is really appreciated.

regards
My System SpecsSystem Spec
Reply

 random BSOD brand new g73jw win 7 ultimate 64bit fresh install




Thread Tools




Similar help and support threads
Thread Forum
BSOD Fresh Win7 Install - Brand new laptop - No AV installed
So I have a Dell XPS 17 laptop that is pretty much brand new (bought in June, pulled out of the box in September). First thing I did was download Windows 7 torrent. Wipe the drives and install it with the intentions of activating it using my OEM key. Everything installed fine all hardware was...
BSOD Help and Support
Random App Crashes on new Install of Windows 7 Ultimate 64Bit
Problems started happening last night just after I installed the new CS:GO Beta, which I think is unrelated. Anyway I opened up chrome, but wasn't able to open it up. It just wouldn't load whenever I tried to open it. I uninstalled and reinstalled and was fine. Then it happened when I tried to...
Software
Windows 7 64bit Asus G73jw Bsod
Hi there , Thanks for your help & time i have bsod , header say "SYSTEM SERVICE EXCEPTION" When its happened ? : when i try to turn on PowerGear turbo button . the bsod happened after couple of a seconds . or when try to overlock using setfsb . my dump files attached another note...
BSOD Help and Support
Windows Ultimate 64bit fresh install wont boot
I cant figure this one out and wont stop till i do. I create a desktop from various used and new piece all working and good. I have a asus p5q motherboard with intel 2.66ghz 775chipset and pny 1 gb crap ram. i update the bios to latest version and i believe everythings running good on that end....
BSOD Help and Support
Random BSOD - Fresh install, fresh system
Hi. I have installed a whole new windows 7 pro x64. My new mobo an ASus p5e3 pro along with new ram pc12800 gskill 2x2 ddr3 (running in 1066mhz due to my q6600) Everythingi s running perfectly...except some random BSOD. 4 total this week. I have posted a pack of dump file in here, the last 4...
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 10:46.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App