Multiple BSOD daily during Web Browsing and Gaming

[slinn1992]

While running memtest for the second time. My memory came back with errors. Could this also be what is effecting my cpu being registered as new each restart? If so i will buy new ram but if it looks like it could be more than just my ram then i will have to save up for new parts

 

[YoYo155]

RAM errors are not a good sign.
About your CPU registering as a newly installed each time is at the motherboard end,
its a semi-common issue with Asus motherboards mainly with AMI BIOS.

 

[slinn1992]

I'm going to go buy a new stick of ram and cmos battery. Ill let you know or results. Once i get it back set up.

 

[slinn1992]

Even with new RAM pc is getting BSOD. I believe new CMOS battery fixed Bios issues. Here is the most recent dump file.
Thanks again for all the help.

 

[YoYo155]

Your first dump is pointing a finger towards your GPU once again.
What is the make and model of your PSU and how old is it?
Please fill out this form and post the Wattage value its calculating | Recommended Power Supply Wattage Calculator .


Your 2nd dump however was more a little bit more revealing:

fffff880`02ffd318  fffff880`03cf0d10 [COLOR=Red][U][B]netr28x[/B][/U][/COLOR]+0x2d10
fffff880`02ffd328  fffff880`03cf06c0 [COLOR=Red][U][B]netr28x[/B][/U][/COLOR]+0x26c0
fffff880`02ffdbf8  fffff880`03cf0d10 [COLOR=Red][U][B]netr28x[/B][/U][/COLOR]+0x2d10
fffff880`02ffdc08  fffff880`03cf06c0 [COLOR=Red][U][B]netr28x[/B][/U][/COLOR]+0x26c0

    Loaded symbol image file: netr28x.sys
    Image path: \SystemRoot\system32\DRIVERS\netr28x.sys
    Image name: netr28x.sys
    Timestamp:        [COLOR=Red][U][B]Thu Feb 26 05:02:09 2009[/B][/U][/COLOR] (49A60631)

802.11n Wireless LAN Card
Ralink 802.11n Wireless Driver for Windows [COLOR=Red][U][B]Vista[/B][/U][/COLOR]

Driver Reference Table - netr28x.sys

I couldn't locate the exact model of the adapter, what is it?
If you don't find an updated Windows 7 driver remove the adapter.
​

 

[slinn1992]

My PSU is a coolermaster 600w, and it is new. The Power wattage calculator suggests 450w. The adaptor is a Tenda 300Mbps Wireless PCI adaptor/ Model Number.. W322P V2.0

 

[slinn1992]

I just installed new driver from W322P Wireless N300 PCI Adapter for the v2.0 model. It says that it is supposed to be compatible with windows 7.

 

[YoYo155]

Ok that PSU should be enough.

I found this | W322Pv2.0Drivers - Tenda |
But I'm not entirely happy with it, its from 2010.

Before installing this version uninstall the currently installed driver:

• Remove any software related to the adapter.
• rb: Start Menu> type Device Manager and select device manager from the options presented.
• Expand Network Adapters, find your wireless adapter (if you're not sure which one post a screenshot)
• Right-click the correct device and choose Uninstall.
• Remove the adapter physically from the PC.
• Reboot the PC.
• Reconnect the adapter and install the newly downloaded driver.

 

[slinn1992]

I installed the new driver without removing the hardware should I re-uninstall the driver and remove hardware, do a restart, then install the hardware then drivers?

 

[YoYo155]

Its preferable to do it that way in-order to avoid conflicts,
but since you already installed it we can wait and see how it goes.

To confirm that the new drivers are in use, upload a new instance of the MSINFO32 file:

Start> RUN> "MSINFO32" without the quotes then hit [Enter].
In "MSINFO32" go to, File> Save> name it your user-name and upload.
​

 

[slinn1992]

here is the file requested

 

[YoYo155]

Yes the driver has been updated.

c:\windows\system32\drivers\netr28x.sys ([U][B]3.0.0.41[/B][/U], 606.00 KB (620,544 bytes), 10/06/2009 2:35 PM)

c:\windows\system32\drivers\netr28x.sys ([U][B]3.1.0.0[/B][/U], 899.28 KB (920,864 bytes), 17/08/2013 3:42 PM)

Post back with further developments .

 

[slinn1992]

and the BSOD continues, here is the most recent logs. I am heading to work will be back on working in a couple hours. Thanks for the help this computer will be the death of me. I'll check forums at work. so if you need any information just shout.

 

[slinn1992]

I had pc running FurMark and Prime 95 to test the hardware, but they both did not cause a crash. After turning these off. I Blue screened again. The Debug points to hardware, but I don't know how to diagnose which piece it is.
I bought new RAM and installed it because of previous memtest reading, and chkdsk came back clean on the HDD. does that either mean it is my CPU or GPU or motherboard?
after multiple days of diagnostics. I am about ready to give up and save up for a new PC.


*************************************************************************
Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )

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


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:
------------------

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: System

