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

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
Wikkedly

Wikkedly

Reputable
Dec 26, 2015
58
0
4,660
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
 
Sort by date Sort by votes


So i was going to do the rest of my hdds when i got home but i dont think i need to, it crashed while i was at work, and i have some new information for you.

"Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA80056A5BE0
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050716-28142-01.dmp
C:\Users\Lilianna\AppData\Local\Temp\WER-26154550-0.sysdata.xml"

Also I checked event viewer and there's an error at the same time of a critical.
which is normal other than the warning reads as:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041790, 0xfffffa80056a5be0, 0x000000000000ffff, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\050716-28142-01.dmp. Report Id: 050716-28142-01.

I don't know if any of this is useful to you but i figured better safe than sorry.
Also my mobo doesn't have an integrated gpu 🙁
 
Upvote 0 Downvote
ok...this is interesting...
0x0000001a refers to a faulty memory module...
ur ram passed the memtest u said...i am not sure wat to interpret frm tht...

run mdsched from ur start menu at "Extended" level...
and only keep ur windows drive attached for the time being...disconnect all other drives...
 
Upvote 0 Downvote


well, i have run memtest when i originally started getting crashes around the end of last year or so, i let it run for several hours though i ended it because it never said there was any issue and because i dont knoew if memtest has an end or just keeps testing.
I have not rerun the test though, how long should i let it run?

 
Upvote 0 Downvote
ok...detach all ur disk drives except the windows drive...
on ur start menu...type "mdsched" and press enter...
it will prompt u to execute it "right now" or on ur next restart...
u choose now and the system will restart...but it will take u to a blue screen just like bsod where ur memory test interface will reflect...
by default it will do a normal test, but if u press F1, u can change the level...
first let it run on "Normal" level...it will run for a few minutes to an hour...if it finds something, it will show on ur screen...
else u press F1 and select "Extended"...and let it run its course...

this test in not unlimited...so it will give u a prompt when it is complete and/or reflect the result on ur screen...
when i ran it last time...it took around 36hrs to complete the "Extended" level...
for u, it might take more or less...but be prepared for a long journey...
 
Upvote 0 Downvote


Okay so, it's crashed 2 times attempting to run the memtest, i'm, 90%+ sure that i started a 3rd today @~8am but the event viewer doesn't show anymore crashes and it was on logon screen when i got home, thore doesn't appear to be any results to look at, so i'm kind of confused, i figured i will attempt the mem test one stick at a time, Unless you have additional information to inform me about i will give you any and all findings as soon as i have them.

 
Upvote 0 Downvote


Hey so i did the first one, and it was at 60% before i went to sleep, but how can i find out the results of the test?

Also i'm wondering how much it makes a difference to have your memory in the proper slots, like i have 2 matching 4gbs and 1 solo 8 gb

The MoBo obviously declares the slots as a1 a2 b1 b2, However the color coding for them is a1 and b1 are blue and a2 and b2 are black, earlier i guess i has the two 4gb sticks on a1 and b1 and the 8gb on a2. but i just adjusted them after i tested the 4gb in a1 slot so not a1 a2 are both my 4gbs and b1 is my 8gb.

If this is the entire cause of my crashes i apologize for not bringing it up sooner.
 
Upvote 0 Downvote
"how can i find out the results of the test?"...
if u did it as i told u, it wud give a the result if thrs anything wrong, else restart normally when its done...which means no issues...

"If this is the entire cause of my crashes i apologize for not bringing it up sooner."...
ideally ur ram arrangement shd not be a prblem...
 
Upvote 0 Downvote
bugcheck ox1a with suberror code 0x41790 is a corrupted page table.
That means the table in memory that maps between the virtual memory (pagefile.sys) and where the files are swapped into memory is corrupted.

This can be a generic memory problem but often it will be related to your SATA drivers, or a error returned by your storage.
It can also be caused by bugs in filter drivers or firmware issues even bios sleep bugs.

you might run crystaldiskinfo.exe to confirm your drives are not kicking up errors.
you might turn off the virutal memory in your system and delete your pagefile.sys. Then reboot and create virtual memory settings so the file is recreated in a different location on disk. (in case the previous one was on a bad/weak spot on the disk)

