BSOD with idle computer

andexls

andexls

New member
I have Windows 7 for 2 months now, and today was the first time that a BSOD showed up. It happened 3 times with a 2 or 3 hours interval.

I have an updated version of Windows 7 Ultimate 64-bits. All the drivers are updated also. My computer is a Core 2 Duo E7500 @2.93GHz, 2GB DDR2 RAM, Geforce 9800GT, 500GB HD.

All the three BSOD crashes happened when the computer was idle: only uTorrent and NOD32 4.0 were running. The screen appears for 1 second, then the computer restarts, and Windows shows a pop-up box saying that the system has just had an unexpected restart, or something like that.

There were 3 dump files in C:\Winodws\Minidump. They are all zipped and attached to this thread. Can someone help-me to find out what is the problem?

Thanks in advance!
 

My Computer

OS
Windows 7
CPU
Core 2 Duo E7500 2993MHz
Motherboard
Asus P5KPL-AM/BR
Memory
2GB DDR2 800MHz
Graphics Card(s)
Geforce 9800GT
Sound Card
VIA VT1708B CE Integrated
Monitor(s) Displays
SyncMaster 592v 15"
Hard Drives
500GB SATA
PSU
Generic
Case
Generic
Cooling
Generic
andexls said:
I have Windows 7 for 2 months now, and today was the first time that a BSOD showed up. It happened 3 times with a 2 or 3 hours interval.

I have an updated version of Windows 7 Ultimate 64-bits. All the drivers are updated also. My computer is a Core 2 Duo E7500 @2.93GHz, 2GB DDR2 RAM, Geforce 9800GT, 500GB HD.

All the three BSOD crashes happened when the computer was idle: only uTorrent and NOD32 4.0 were running. The screen appears for 1 second, then the computer restarts, and Windows shows a pop-up box saying that the system has just had an unexpected restart, or something like that.

There were 3 dump files in C:\Winodws\Minidump. They are all zipped and attached to this thread. Can someone help-me to find out what is the problem?

Thanks in advance!
Click to expand...



What virus protection do you have and have you done a 100% complete scan with updated definitions?

Do you have and Malware program. Malewarebytes.com has a great free one.

Lets start here first then I will ask you what hardware or Software/updates have you installed prior to this happening. MS did have some updates on the 15th that opened the door to some trojans or viruses.

Let us know about your scans.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Built
OS
Windows 10 Pro
CPU
Intel i5
Motherboard
I have a fatherboard
Memory
I'm old and lost a few chips
Graphics Card(s)
Yup
Sound Card
Yup
Monitor(s) Displays
Samsung 32" UHD
Screen Resolution
3840 x 2160
Hard Drives
Samsung 860 EVO drives
PSU
450 Watt and some fans that blow
Case
Small tower
Cooling
Yes I am cool. lol
Keyboard
Who needs a keyboard?
Mouse
Logitech Laser G7 wireless
Internet Speed
Zippy fast UP and DOWN
Antivirus
I got a shot
Browser
The new Improved EDGE 2020
IggyAZ said:
andexls said:
I have Windows 7 for 2 months now, and today was the first time that a BSOD showed up. It happened 3 times with a 2 or 3 hours interval.

I have an updated version of Windows 7 Ultimate 64-bits. All the drivers are updated also. My computer is a Core 2 Duo E7500 @2.93GHz, 2GB DDR2 RAM, Geforce 9800GT, 500GB HD.

All the three BSOD crashes happened when the computer was idle: only uTorrent and NOD32 4.0 were running. The screen appears for 1 second, then the computer restarts, and Windows shows a pop-up box saying that the system has just had an unexpected restart, or something like that.

There were 3 dump files in C:\Winodws\Minidump. They are all zipped and attached to this thread. Can someone help-me to find out what is the problem?

Thanks in advance!
Click to expand...



What virus protection do you have and have you done a 100% complete scan with updated definitions?

Do you have and Malware program. Malewarebytes.com has a great free one.

Lets start here first then I will ask you what hardware or Software/updates have you installed prior to this happening. MS did have some updates on the 15th that opened the door to some trojans or viruses.

Let us know about your scans.
Click to expand...

