Tech Support Guy banner
Status
Not open for further replies.
1 - 5 of 5 Posts

·
Registered
Joined
·
3 Posts
Discussion Starter · #1 ·
Laptop Specs:

Inter(R) Core(TM)2 Duo CPU P8700 @ 2.53 GHz
Installed Memory (RAM): 4.00 GB
System Type: 64-bit OS

For more detail, it's the Dell Studio XPS 16, barring a few minor modifications (such as the Windows 7).

From Windows Error Thing:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF800037EC477
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Comments:
My laptop had been working fine and dandy until I came back from Minnesota to Florida, on the 22nd. I don't recall installing a lot of programs. I did install Mass Effect, not sure if that has a lot to do with it. Also some updated drivers for my graphics card, thinking I might downgrade the drivers (is that possible?).Somewhere along the lines, I started getting Blue Screen'd, not totally super frequent, but a couple times a day (I use my computer a lot).

I researched this problem, and some concerns were raised about overheating, though using programs (in particular Everest), it didn't seem like it reached overbearing temperatures i.e. never got past 60 degrees celcius.

At this, I'm utterly lost as to how to proceed. I've thought about buying of them compressed-air cans and trying to clean it out, see if that helps, but I figured I oughta ask more experienced people. Help?

tl;dr
I'm getting blue screen'd, details above, haven't really installed a lot of things barring Mass Effect and some drivers for graphics cards.

Please help. : (
 

·
Registered
Joined
·
143 Posts
Download WhoCrashed from this link http://www.resplendence.com/downloads

This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It may want to download the Debugger and install it Say Yes

WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
 

·
Registered
Joined
·
3 Posts
Discussion Starter · #3 ·
I did as instructed, and here's the analysis:


Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 12/28/2010 3:04:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122710-25490-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003214477)
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 which cannot be identified at this time.


On Tue 12/28/2010 3:04:18 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netw5v64.sys (netw5v64+0x5B7D)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003214477)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netw5v64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: netw5v64.sys Intel Corporation IRQL_NOT_LESS_OR_EQUAL



On Tue 12/28/2010 12:16:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122710-27783-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037EC477)
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 which cannot be identified at this time.


On Mon 12/27/2010 9:26:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122710-51761-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037D6477)
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 which cannot be identified at this time.


On Sun 12/26/2010 1:38:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122510-23150-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000321A477)
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 which cannot be identified at this time.


On Sun 12/26/2010 12:17:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122510-28267-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037E2477)
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 which cannot be identified at this time.


On Fri 12/24/2010 3:40:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-30934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41287, 0x30, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/24/2010 3:32:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-33493-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003216477)
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 which cannot be identified at this time.


On Fri 12/24/2010 3:04:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-28314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037F0477)
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 which cannot be identified at this time.


On Fri 12/24/2010 1:19:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-23712-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003207477)
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 which cannot be identified at this time.


On Fri 12/24/2010 1:04:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-29125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037EB477)
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 which cannot be identified at this time.


On Thu 12/23/2010 4:49:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-30108-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000320A488)
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 which cannot be identified at this time.


On Thu 12/23/2010 7:54:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-22885-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000321A477)
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 which cannot be identified at this time.


On Thu 12/23/2010 6:56:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-44538-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003221477)
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 which cannot be identified at this time.


On Sun 10/17/2010 6:13:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101710-40388-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF860033F46BC, 0x1, 0xFFFFF800033AE2C2, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 which cannot be identified at this time.


Conclusion
22 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have 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:

pneteth.sys (PdaNet Broadband Adapter Driver, June Fabrics Technology Inc.)

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.
 

·
Registered
Joined
·
143 Posts
It seems that there might be a problem with the network adapter. uninstall the adapter and uninstall the drivers. Then make sure windows is up to date and check on line to see if you have the latest drivers for your network card. You also need to check your memory. go to http://www.memtest86.com/ and download the .iso image and burn it to a disc. Then test the memory one stick at a time. You could also pull out one stick of memory now and see if the pc crashes. If it does then swap the sick out for the other one and see what happens.
 

·
Registered
Joined
·
3 Posts
Discussion Starter · #5 ·
It seems that there might be a problem with the network adapter. uninstall the adapter and uninstall the drivers.
This is embarrassing but...how do I know what to uninstall? Like, how do I unstill the adapter? What exactly is the adapter?
 
1 - 5 of 5 Posts
Status
Not open for further replies.
Top