CURRENT_IRQL: 0

TAG_NOT_DEFINED_c000000f: FFFFF88002F22FB0

EXCEPTION_RECORD: fffff88002f1ba38 -- (.exr 0xfffff88002f1ba38)
ExceptionAddress: fffff80002e2b802 (hal!KeQueryPerformanceCounter+0x000000000000010e)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME: fffff88002f1bae0 -- (.trap 0xfffff88002f1bae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000004ac0557d5 rbx=0000000000000000 rcx=0000000000000001
rdx=000012b000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e2b802 rsp=fffff88002f1bc70 rbp=0000000000000000
r8=0000000000000000 r9=00000000002faf5f r10=000000000002572c
r11=fffffa8006c65738 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
hal!KeQueryPerformanceCounter+0x10e:
fffff800`02e2b802 c4 ???
Resetting default scope

MISALIGNED_IP:
hal!KeQueryPerformanceCounter+10e
fffff800`02e2b802 c4 ???

LAST_CONTROL_TRANSFER: from fffff80002ed257e to fffff80002edab50

STACK_TEXT:
fffff880`02f1ab18 fffff800`02ed257e : fffff880`02f1ae50 00000000`cf7fe53c fffff880`02f1b290 fffff800`02f05a90 : nt!KeBugCheck
fffff880`02f1ab20 fffff800`02f0575d : fffff800`030e90e0 fffff800`03027a80 fffff800`02e65000 fffff880`02f1ba38 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1ab50 fffff800`02f04535 : fffff800`0302a038 fffff880`02f1abc8 fffff880`02f1ba38 fffff800`02e65000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1ab80 fffff800`02f154e1 : fffff880`02f1ba38 fffff880`02f1b290 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x415
fffff880`02f1b260 fffff800`02eda202 : fffff880`02f1ba38 00000000`00000000 fffff880`02f1bae0 fffff880`009eb180 : nt!KiDispatchException+0x135
fffff880`02f1b900 fffff800`02ed835f : fffff880`02f1bae0 00000000`00000500 fffffa80`08a82000 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f1bae0 fffff800`02e2b802 : 00000000`00000010 00000000`00000246 fffff880`02f1bc98 00000000`00000018 : nt!KiInvalidOpcodeFault+0x11f
fffff880`02f1bc70 fffff800`02ee3786 : 00000000`002faf5f 00000000`00000000 fffffa80`0855a470 00000000`00000000 : hal!KeQueryPerformanceCounter+0x10e
fffff880`02f1bca0 fffff800`02ed285c : fffff880`009eb180 fffff880`00000000 00000000`00000000 fffff880`014c9800 : nt!PoIdle+0x5a7
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02ed257e 90 nop

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

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

 

[YoYo155]

slinn1992, I'm sorry you feel this way but if you wish to give up on the PC
the decision is only yours to make, I believe there are other avenues that we have yet
to try.

I just have to ask,
What is the new RAM configuration?

Will you be willing to perform a clean Windows install?
Will you be able to run without your GPU? (for troubleshooting purposes)
Will you be able to switch to a wired inernet connection? (for troubleshooting purposes)

 

[slinn1992]

I could perform another clean install, my ram is in slots a1 and b1, i did another ram test and he new memory came back with errors so it could be my ram slots. I. Going to try slots a2 and b2. I may be able to run a cable from the router to the computer. Ill check to see if i have one long enough.

 

[slinn1992]

Also, I have no way to run without the gpu as there is no on board gpu.

 

[YoYo155]

I could perform another clean install, my ram is in slots a1 and b1, i did another ram test and he new memory came back with errors so it could be my ram slots. I. Going to try slots a2 and b2. I may be able to run a cable from the router to the computer. Ill check to see if i have one long enough.

Did you read the tutorial in detail?
Part 3 in particular?

Did you buy a new 2 DIMM kit, or are you using the old RAM along with the new RAM?

 

[slinn1992]

Im sorry which tutorial? I bought a new 2 stick kit.

 

[YoYo155]

In safe mode it did not crash immediatly and I was able to run the driver sweeper and install the new drivers. I also have posted the most recent dump file.

Yes, I only have one RAM module

Were you able to install the suggested drivers?
Does it still bugcheck?

I recommend you remove Avast using Avast Removal Tool.

Install Microsoft Security Essentials instead.
​

If problems persists:

• http://www.sevenforums.com/tutorials/433-disk-check.html
• http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
  

Those bullet points are links :huh: