What the BSOD stop codes?
I can't open ur attached file
I can't open ur attached file
-
Please click the link below for your operating system to download the TSG SysInfo Utility. Click on "Save File" then double-click the file to run it. Copy and paste the report in your initial post. Windows 7 and later (downloads a file named tsginfo.exe) | Windows XP (downloads a file named SysInfo.exe)
Needs some advanced help!
Hello, I'm new to this forum btw.
So first of all, I've buit a modest Gaming PC for one of my friends. It was a lot of fun building this PC for a friend, And it all looked neat when everything was assembled. Thee are the specs:
--------------------------------------------------
- ASRock 970 Pro3 R2.0 - (Motherboard)
--------------------------------------------------
- AMD FX 9590 Black Edition - (CPU)
- Cooler Master Hyper 212 Evo - (CPU Cooler)
--------------------------------------------------
- Kingston HyperX FURY Red Series - 2 x 8 Gb - 1600 Mhz (RAM)
--------------------------------------------------
- MSI GTX 770 Gaming - (GPU)
--------------------------------------------------
- GOODRAM CX100 - 240 Gb - (SSD - OS)
- Seagate Barracuda ST1000DM003 - 1 TB - (HDD)
--------------------------------------------------
- Cooler Master B700 ver.2 - (PSU)
--------------------------------------------------
So, Now it was time to test this mean little machine.
Windows 7 - 64bit Started perfectly, and everything worked quickly thanks to the SSD.
Now after downloading some games from steam, we wanted to see what this thing could do. And so we went to test the fella. We were able to start Rust, and play it on max settings like we expected. But after playing for about 2 hours, the computer popped up with a BSOD.
Now we were kinda sad, obviously thinking it could be thanks to faulty memory. So, we turned off the machine. Unplugged it from the power source, And went to test the memory. We ran Memtest86, but it returned with no errors. It all worked perfectly fine.
After testing that, we ran the tools to check out the HDD for corrupted tiles and whatsoever, Both the SSD and HDD also returned with no errors of any kind.
Next thing we tried was seeing if the Cooler was able to keep the CPU cool at any given circumstance to rule the BSOD was caused by an overheting CPU. We ran Prime95, and monitored the Temp of CPU with HWmonitor active in the background. From the information HWmonitor gave us, the CPU was not getting much hotter then 55 Degrees. And that under heavy load seems good to me.
Next thing we tried, was replacing the PSU. We tried replacing it with a PSU that had an higher amount of Watts. So we replaced the 700 Watts, with a modulair PSU that delivered 850 Watts.Now both were Bronze 80+ PSU's So we did expect some loss of Watts like usual. We thought that the 700 Watts under heavy loss might be the cause of the BSOD, maybe it could be that the PS was not preforming good enough to handle the PC under heavy load? Well guess what. It was not the case. The PC still gave the BSOD's like it just didn't care for the PSU.
Now as you can see, I've pretty much tried everything to check where to BSOD's might came from. Atleast I'm kinda with my hands in my hair at this point.
So I tried to track down some of the BSOD's data, and tried to make sense of the messages. I googled up some of the BSOD error codes, and some people stated that it was the cause of faulty drivers. Now that's like searching for a needle in a haystack. Try to find that driver lol. But I have updated everything there was to be done, and yet it continued to give the BSOD's
My question was:
Are any of you able to assist me in this problem? I could really use some help.
I've got a link here which leads to a file that has stored all the information about the different BSODs the computer is experiencing. Can you make some sense of the problem?
OneDrive link:
https://onedrive.live.com/redir?resid=35D65A885F7A2CD3!2342&authkey=!AG7DfOg5YjKYexw&ithint=file,evtx
You can open this file, which leads to Event Viewer and displays the exact errors that I've exported from his Event Viewer.
---------------------------
Edit:
I should state that whenever the PC is in Power saving mode, It does not give any errors or BSODs. However, If we switch the PC to High Performance, or Balanced mode, It does give an BSOD in about an hour after changing the scheme.
Thought you guys should know this little fact.
So first of all, I've buit a modest Gaming PC for one of my friends. It was a lot of fun building this PC for a friend, And it all looked neat when everything was assembled. Thee are the specs:
--------------------------------------------------
- ASRock 970 Pro3 R2.0 - (Motherboard)
--------------------------------------------------
- AMD FX 9590 Black Edition - (CPU)
- Cooler Master Hyper 212 Evo - (CPU Cooler)
--------------------------------------------------
- Kingston HyperX FURY Red Series - 2 x 8 Gb - 1600 Mhz (RAM)
--------------------------------------------------
- MSI GTX 770 Gaming - (GPU)
--------------------------------------------------
- GOODRAM CX100 - 240 Gb - (SSD - OS)
- Seagate Barracuda ST1000DM003 - 1 TB - (HDD)
--------------------------------------------------
- Cooler Master B700 ver.2 - (PSU)
--------------------------------------------------
So, Now it was time to test this mean little machine.
Windows 7 - 64bit Started perfectly, and everything worked quickly thanks to the SSD.
Now after downloading some games from steam, we wanted to see what this thing could do. And so we went to test the fella. We were able to start Rust, and play it on max settings like we expected. But after playing for about 2 hours, the computer popped up with a BSOD.
Now we were kinda sad, obviously thinking it could be thanks to faulty memory. So, we turned off the machine. Unplugged it from the power source, And went to test the memory. We ran Memtest86, but it returned with no errors. It all worked perfectly fine.
After testing that, we ran the tools to check out the HDD for corrupted tiles and whatsoever, Both the SSD and HDD also returned with no errors of any kind.
Next thing we tried was seeing if the Cooler was able to keep the CPU cool at any given circumstance to rule the BSOD was caused by an overheting CPU. We ran Prime95, and monitored the Temp of CPU with HWmonitor active in the background. From the information HWmonitor gave us, the CPU was not getting much hotter then 55 Degrees. And that under heavy load seems good to me.
Next thing we tried, was replacing the PSU. We tried replacing it with a PSU that had an higher amount of Watts. So we replaced the 700 Watts, with a modulair PSU that delivered 850 Watts.Now both were Bronze 80+ PSU's So we did expect some loss of Watts like usual. We thought that the 700 Watts under heavy loss might be the cause of the BSOD, maybe it could be that the PS was not preforming good enough to handle the PC under heavy load? Well guess what. It was not the case. The PC still gave the BSOD's like it just didn't care for the PSU.
Now as you can see, I've pretty much tried everything to check where to BSOD's might came from. Atleast I'm kinda with my hands in my hair at this point.
So I tried to track down some of the BSOD's data, and tried to make sense of the messages. I googled up some of the BSOD error codes, and some people stated that it was the cause of faulty drivers. Now that's like searching for a needle in a haystack. Try to find that driver lol. But I have updated everything there was to be done, and yet it continued to give the BSOD's
My question was:
Are any of you able to assist me in this problem? I could really use some help.
I've got a link here which leads to a file that has stored all the information about the different BSODs the computer is experiencing. Can you make some sense of the problem?
OneDrive link:
https://onedrive.live.com/redir?resid=35D65A885F7A2CD3!2342&authkey=!AG7DfOg5YjKYexw&ithint=file,evtx
You can open this file, which leads to Event Viewer and displays the exact errors that I've exported from his Event Viewer.
---------------------------
Edit:
I should state that whenever the PC is in Power saving mode, It does not give any errors or BSODs. However, If we switch the PC to High Performance, or Balanced mode, It does give an BSOD in about an hour after changing the scheme.
Thought you guys should know this little fact.
- Status
- Not open for further replies.
1 - 20 of 22 Posts
0x0101What the BSOD stop codes?
I can't open ur attached file
0x01a
0x01e
and another one, i will post a more detailed report when i get back home from work.
Are there any file names listed with the STOP codes? If so which file names with which codes?
I do have an XML Report for ya if you mean this.:Are there any file names listed with the STOP codes? If so which file names with which codes?
0x0101
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-12-05T12:31:33.000000000Z" />
<EventRecordID>11107</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>KVN-PC</Computer>
<Security />
</System>
- <EventData>
0x00000101 (0x0000000000000019, 0x0000000000000000, 0xfffff88002f65180, 0x0000000000000002)
C:\Windows\MEMORY.DMP
120515-19203-01
</EventData>
</Event>
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-12-05T12:31:33.000000000Z" />
<EventRecordID>11107</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>KVN-PC</Computer>
<Security />
</System>
- <EventData>
0x00000101 (0x0000000000000019, 0x0000000000000000, 0xfffff88002f65180, 0x0000000000000002)
C:\Windows\MEMORY.DMP
120515-19203-01
</EventData>
</Event>
oxo1a
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-11-27T20:49:02.000000000Z" />
<EventRecordID>9079</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>KVN-PC</Computer>
<Security />
</System>
- <EventData>
0x0000001a (0x0000000000000403, 0xfffff680001ed2e0, 0xafb00002a478f867, 0xfffff680001ed2e8)
C:\Windows\MEMORY.DMP
112715-8361-01
</EventData>
</Event>
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-11-27T20:49:02.000000000Z" />
<EventRecordID>9079</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>KVN-PC</Computer>
<Security />
</System>
- <EventData>
0x0000001a (0x0000000000000403, 0xfffff680001ed2e0, 0xafb00002a478f867, 0xfffff680001ed2e8)
C:\Windows\MEMORY.DMP
112715-8361-01
</EventData>
</Event>
0x01e
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-10-28T19:27:03.000000000Z" />
<EventRecordID>2834</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>KVN-PC</Computer>
<Security />
</System>
- <EventData>
0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)
C:\Windows\MEMORY.DMP
102815-10998-01
</EventData>
</Event>
- <System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-10-28T19:27:03.000000000Z" />
<EventRecordID>2834</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>KVN-PC</Computer>
<Security />
</System>
- <EventData>
0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)
C:\Windows\MEMORY.DMP
102815-10998-01
</EventData>
</Event>
Yes Ty.....give me a few minutes to look it over
First points to possibly outdated/faulty directx software.
Update to current version and see if it helps.
Second points to faulty RAM. Pull out all your rams and then put ONE IN AT A TIME and fun memtest again for a minimum of 4 passes. Do this test for each stick , doing so one stick at a time.
Third also points to memory issues.
I would update directx to its most recent version and the run memtest on all of your RAM as stated above. If tests come back OK we can proceed to another avenue.
Update to current version and see if it helps.
Second points to faulty RAM. Pull out all your rams and then put ONE IN AT A TIME and fun memtest again for a minimum of 4 passes. Do this test for each stick , doing so one stick at a time.
Third also points to memory issues.
I would update directx to its most recent version and the run memtest on all of your RAM as stated above. If tests come back OK we can proceed to another avenue.
Alright, I will try to test the RAM again. However we have tried to check the RAM for errors already. Might have done it wrong, or not long enough though.
The funny thing however is, when the PC is in power saving mode, None of these BSODs ever show up. It works all fine in power saving mode. As soon as we set it to balanced, or high performance, the PC will lock up after around 30 minutes - 2 hours. It completly random.
So as you can guess, I don't relly think this would be a RAM problem. But we will try the test again tonight.
The funny thing however is, when the PC is in power saving mode, None of these BSODs ever show up. It works all fine in power saving mode. As soon as we set it to balanced, or high performance, the PC will lock up after around 30 minutes - 2 hours. It completly random.
So as you can guess, I don't relly think this would be a RAM problem. But we will try the test again tonight.
I'm kind of not thinking RAM either BUT we have to test it properly to be sure. Yes in order to get a good accurate test on RAM normally you should let it run 7-10 passes on one stick at a time, but I normally have done 4-5 and been OK.
Gonna test the modules in half an hour. so stay tuned for the results ^^
I'll be available periodically throughout my day 
Awesome, thanks for replying so quickly btw. you don't see that very often hehe!
I'm unemployed unfortunately for right now so I'm on here quite often. Keeps my brain working and kills time! Haha
Well, Here I am with the results.
Seemed like the memory was just fine. Tested it with memtest86, and even replaced my own RAM with my Friends RAM and the problems still persisted on his PC, so I guess we can check that one off.
Seemed like the memory was just fine. Tested it with memtest86, and even replaced my own RAM with my Friends RAM and the problems still persisted on his PC, so I guess we can check that one off.
So you tested your RAM in his machine and you still got BSODs In his machine??
Yes I did, And that was the outcome yeah.
It would seem then your RAM is faulty.
But it issn't. I've been using my RAM for 3 years now with my own setup without a problem. And his RAM module also worked fine when I installed them in my PC
Well u have 3 different BSODs. 2 outta 3 point to memory. So I would say its time to look into testing the memory or even replacing it. When memory dies, it does just that no warning
Well that's the thing. I am really sure it is not the memory. I've tested this completely and I can assure you that it's not the memory. I've tested his RAM modules in my setup and I state: There were no errors in this testing phase. I can even film it for ya if you want to haha. But that will take some while to watch ;p
1 - 20 of 22 Posts
- Status
- Not open for further replies.
Tech Support Guy
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!
Full Forum Listing
Explore Our Forums
