• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Asus g2s with windows 7 help

C

chimimoryo

Junior Member
I have an old g2s, purchased about 6 or years ago. It was just sitting in my closet collecting dust, so I decided to break it out and use it as a HTPC rather than building a new one or spending any money on a media box. Plus it works well for talking to the parents and showing them their grandchild.
Well anyhow, it came with Vista installed on it and when 7 came out, I wiped the thing and put 7 on it. The vast majority of the drivers I could find and for the ones that I couldn’t find I didn’t think it was going to be much of a problem. And it wasn’t. I used it fine for about 1 or 2 years with 7 on it and it was very stable. Just an occasionally blue screen every now and then.
So here’s my problem. I busted it out of the closet about 6 months ago, and it was working no problem, just like it used to. Just an occasional blue screen about once or twice a month. Now, starting from last month or so, all hell has broken loose. Blue screens, crashes without blue screens, not waking up from sleep mode, and general sluggishness; more so than usual capped off with the webcam freezing constantly.
There is no rhyme or reason as to when these crashes occur. Starting a google hangout, opening chrome, clicking on links, trying to install windows updates, watching netflix, streaming videos on youtube, you get the picture. Basically the lowest common denominator is that the computer is on and running windows.
Can anyone help me diagnose the problem or point me into any directions?
 
Welcome to the forums.one question do you have 2gb or 4 gb memory.and what windows 7 are you running.32 bit or 64 bit.and for the BSOD.download whocrached and analyse.come back with report.
 
I see this kind of behavior when a memory stick is going bad. Not always, depends what slot it's in. Usually starts with a blue screen every once in a while, and gets more and more common over time. Might be worth checking.
 
thanks for your reply. i did what you told me about who crashed and it recommended me to update my wireless driver. below are the particulars. also im running win 7 64bit and added an extra 2gigs to the laptop bringing it to 4gigs. also how can i tell if the ram is going bad?

here is whocrased analysis
System Information (local)
--------------------------------------------------------------------------------

computer name: ULI-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294238208 total
VM: 2147352576, free: 1879797760




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 8/14/2013 1:52:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081413-83366-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE7C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006AAA718, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 8/14/2013 1:20:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081413-34086-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006BA0308, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 8/14/2013 1:05:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081413-44803-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80069476D8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 8/12/2013 3:34:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081213-50435-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 8/12/2013 3:34:54 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: i8042prt.sys (i8042prt+0x28FA)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\i8042prt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: i8042 Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 8/11/2013 12:07:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-43508-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80069618F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 8/11/2013 11:57:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-44117-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800691D038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 8/11/2013 10:34:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-47315-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002F39211)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 8/10/2013 10:53:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081013-47377-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002F74211)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 8/8/2013 12:19:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-45099-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006911038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 8/8/2013 12:13:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-44382-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80068FD038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 8/8/2013 12:06:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-48438-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80069158F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 8/7/2013 12:47:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-36691-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002F30211)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 7/29/2013 10:02:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072913-44413-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002F83211)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 7/28/2013 12:01:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-83039-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006921748, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

45 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 
chimimoryo said:
thanks for your reply. i did what you told me about who crashed and it recommended me to update my wireless driver. below are the particulars. also im running win 7 64bit and added an extra 2gigs to the laptop bringing it to 4gigs. also how can i tell if the ram is going bad?
Click to expand...

Hello chimimoryo, let's focus on getting an updated version of that wireless driver first. If the problem keeps occurring after that, and keeps pointing to difference drivers, we can look at the possibility of another issue, like RAM.
 
thanks for all of your suggestions. after updating that network driver, it has been running stably. thanks for pointing me towards that software!!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top