there can be other causes for this error but if memtest works I would be looking at the disk subsystem


 
Upvote 0 Downvote
Okay, so i ran memtest successfully on two of my memory sticks, that plus the fact that it wouldn't run with all three tells me my 8gb stick is most likely messed up, i'm running without it for now, going to give it a day or so to see if blue screen crashes continue, but then i will declare this as solved, if by chance i get them past that time i will make a new thread and link this one for info, thank you everyone for your help and your patience!
 
Upvote 0 Downvote


Hey so you said to reply on here if i continued having issues...

My computer just crashed but didn't show me the blue screen
but here is the information, but all my drivers are up to date according to Driver booster

Crash time: 5/11/2016 9:22:38 PM
Bug check string: IRQL_NOT_LESS_OR_EQUAL
Bug check code: 0x0000000a
Parameter 1: fffffa80`138b1010
Parameter 2: 00000000`00000002
Parameter 3: 00000000`00000001
Parameter 4: fffff800`0413e4e6
Caused by Driver: ks.sys
Caused by address: ks.sys+22bda19
 
Upvote 0 Downvote
Stop error code 0x0000000A...
This Stop error message usually occurs during installation when there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). Typically, this error occurs when a driver uses an incorrect memory address. Other possible causes of this error include an incompatible device driver, a general hardware problem, or incompatible software.

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. This is usually caused by drivers using improper addresses.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

********************************************************************
everything is referring to ur memory mate...
 
Upvote 0 Downvote
Oh im not disagreeing with you at all, just that that crash was only with the 2 4gb sticks that passed the extended mdsched tests, and so i dont know what to do anymore.

additionally, another one this morning:

Crash time: 5/11/2016 9:52:58 PM
Bug check string: BAD_POOL_HEADER
Bug check code: 0x00000019
Parameter 1: 00000000`00000003
Parameter 2: fffff8a0`12c90120
Parameter 3: 71fff8a0`12c90120
Parameter 4: fffff8a0`12c90120
Caused by Driver: serial.sys
Caused by Address: serial.sys+f0b9120
Crash Address: ntoskrnl.exe+6f400

Again, i dont know if this give you new information, just relaying what my computer tells me.
 
Upvote 0 Downvote
change the memory dump type to kernel, reboot the machine, run cmd.exe as an admin and run
verifier.exe /standard /all
reboot
then next time you get a bugcheck, put c:\windows\memory.dmp file on a server like microsoft one drive, share the file for guest access and post a link.

be sure you know how to get into safe mode (f8 or shift+f8) so you can turn off verifier functions if you system bugchecks during the boot process.

Note use
verifier.exe /reset
to turn off verifier functions after you are done testing or your machine will run slowly until you do.

send me a email if you get a memory dump. I tend to stop looking at thread after they get long and involved or are marked solved.



 
Upvote 0 Downvote
Hey sorry for the delay everyone, just super busy with work, i will follow the advised course of actions as soon as i get a chance and i will let you know, thank you again for your patients.
 
Upvote 0 Downvote
hey, so i was about to do this

"change the memory dump type to kernel,
reboot the machine,
run cmd.exe as an admin and
run verifier.exe /standard /all
reboot
then next time you get a bugcheck,
put c:\windows\memory.dmp file on a server like microsoft one drive,
share the file for guest access and post a link."

but my first issue is how do i change the memory type to kernel?
 
Upvote 0 Downvote
try https://www.sophos.com/en-us/support/knowledgebase/111474.aspx



 
Upvote 0 Downvote
Okay, well i followed the directions, i got as for as rebooting after running verifier but moments after the computer loads windows ( i dont even have to log in) the screen just has repeating horizontal stripes of blue. this is me now in safe mode :/
 
Upvote 0 Downvote
note: you can turn off verifier functions by running
verifier.exe /reset

you will want to turn them off after you are done testing or your machine will run slowly until you do.

you can put any memory dumps you have in c:\windows\minidump directory or c:\windows\memory.dmp on a server like microsoft one drive, share the files for public access and post a link.



 
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