Ok, I just made a full scan with NOD32 4.0 updated, and no virus found. NOD32 is also an antispyware. By the way, I always leave the resident protection turned on in NOD32 and Windows Defender, and I update daily... so I don't think it's a virus or spyware issue.
 

My Computer

OS
Windows 7
CPU
Core 2 Duo E7500 2993MHz
Motherboard
Asus P5KPL-AM/BR
Memory
2GB DDR2 800MHz
Graphics Card(s)
Geforce 9800GT
Sound Card
VIA VT1708B CE Integrated
Monitor(s) Displays
SyncMaster 592v 15"
Hard Drives
500GB SATA
PSU
Generic
Case
Generic
Cooling
Generic
Could someone that is good in reading minidumps take a look.
I'm not an expert yet in reading them.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Built
OS
Windows 10 Pro
CPU
Intel i5
Motherboard
I have a fatherboard
Memory
I'm old and lost a few chips
Graphics Card(s)
Yup
Sound Card
Yup
Monitor(s) Displays
Samsung 32" UHD
Screen Resolution
3840 x 2160
Hard Drives
Samsung 860 EVO drives
PSU
450 Watt and some fans that blow
Case
Small tower
Cooling
Yes I am cool. lol
Keyboard
Who needs a keyboard?
Mouse
Logitech Laser G7 wireless
Internet Speed
Zippy fast UP and DOWN
Antivirus
I got a shot
Browser
The new Improved EDGE 2020
andexls said:
I have Windows 7 for 2 months now, and today was the first time that a BSOD showed up. It happened 3 times with a 2 or 3 hours interval.

I have an updated version of Windows 7 Ultimate 64-bits. All the drivers are updated also. My computer is a Core 2 Duo E7500 @2.93GHz, 2GB DDR2 RAM, Geforce 9800GT, 500GB HD.

All the three BSOD crashes happened when the computer was idle: only uTorrent and NOD32 4.0 were running. The screen appears for 1 second, then the computer restarts, and Windows shows a pop-up box saying that the system has just had an unexpected restart, or something like that.

There were 3 dump files in C:\Winodws\Minidump. They are all zipped and attached to this thread. Can someone help-me to find out what is the problem?

Thanks in advance!
Click to expand...


Hi Andexls

These crashes were caused by rt64win7.sys which as part of your reltek networking driver.

I would download and install a fresh copy of it.

I would also run a system file check
type cmd in search>right click and run as admin>SFC /SCANNOW

Good Luck

Ken







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\New folder\021910-21824-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\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`02a1c000 PsLoadedModuleList = 0xfffff800`02c59e50
Debug session time: Fri Feb 19 15:09:39.113 2010 (GMT-5)
System Uptime: 0 days 3:28:05.830
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {100002c, 2, 0, fffff80002ffd5d0}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+f102 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000100002c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ffd5d0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc40e0
 000000000100002c 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalBuildScatterGatherList+1a4
