BSOD occurs even in safe mode.

Toggle sidebar Toggle sidebar
K

Kenneth_SJ

Reputable
Mar 26, 2015
6
0
4,510
So in just a day, i have several BSODs. It even occurs in safemode as of now im trying to write this thread =(.

It occurs maybe about 10-20 mins after boot..

Attached link is the minidumps. driverslist..eventapps/sys,, etcetc.
https://www.dropbox.com/s/546ihvlw6x279u8/SF_05-06-2015.rar?dl=0

Could anyone take a look through it and identify the exact problem that is causing it? maybe a driver?
Then maybe list down the necessary steps for me to solve it.

I appreciate it very much for taking a look!

Sincerely,Kenneth.
 
Solution
J
all of the various bugcheck are caused by memory corruption of device driver data.
I would remove some of the device drivers listed below, then reboot. if you continue to get memory corruption there will be two causes.
First you would want to check for bad BIOS memory timings and hardware problems by running memtest86.

and second you would want to force windows to check device drivers for common programming mistakes that cause memory corruption. To do this you would start cmd.exe as an admin then run
verifier.exe /standard /all
then reboot, if windows detectes problems it will force a bugcheck of the system and name the bad driver in the memory dump file.

note: uses the command
verifier.exe /reset
to turn off this extra...
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
all of the various bugcheck are caused by memory corruption of device driver data.
I would remove some of the device drivers listed below, then reboot. if you continue to get memory corruption there will be two causes.
First you would want to check for bad BIOS memory timings and hardware problems by running memtest86.

and second you would want to force windows to check device drivers for common programming mistakes that cause memory corruption. To do this you would start cmd.exe as an admin then run
verifier.exe /standard /all
then reboot, if windows detectes problems it will force a bugcheck of the system and name the bad driver in the memory dump file.

note: uses the command
verifier.exe /reset
to turn off this extra checking after you are done testing or your machine will run slowly until you do.

be sure to remove any of the below drivers that you really don't need or update them if you can.
many of them will fail windows verification when it is turned on.
-------------
first bugcheck was caused by a bad memory address used by virus scanner.
most likely its memory was corrupted by another driver.

remove:
\SystemRoot\system32\DRIVERS\AiCharger.sys Wed Oct 20 05:00:33 2010
\SystemRoot\SysWow64\drivers\AiChargerPlus.sys Wed Apr 18 18:17:35 2012
\SystemRoot\SysWow64\drivers\AsUpIO.sys Mon Aug 02 19:47:59 2010
C:\Windows\system32\drivers\IOMap64.sys Thu Feb 04 17:55:34 2010
all of these tend to corrupt memory, the last one iomap64.sys particularly.
remove:
C:\Program Files (x86)\Common Files\Realtime Soft\UltraMonMirrorDrv\x64\UltraMonUtility.sys Thu Nov 13 17:10:30 2008

suspect driver you should test:
\SystemRoot\system32\DRIVERS\evolve.sys Fri Aug 06 21:47:00 2010

suspect driver: (just the razer overlay driver)
C:\Windows\system32\drivers\rzpmgrk.sys Thu Apr 17 12:36:12 2014
 
Upvote 0 Downvote
Solution
K

Kenneth_SJ

Reputable
Mar 26, 2015
6
0
4,510
Thank you john! I did all those steps and been testing my computer. So Far so good! I really appreciate you telling me all these drivers and steps for me to rectify the problem.

Cheers!
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom