BSOD Error

BipolarAvatar

New member
Local time
1:16 AM
Messages
5
- x64 bit windows 7 Ultimate os
- the original installed OS on the system? yes
- an OEM or full retail version? full retail
- What is the age of system (hardware)? ~1year 3 months
- What is the age of OS installation ~6months

just not sure why I'm getting this, i think it has happened twice now. usually when I'm sleeping, i wake up with my PC restarted
 

My Computer

Computer Manufacturer/Model Number
Custom
OS
Windows 7 Ultimate x64
CPU
AMD Phenom(tm) II x4 965 Processor 3.41 GHz
Motherboard
Asus M4A78T-E
Memory
4gb cruical Ballistix tracer DDR3
Graphics Card(s)
EVGA - Nividia GTX460
Sound Card
motherboard
Monitor(s) Displays
asus 23in and asus 24in lcd displays
Hard Drives
2x WD 1TB caviar green
PSU
700 watt
Case
Antex 900
Cooling
air
- x64 bit windows 7 Ultimate os
- the original installed OS on the system? yes
- an OEM or full retail version? full retail
- What is the age of system (hardware)? ~1year 3 months
- What is the age of OS installation ~6months

just not sure why I'm getting this, i think it has happened twice now. usually when I'm sleeping, i wake up with my PC restarted


These (after the update to sp-1) were caused by hardware. I also notice some really old drivers that need updating.

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\Windows_NT6_BSOD_jcgriff2\041611-31137-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0305d000 PsLoadedModuleList = 0xfffff800`032a2e90
Debug session time: Sat Apr 16 12:54:37.307 2011 (GMT-4)
System Uptime: 1 days 8:30:07.899
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa801976abea, 2, 1, fffff880015198c3}

Probably caused by : hardware ( NETIO!RtlReturnTimerWheelEntry+3 )

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

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: fffffa801976abea, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880015198c3, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330e0e8
 fffffa801976abea 

CURRENT_IRQL:  2

FAULTING_IP: 
NETIO!RtlReturnTimerWheelEntry+3
fffff880`015198c3 28837a10000f    sub     byte ptr [rbx+0F00107Ah],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Game.exe

TRAP_FRAME:  fffff80000ba2430 -- (.trap 0xfffff80000ba2430)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000073400001 rbx=0000000000000000 rcx=fffffa8007905000
rdx=fffffa800a769e58 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880015198c3 rsp=fffff80000ba25c8 rbp=0000000000000000
 r8=fffff80000ba2600  r9=0000000000000000 r10=0000000000b29b36
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
NETIO!RtlReturnTimerWheelEntry+0x3:
fffff880`015198c3 28837a10000f    sub     byte ptr [rbx+0F00107Ah],al ds:2830:00000000`0f00107a=??
Resetting default scope

MISALIGNED_IP: 
NETIO!RtlReturnTimerWheelEntry+3
fffff880`015198c3 28837a10000f    sub     byte ptr [rbx+0F00107Ah],al

LAST_CONTROL_TRANSFER:  from fffff800030dcbe9 to fffff800030dd640

STACK_TEXT:  
fffff800`00ba22e8 fffff800`030dcbe9 : 00000000`0000000a fffffa80`1976abea 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba22f0 fffff800`030db860 : fffffa80`0b6d09e0 fffffa80`0000003a 00000000`00000000 fffffa80`0a769b70 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2430 fffff880`015198c3 : fffff880`0176cef9 fffffa80`0a769b70 fffffa80`06b11a70 fffffa80`06b00b50 : nt!KiPageFault+0x260
fffff800`00ba25c8 fffff880`0176cef9 : fffffa80`0a769b70 fffffa80`06b11a70 fffffa80`06b00b50 00000000`00b28978 : NETIO!RtlReturnTimerWheelEntry+0x3
fffff800`00ba25d0 fffff880`0176d327 : 00000000`00000004 00000000`00000000 00000000`00000000 00000000`00000001 : tcpip!TcpProcessExpiredTcbTimers+0x1b9
fffff800`00ba26a0 fffff800`030e9062 : fffff800`0324fe80 00000000`00000000 fffff800`00ba2830 00000000`00000001 : tcpip!TcpPeriodicTimeoutHandler+0x297
fffff800`00ba27a0 fffff800`030e8f06 : fffffa80`06b1eb30 00000000`007272aa 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00ba2810 fffff800`030e8dee : 00000110`6e249903 fffff800`00ba2e88 00000000`007272aa fffff800`032537c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`030e8bd7 : fffffa80`08856cc1 fffffa80`007272aa 00000000`00000000 00000000`000000aa : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`030e0165 : 00000000`00000000 fffffa80`09b72a00 00000000`00000000 fffff880`01423a00 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`030dff7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`06c54be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!RtlReturnTimerWheelEntry+3
fffff880`015198c3 28837a10000f    sub     byte ptr [rbx+0F00107Ah],al

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETIO!RtlReturnTimerWheelEntry+3

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_NETIO.SYS

BUCKET_ID:  X64_IP_MISALIGNED_NETIO.SYS

Followup: MachineOwner
---------
Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html


Drivers
Code:
fcdabus.sys    9/5/2006 02:44:40 AM    fffff880`04a5a000    fffff880`04a63000    0x00009000    0x44fd1cd8                            
pcouffin.sys    12/5/2006 10:39:30 AM    fffff880`0481a000    fffff880`0482e380    0x00014380    0x457584a2                            
fsRamDsk.sys    3/30/2007 05:12:27 AM    fffff880`0163a000    fffff880`01645680    0x0000b680    0x460cd47b                            
fvxscsi.sys    7/17/2007 08:48:51 AM    fffff880`00c47000    fffff880`00c5f000    0x00018000    0x469cbab3                            
AsIO.sys    12/17/2007 05:11:49 AM    fffff880`04050000    fffff880`04057000    0x00007000    0x47663d55                            
AtiPcie.sys    5/5/2009 11:00:22 AM    fffff880`016a0000    fffff880`016a8000    0x00008000    0x4a005486                            
viahduaa.sys    5/7/2009 11:24:59 PM    fffff880`0566b000    fffff880`057f6000    0x0018b000    0x4a03a60b                            
spldr.sys    5/11/2009 12:56:27 PM    fffff880`0198b000    fffff880`01993000    0x00008000    0x4a0858bb
How To Find Drivers:
- 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 Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
 

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
Back
Top