fffff800`02ffd5d0 448b5f2c        mov     r11d,dword ptr [rdi+2Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880037b4710 -- (.trap 0xfffff880037b4710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000007f7a62d0 rbx=0000000000000000 rcx=000000007f68e540
rdx=fffffa8003258ae0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ffd5d0 rsp=fffff880037b48a0 rbp=fffffa8003258aa0
 r8=0000000000000000  r9=fffffa800208e530 r10=fffffa8003258aa0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
hal!HalBuildScatterGatherList+0x1a4:
fffff800`02ffd5d0 448b5f2c        mov     r11d,dword ptr [rdi+2Ch] ds:0003:00000000`0000002c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a8d469 to fffff80002a8df00

STACK_TEXT:  
fffff880`037b45c8 fffff800`02a8d469 : 00000000`0000000a 00000000`0100002c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`037b45d0 fffff800`02a8c0e0 : 00000000`00000007 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`037b4710 fffff800`02ffd5d0 : 00000000`00000014 fffffa80`03531080 00000000`00000000 00000000`00000008 : nt!KiPageFault+0x260
fffff880`037b48a0 fffff880`0145c831 : fffffa80`021a6160 fffffa80`0322f0a0 00000000`00008e1e 00000008`00000000 : hal!HalBuildScatterGatherList+0x1a4
fffff880`037b4910 fffff880`0fdd4102 : fffffa80`02f051a0 fffffa80`03226000 fffffa80`0322f0a0 fffffa80`0322f0a0 : ndis!NdisMAllocateNetBufferSGList+0x181
fffff880`037b49b0 fffffa80`02f051a0 : fffffa80`03226000 fffffa80`0322f0a0 fffffa80`0322f0a0 fffffa80`03258aa0 : Rt64win7+0xf102
fffff880`037b49b8 fffffa80`03226000 : fffffa80`0322f0a0 fffffa80`0322f0a0 fffffa80`03258aa0 00000000`00000190 : 0xfffffa80`02f051a0
fffff880`037b49c0 fffffa80`0322f0a0 : fffffa80`0322f0a0 fffffa80`03258aa0 00000000`00000190 00000103`00000000 : 0xfffffa80`03226000
fffff880`037b49c8 fffffa80`0322f0a0 : fffffa80`03258aa0 00000000`00000190 00000103`00000000 00000000`00000000 : 0xfffffa80`0322f0a0
fffff880`037b49d0 fffffa80`03258aa0 : 00000000`00000190 00000103`00000000 00000000`00000000 0000a000`00000000 : 0xfffffa80`0322f0a0
fffff880`037b49d8 00000000`00000190 : 00000103`00000000 00000000`00000000 0000a000`00000000 00000014`00000000 : 0xfffffa80`03258aa0
fffff880`037b49e0 00000103`00000000 : 00000000`00000000 0000a000`00000000 00000014`00000000 00000000`00000001 : 0x190
fffff880`037b49e8 00000000`00000000 : 0000a000`00000000 00000014`00000000 00000000`00000001 00000000`00000004 : 0x103`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+f102
fffff880`0fdd4102 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  Rt64win7+f102

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49a65b0d

FAILURE_BUCKET_ID:  X64_0xA_Rt64win7+f102

BUCKET_ID:  X64_0xA_Rt64win7+f102

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

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
Thank you zigzag3143 for stepping in.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Built
OS
Windows 10 Pro
CPU
Intel i5
Motherboard
I have a fatherboard
Memory
I'm old and lost a few chips
Graphics Card(s)
Yup
Sound Card
Yup
Monitor(s) Displays
Samsung 32" UHD
Screen Resolution
3840 x 2160
Hard Drives
Samsung 860 EVO drives
PSU
450 Watt and some fans that blow
Case
Small tower
Cooling
Yes I am cool. lol
Keyboard
Who needs a keyboard?
Mouse
Logitech Laser G7 wireless
Internet Speed
Zippy fast UP and DOWN
Antivirus
I got a shot
Browser
The new Improved EDGE 2020
zigzag3143 said:
andexls said:
I have Windows 7 for 2 months now, and today was the first time that a BSOD showed up. It happened 3 times with a 2 or 3 hours interval.

I have an updated version of Windows 7 Ultimate 64-bits. All the drivers are updated also. My computer is a Core 2 Duo E7500 @2.93GHz, 2GB DDR2 RAM, Geforce 9800GT, 500GB HD.

All the three BSOD crashes happened when the computer was idle: only uTorrent and NOD32 4.0 were running. The screen appears for 1 second, then the computer restarts, and Windows shows a pop-up box saying that the system has just had an unexpected restart, or something like that.

There were 3 dump files in C:\Winodws\Minidump. They are all zipped and attached to this thread. Can someone help-me to find out what is the problem?

Thanks in advance!
Click to expand...


Hi Andexls

These crashes were caused by rt64win7.sys which as part of your reltek networking driver.

I would download and install a fresh copy of it.

I would also run a system file check
type cmd in search>right click and run as admin>SFC /SCANNOW

Good Luck

Ken







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\New folder\021910-21824-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\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`02a1c000 PsLoadedModuleList = 0xfffff800`02c59e50
Debug session time: Fri Feb 19 15:09:39.113 2010 (GMT-5)
System Uptime: 0 days 3:28:05.830
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {100002c, 2, 0, fffff80002ffd5d0}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+f102 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000100002c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ffd5d0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc40e0
 000000000100002c 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalBuildScatterGatherList+1a4
fffff800`02ffd5d0 448b5f2c        mov     r11d,dword ptr [rdi+2Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880037b4710 -- (.trap 0xfffff880037b4710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000007f7a62d0 rbx=0000000000000000 rcx=000000007f68e540
rdx=fffffa8003258ae0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ffd5d0 rsp=fffff880037b48a0 rbp=fffffa8003258aa0
 r8=0000000000000000  r9=fffffa800208e530 r10=fffffa8003258aa0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
hal!HalBuildScatterGatherList+0x1a4:
fffff800`02ffd5d0 448b5f2c        mov     r11d,dword ptr [rdi+2Ch] ds:0003:00000000`0000002c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a8d469 to fffff80002a8df00

STACK_TEXT:  
fffff880`037b45c8 fffff800`02a8d469 : 00000000`0000000a 00000000`0100002c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`037b45d0 fffff800`02a8c0e0 : 00000000`00000007 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`037b4710 fffff800`02ffd5d0 : 00000000`00000014 fffffa80`03531080 00000000`00000000 00000000`00000008 : nt!KiPageFault+0x260
fffff880`037b48a0 fffff880`0145c831 : fffffa80`021a6160 fffffa80`0322f0a0 00000000`00008e1e 00000008`00000000 : hal!HalBuildScatterGatherList+0x1a4
fffff880`037b4910 fffff880`0fdd4102 : fffffa80`02f051a0 fffffa80`03226000 fffffa80`0322f0a0 fffffa80`0322f0a0 : ndis!NdisMAllocateNetBufferSGList+0x181
fffff880`037b49b0 fffffa80`02f051a0 : fffffa80`03226000 fffffa80`0322f0a0 fffffa80`0322f0a0 fffffa80`03258aa0 : Rt64win7+0xf102
fffff880`037b49b8 fffffa80`03226000 : fffffa80`0322f0a0 fffffa80`0322f0a0 fffffa80`03258aa0 00000000`00000190 : 0xfffffa80`02f051a0
fffff880`037b49c0 fffffa80`0322f0a0 : fffffa80`0322f0a0 fffffa80`03258aa0 00000000`00000190 00000103`00000000 : 0xfffffa80`03226000
fffff880`037b49c8 fffffa80`0322f0a0 : fffffa80`03258aa0 00000000`00000190 00000103`00000000 00000000`00000000 : 0xfffffa80`0322f0a0
fffff880`037b49d0 fffffa80`03258aa0 : 00000000`00000190 00000103`00000000 00000000`00000000 0000a000`00000000 : 0xfffffa80`0322f0a0
fffff880`037b49d8 00000000`00000190 : 00000103`00000000 00000000`00000000 0000a000`00000000 00000014`00000000 : 0xfffffa80`03258aa0
fffff880`037b49e0 00000103`00000000 : 00000000`00000000 0000a000`00000000 00000014`00000000 00000000`00000001 : 0x190
fffff880`037b49e8 00000000`00000000 : 0000a000`00000000 00000014`00000000 00000000`00000001 00000000`00000004 : 0x103`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+f102
fffff880`0fdd4102 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  Rt64win7+f102

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49a65b0d

FAILURE_BUCKET_ID:  X64_0xA_Rt64win7+f102

BUCKET_ID:  X64_0xA_Rt64win7+f102

Followup: MachineOwner
---------
Click to expand...

Oh, I see. My network card drivers were the Windows 7 ones. I just installed the Asus drivers... let's see if this solves the problem!

And I've done a SFC /scannow, it says that it has found some problems, but could not fix all of them.
 

My Computer

OS
Windows 7
CPU
Core 2 Duo E7500 2993MHz
Motherboard
Asus P5KPL-AM/BR
Memory
2GB DDR2 800MHz
Graphics Card(s)
Geforce 9800GT
Sound Card
VIA VT1708B CE Integrated
Monitor(s) Displays
SyncMaster 592v 15"
Hard Drives
500GB SATA
PSU
Generic
Case
Generic
Cooling
Generic
You must log in or register to reply here.
Back
Top