BSOD BCC 1e

I am new to the forum but have been having this issue with the BSOD. I built my system 1.5 years ago and had been running XP Pro until Feb. I bought the builders vers. of 7 Pro and installed Feb. I was continually getting BSOD. Yesterday I re-installed it. I added Nvidia control panel and Windows live and an HD Via management tool.. Today I got BSOD again. Pertinent data:
Intel E 8400 3Ghz.
4 Gb Kingston HyperX Ram Each 1 Gb stick
500GB Hitachi HD
DVD writer
Thermaltake TR2 430W PSU
3-120MM Fans 1 100MM fan I think? 2 are intake 2 are outgo.

Info I got on error report
Bcc 1e
Locale 1033
OS vers. 6.1.7600
Product 256_1

Any help will be appreciated.

Hi,

I'm sorry for the delay
Here is what I suggest you to do, based on the DMP you uploaded, stop code 1E can be caused by:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

As you see, Device driver is the first thing that it indicate. Netio.sys was blamed in the DMP and it's probably not the cause. In order to investigate further, pleaes enable driver verifier:
Driver Verifier - Enable and Disable

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/Win7 Startup Repair feature).

Update this driver:

Code:

AsInsHelp64 AsInsHelp64.sys Fri Jan 04 12:36:10 2008 (477DC5CA)

It is Asus Ai Booster software ASUSTeK Computer Inc.-Support-

BUGCHECK SUMMARY:

Code:

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


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI01.261\080810-24429-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02813000 PsLoadedModuleList = 0xfffff800`02a50e50
Debug session time: Sun Aug  8 21:42:47.374 2010 (UTC + 7:00)
System Uptime: 0 days 17:52:26.508
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea )

Followup: MachineOwner
---------

Regard,

Tuan

Your attachment did not contain the .dmp files... please navigate to c:/windows/minidump and zip up the .dmp files and attach it to your next post..

You have dump files and both point to hardware or hardware related problems.

One of these dumps is a Driver Verifier enables dump and it blames a Windows system core driver which most probably not the cause. The other dump has an error code of 1E and blames NETIO.SYS which is another Windows system core driver. However, this may give us a clue.

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED


Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_minidumpfile.zip\080810-24429-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02813000 PsLoadedModuleList = 0xfffff800`02a50e50
Debug session time: Sun Aug  8 10:42:47.374 2010 (GMT-4)
System Uptime: 0 days 17:52:26.508
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea )

