BSoD Crashes frequently, i don't know what to do.

[Wikkedly]

Hi, My system specs are:

Operating System
Windows 7 Home Premium 64-bit SP1
CPU
AMD FX-4100 29 °C
Zambezi 32nm Technology
//Possibly old and needs upgraded?
RAM
16.0GB Dual-Channel DDR3 @ 722MHz (9-9-9-24)
// Two four Gb sticks, one eight Gb.
Motherboard
ASUSTeK COMPUTER INC. M5A97 LE R2.0 (Socket 942) 36 °C
//Could my MoBo cause this?
Graphics
DELL 1704FPT (1280x1024@60Hz)
LRK32G30RQ (2560x1440@60Hz)
2048MB ATI AMD Radeon R9 200 Series (ASUStek Computer Inc) 57 °C
1024MB ATI AMD Radeon HD 6570 (Sapphire/PCPartner) 46 °C
CrossFire Disabled
//R9 is main (obv.) two monitors connected, HD is not in use.
Storage
931GB Western Digital WDC WD10 EARS-22Y5B1 SATA Disk Device (SATA) 36 °C
931GB Seagate ST1000DM 003-1ER162 SATA Disk Device (SATA) 34 °C
465GB Seagate ST500DM0 02-1BC142 SATA Disk Device (SATA) 32 °C
232GB Maxtor 7 L250S0 SATA Disk Device (SATA)
//Possible corruption? should i just reformat everything and start from scratch?
Power Supply
Corsair RM 750

If you need any additional information please feel free to ask.

BSoD *event viewer* Critical Info.
1. - System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2016-05-04T03:07:25.830414600Z

EventRecordID 173960

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Home Computer

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 10
BugcheckParameter1 0xfffffa802d52d010
BugcheckParameter2 0x2
BugcheckParameter3 0x1
BugcheckParameter4 0xfffff800041373c6
SleepInProgress false
PowerButtonTimestamp 0


2.- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2016-05-04T02:44:47.222013500Z

EventRecordID 173816

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Home Computer

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 268435582
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff8801115e9f0
BugcheckParameter3 0xfffff88002d97f68
BugcheckParameter4 0xfffff88002d977c0
SleepInProgress false
PowerButtonTimestamp 0


3. - System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2016-05-03T18:38:09.705614300Z

EventRecordID 172731

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Home Computer

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 59
BugcheckParameter1 0xc0000005
BugcheckParameter2 0xfffff800041b19cc
BugcheckParameter3 0xfffff88009debf60
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0


4. - System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2016-05-03T16:37:48.392015500Z

EventRecordID 172429

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Home Computer

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 26
BugcheckParameter1 0x783
BugcheckParameter2 0xfffff88003185680
BugcheckParameter3 0xfffff98042480000
BugcheckParameter4 0xfffff8a016ebd440
SleepInProgress false
PowerButtonTimestamp 0


5. - System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2016-05-02T20:07:58.579215800Z

EventRecordID 170495

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Home Computer

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 25
BugcheckParameter1 0x21
BugcheckParameter2 0xfffff900c085a000
BugcheckParameter3 0x1240
BugcheckParameter4 0xf700000000001240
SleepInProgress false
PowerButtonTimestamp 0


6. - System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2016-05-02T20:07:58.579215800Z

EventRecordID 170495

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Home Computer

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 25
BugcheckParameter1 0x21
BugcheckParameter2 0xfffff900c085a000
BugcheckParameter3 0x1240
BugcheckParameter4 0xf700000000001240
SleepInProgress false
PowerButtonTimestamp 0


I have 50+ more Events like this since the start of the year. But i don't know what to do with any of this informations or what it's telling me.

Ive Run malwarebytes anti-malware, Ccleaner, checked the ram, switched out video cards, psu's, one of my HDD's is brand new in hopes that i could figure out how to fix it.

I do not have Windows currently available, however i do have 2 32Gb+ flash drives. Please be patient as i am not the most skilled with fixing computers

 

[Wikkedly]

This is the screen that appears when trying to start it normally with verifier on.
my first attempt i logged in and it just went to that, second attempt i just let it sit for a moment and after roughly the same amount of time passed it went to the same screen.

http://gyazo.com/39b623fa1c71ae9580f2ebe04f11e7c4

I have not had this issue before, only when attempting to restart my computer after following the instructions of switching memory dump type and running verifier.


I do not have an integrated gpu.

all of my temps are well below 40c like 31c is the highest i have.
Nothing on my computer was touched from between before and after this process of memory dump type and verifier.

I considered plugging in the possible problematic memory stick i have since it would double my current but decided against is since it was likely causing some of my blue screens.

So yeah i'm currently running with 8 gbs of ram and yes it's a bit slow but i'm just sad that i can't follow through with the instructions so that you all can help me.

 

[johnbl]

check the video cables for a good connection, or disconnect a video cable and reconnect it.

This is the screen that appears when trying to start it normally with verifier on.
my first attempt i logged in and it just went to that, second attempt i just let it sit for a moment and after roughly the same amount of time passed it went to the same screen.

http://gyazo.com/39b623fa1c71ae9580f2ebe04f11e7c4

I have not had this issue before, only when attempting to restart my computer after following the instructions of switching memory dump type and running verifier.


I do not have an integrated gpu.

all of my temps are well below 40c like 31c is the highest i have.
Nothing on my computer was touched from between before and after this process of memory dump type and verifier.

I considered plugging in the possible problematic memory stick i have since it would double my current but decided against is since it was likely causing some of my blue screens.

So yeah i'm currently running with 8 gbs of ram and yes it's a bit slow but i'm just sad that i can't follow through with the instructions so that you all can help me.

 

[Wikkedly]

