BSOD and freezing

[Curtisv94]

I have recently been getting BSODs and freezing. Originally it was system service exceptions during gaming but after a system recovery and reinstalling the nvidia drivers those are gone.

I am now getting freezing the pc completely locks up without any errors and requires a restart. I've also gotten 3 new bsods all different.

http:// Link to dropbox with the 3 most recent dmp files

 

[johnbl]

you had 3 bugchecks each returned a error code that means memory was corrupted.

1 bugcheck in networking, one bugcheck in virutual memory, and another in the windows user kernel.

I would think that either one of the drivers below is corruptiong memory or you have a physical ram timing problem or a RAM defect. You can test for that by downloading and running memtest86 and confirm your memory settings are ok.

There is a chance that the problem in in the plug and play system with your mouse driver but you would have to change your memory dump type to kernel and provide memory.dmp file. Based on how fast your machine bugchecks, I would run the memtest86 first and confirm your ram is ok. The overclocking software can mess up the ram timings while in windows, and the old mouse driver might be using methods that are not allowed in windows 8 (pooling at two high a rate)



first bugcheck was caused by a bad memory address passed to a driver.

update the following drivers: and remove the overclocking driver and retest.


old driver:
Asus PCProbe Utility
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012
overclocking driver:
C:\WINDOWS\system32\drivers\IOMap64.sys Wed Oct 22 17:52:12 2014

check for update for:
SteelSeries Engine HID Driver
\SystemRoot\System32\drivers\SAlpham64.sys Fri May 31 07:19:10 2013


Manufacturer ASUSTeK COMPUTER INC.
Product M5A97 R2.0

BIOS Version 2603
BIOS Starting Address Segment f000
BIOS Release Date 06/26/2015

Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4000MHz
Current Speed 4000MHz

 

[Curtisv94]

you had 3 bugchecks each returned a error code that means memory was corrupted.

1 bugcheck in networking, one bugcheck in virutual memory, and another in the windows user kernel.

I would think that either one of the drivers below is corruptiong memory or you have a physical ram timing problem or a RAM defect. You can test for that by downloading and running memtest86 and confirm your memory settings are ok.

There is a chance that the problem in in the plug and play system with your mouse driver but you would have to change your memory dump type to kernel and provide memory.dmp file. Based on how fast your machine bugchecks, I would run the memtest86 first and confirm your ram is ok. The overclocking software can mess up the ram timings while in windows, and the old mouse driver might be using methods that are not allowed in windows 8 (pooling at two high a rate)



first bugcheck was caused by a bad memory address passed to a driver.

update the following drivers: and remove the overclocking driver and retest.


old driver:
Asus PCProbe Utility
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012
overclocking driver:
C:\WINDOWS\system32\drivers\IOMap64.sys Wed Oct 22 17:52:12 2014

check for update for:
SteelSeries Engine HID Driver
\SystemRoot\System32\drivers\SAlpham64.sys Fri May 31 07:19:10 2013


Manufacturer ASUSTeK COMPUTER INC.
Product M5A97 R2.0

BIOS Version 2603
BIOS Starting Address Segment f000
BIOS Release Date 06/26/2015

Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4000MHz
Current Speed 4000MHz

Ran memtest and everything passed with no errors.

Also disabled Amd turbo boost in bios as I read of issues with that and freezing and blue screens.

I updated the steel series engine for my mouse so that should do the driver too correct?

The other two drivers mentioned how would I remove those? Just simply delete them?

I'll try running some games now as those were causing the issues mostly before.

 

[johnbl]

the other two drivers were asus tools, you should look to see if they have a uninstall program for them.

you had 3 bugchecks each returned a error code that means memory was corrupted.

1 bugcheck in networking, one bugcheck in virutual memory, and another in the windows user kernel.

I would think that either one of the drivers below is corruptiong memory or you have a physical ram timing problem or a RAM defect. You can test for that by downloading and running memtest86 and confirm your memory settings are ok.

There is a chance that the problem in in the plug and play system with your mouse driver but you would have to change your memory dump type to kernel and provide memory.dmp file. Based on how fast your machine bugchecks, I would run the memtest86 first and confirm your ram is ok. The overclocking software can mess up the ram timings while in windows, and the old mouse driver might be using methods that are not allowed in windows 8 (pooling at two high a rate)



first bugcheck was caused by a bad memory address passed to a driver.

update the following drivers: and remove the overclocking driver and retest.


old driver:
Asus PCProbe Utility
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012
overclocking driver:
C:\WINDOWS\system32\drivers\IOMap64.sys Wed Oct 22 17:52:12 2014

check for update for:
SteelSeries Engine HID Driver
\SystemRoot\System32\drivers\SAlpham64.sys Fri May 31 07:19:10 2013


Manufacturer ASUSTeK COMPUTER INC.
Product M5A97 R2.0

BIOS Version 2603
BIOS Starting Address Segment f000
BIOS Release Date 06/26/2015

Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4000MHz
Current Speed 4000MHz

Ran memtest and everything passed with no errors.

Also disabled Amd turbo boost in bios as I read of issues with that and freezing and blue screens.

I updated the steel series engine for my mouse so that should do the driver too correct?

The other two drivers mentioned how would I remove those? Just simply delete them?

I'll try running some games now as those were causing the issues mostly before.