Followup: MachineOwner
---------

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+611a952f01a5d864
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c268 -- (.exr 0xfffff80000b9c268)
ExceptionAddress: fffff880015980f9 (NETIO!RtlGetNextExpiredTimerWheelEntry+0x00000000000000ea)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9c310 -- (.trap 0xfffff80000b9c310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004f0ce50 rbx=0000000000000000 rcx=fffffa8004f0ce50
rdx=3f800000178dfab0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880015980f9 rsp=fffff80000b9c4a8 rbp=00000000000001f4
 r8=0000000003d5d541  r9=fffffa8004f0b000 r10=fffff80002813000
r11=0000000000000097 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
NETIO!RtlGetNextExpiredTimerWheelEntry+0xea:
fffff880`015980f9 8b4210          mov     eax,dword ptr [rdx+10h] ds:a9b8:3f800000`178dfac0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000287cc2e to fffff80002884ed0

STACK_TEXT:  
fffff800`00b9b348 fffff800`0287cc2e : 00000000`00000000 00000000`00000000 fffff800`00b9bac0 fffff800`028b1e28 : nt!KeBugCheck
fffff800`00b9b350 fffff800`028aabed : fffff800`02a91c24 fffff800`029caa3c fffff800`02813000 fffff800`00b9c268 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b380 fffff800`028b2250 : fffff800`029d2b5c fffff800`00b9b3f8 fffff800`00b9c268 fffff800`02813000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b3b0 fffff800`028bf1b5 : fffff800`00b9c268 fffff800`00b9bac0 fffff800`00000000 fffff780`00000008 : nt!RtlDispatchException+0x410
fffff800`00b9ba90 fffff800`02884542 : fffff800`00b9c268 00000000`00000000 fffff800`00b9c310 00000000`000003e8 : nt!KiDispatchException+0x135
fffff800`00b9c130 fffff800`02882e4a : fffff800`00b9c3a0 fffff880`016572a0 fffff800`00b9c320 fffff800`02893494 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c310 fffff880`015980f9 : fffff880`02d300cc 00000000`03d5d98c 00000000`00000002 00000000`000003e8 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c4a8 fffff880`02d300cc : 00000000`03d5d98c 00000000`00000002 00000000`000003e8 fffff880`03a54698 : NETIO!RtlGetNextExpiredTimerWheelEntry+0xea
fffff800`00b9c4b0 fffff800`02890fa6 : fffff800`00b9c5f0 00000000`00000001 00000000`00000000 00000000`00000000 : afd!AfdTimerWheelHandler+0xbc
fffff800`00b9c530 fffff800`02890326 : fffffa80`04730768 fffffa80`04730768 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`02890e7e : 00000095`d181f9c8 fffff800`00b9cc18 00000000`003ef04d fffff800`02a00c28 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`02890697 : 0000002c`09ff53cc 0000002c`003ef04d 0000002c`09ff53a6 00000000`0000004d : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`0288d6fa : fffff800`029fde80 fffff800`02a0bc40 00000000`00000000 fffff880`03c02db0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!RtlGetNextExpiredTimerWheelEntry+ea
fffff880`015980f9 8b4210          mov     eax,dword ptr [rdx+10h]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  NETIO!RtlGetNextExpiredTimerWheelEntry+ea

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

FAILURE_BUCKET_ID:  X64_0x1E_NETIO!RtlGetNextExpiredTimerWheelEntry+ea

BUCKET_ID:  X64_0x1E_NETIO!RtlGetNextExpiredTimerWheelEntry+ea

Followup: MachineOwner
---------

To begin your troubleshooting, uninstall AVG using this tool >Info > Tool (32bit) - Tool (64 bit). If you have AVG Identity Protection installed, uninstall it also using this tool > Info > Tool. AVG has been know to cause crashes on some Win 7 systems. Replace it with Microsoft Security Essentials. What firewall are you using?

I find some out of date drivers on your system. Win 7 does not like older drivers and they can cause conflicts and crashes.

AsInsHelp64.sys Fri Jan 04 00:36:10 2008
AsIO.sys Mon Dec 17 04:11:49 2007
Rt64win7.sys Thu Feb 26 04:04:13 2009
viahduaa.sys Tue Jun 02 04:55:21 2009

Update these drivers, especially the ones in red font.

- 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

If you need help with locating or updating drivers, please post. Turn off Driver Verifier while you are updating.

Post back after you have done this and we will go from there.

Here is some help with the drivers.

AsInsHelp64.sys Fri Jan 04 00:36:10 2008 - I cannot find the program this driver is associated with nor can I find the manufaturer. It came from ASUSTeK COMPUTER INC. and is probably part of a utility program. See if you can find an update from the ASUS site. If there is no update, suggest you do a search for this file, find the location, and rename it from AsInsHelp64.sys to AsInsHelp64.bak. This way you can always rename it if you find it is essential.

AsIO.sys Mon Dec 17 04:11:49 2007 - belongs to the software AsIO or ASUS Probe V by ASUSTeK Computer Inc. This is very old software for Win 7. See if you can update it via the ASUS website or perhaps update ASUS Probe. It not, you can rename it by going to C:\Windows\System32\Drivers.

Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver, Realtek. Update this driver.

viahduaa.sys Tue Jun 02 04:55:21 2009 - VIA High Definition Audio Function Driver, VIA High Definition Audio Driver, VIA Technologies, Inc. VIA Technologies, Inc. Update this driver.