Okay i checked them just incase anything had happened to them, Unplugged them and and replugged them in, they are plugged in securely, Out of curiosity why would i be able to run fine without verifier and verifier in safe mode but nor with verifier normally if it was a loose video cable?

 

[johnbl]

- you can run verifier.exe /? to see some of the options on how to selectively run verifier.
the flags option shows what each flag means:

/flags <options> [<options> ...]
Specifies one or more options that should be enabled for verification.
Flags are applied to all drivers being checked by Driver Verifier. The
provided options values must be either in decimal, hexadecimal ("0x"
prefix), octal ("0o" prefix) or binary ("0b" prefix) format.

Standard Flags:
Standard Driver Verifier options can be specified using '/standard'
or '/flags 0x209BB'.

0x00000001 (bit 0) - Special pool
0x00000002 (bit 1) - Force IRQL checking
0x00000008 (bit 3) - Pool tracking
0x00000010 (bit 4) - I/O verification
0x00000020 (bit 5) - Deadlock detection
0x00000080 (bit 7) - DMA checking
0x00000100 (bit 8) - Security checks
0x00000800 (bit 11) - Miscellaneous checks
0x00020000 (bit 17) - DDI compliance checking

Additional Flags:
These flags are intended for specific scenario testing. Flags marked
with (*) require I/O Verification (bit 4) that will be automatically
enabled. Flags marked with (**) support disabling of individual
rules.

0x00000004 (bit 2) - Randomized low resources simulation
0x00000200 (bit 9) - Force pending I/O requests (*)
0x00000400 (bit 10) - IRP logging (*)
0x00002000 (bit 13) - Invariant MDL checking for stack (*)
0x00004000 (bit 14) - Invariant MDL checking for driver (*)
0x00008000 (bit 15) - Power framework delay fuzzing
0x00010000 (bit 16) - Port/miniport interface checking
0x00040000 (bit 18) - Systematic low resources simulation
0x00080000 (bit 19) - DDI compliance checking (additional)
0x00200000 (bit 21) - NDIS/WIFI verification (**)
0x00800000 (bit 23) - Kernel synchronization delay fuzzing
0x01000000 (bit 24) - VM switch verification
0x02000000 (bit 25) - Code integrity checks




you should be able to run fine with verifier running, it adds tracking for all the memory allocation so it tends to tie up more memory and it does more checking for driver problems so it will slow down program that is being running.

verifier is useful when trying to find problems that are caused by drivers because of the extra checking it does and the extra debug info it provides.

normally the screen that you showed should not be caused by verifier, but I have Isolated some interactions before that just seem totally unrelated. You can be more selective in the use of verifier.exe You can have it only verify certain drivers for example, or you can have it only do certain types of verifications. There are a lot of options, I just tell people to run the standard tests on all of the drivers because it is easy to explain and hits most of the cases of failure.

when you suspect certain drivers or subsystem you would only test those drivers and what you think is failing. For the most part this is what you would do if you were the developer of the driver and had access to the code to make a fix. For most people, just knowing what driver caused the problem is the best we can do. Knowing why the driver had the problem is just extra debugging. The solution is the same, you have to get a driver update from the developer of the driver.

Okay i checked them just incase anything had happened to them, Unplugged them and and replugged them in, they are plugged in securely, Out of curiosity why would i be able to run fine without verifier and verifier in safe mode but nor with verifier normally if it was a loose video cable?

 

[Wikkedly]

yeah i ran verifier /standard /all then went to reboot.

thank you for explaining all that, i feel like i understand it a little bit better, though i'm not sure what i'm supposed to do with it now, like i get that i can be precise about what i want verified and how but i dont know what to focus on.

i had though that the memory was the issue, but if i'm still having issues is is okay to put it back in? or is it likely that two or more things may be messing up around the same time?

 

[Hellfire13]

sometimes a combination of hardware components can be as messy as one single faulty component...for eg, once when i had this problem of bsods and sudden crashes, i tried all possible tests and checks but to no avail...even individually the ram and the hdd passed all tests inspite of ongoing freezes and crashes...but when i was fed up and finally decided to change both the ram and hdd, the problem disappeared...so yeah, u may never know whther one dying component is playing up or whether its a combination of factors...

 

[Wikkedly]

okay well i think for now i will turn verifier off until i know more precisely what to verify etc, i can still mostly use my computer. ^_^

 

[Hellfire13]

wats ur situation now...how frequent are the crashes???

 

[Wikkedly]

well not as often now, though i have had it in safe mode for the last two days, last crash was on the 19th before that was twice on the 18th

 

[Hellfire13]

and is this with the faulty ram stick attached or detached???

 

[Wikkedly]

it's not attached, hasn't been since i ran those memory tests

 

[Hellfire13]

and if u r to specify one single test or check that u have performed since the starting of this thread, that has reduced the bsods or made a difference from bfore...which one wud tht be???

 

[Wikkedly]

well i had thought that the memory tests and updating drivers was helping but i'm still getting blue screens that point to either drivers or memory but without my 8 gb stick in and after i updated all my drivers i still get them, one this morning was irql not equal or less so :/
really i kinda feel like im at square one.

 

[Hellfire13]

hmmm...well wat can i say....we have exhausted all possibilities...at this stage i can only suggest u one thing...
get to a nearest professional shop and ask them to test ur hardwares as they have lots of spares/substitutes...ideally thy wont charge u much for testing and pinpointing the source...

 

[Wikkedly]

well as far as i know the only computer shop near me is best buy and the geek squad.... well i will stop there but my opinion of them isnt very good x.x

 

[Hellfire13]

i blv...from the last few days discussions, u must have grasped a lot than bfore , and have a fairly gud idea wat u r dealing with...just stand and observe them closely while thy perform the diagnostic and u shd be able to make out if thy r correct or not...