Re: Windows 8 constant BSOD

Hello friends. I am having a major problem with my bootcamp partition. I just installed windows 8 as an upgrade from windows 7 after a successful installation. However, when i booted up the partition it gives me the BSOD error almost every time i boot up. It lets you use for 2 minutes and then immediately BSOD. I cannot install bootcamp drivers because it keeps crashing. Can someone help me? I am using a mid 2010 macbook pro 13 inch. I do know that it is not officially supported but my friend managed to install on his 13 inch mid 2010 mbp as well. Thank you!

Hi
One very important point is that your Satellite L555 is not officially Win 8 supported.
What does this means?
This means that there are no Toshiba Win 8 drivers for this series.
But this does not mean that you cannot use the Win 8.
You can install the Win 8 and can use it if you purchased the Microsoft licence
Regarding the drivers:
Well you will need to search drivers at your own hand and in some cases Win 7 drivers can be installed on Win 8 system

Similar Messages

Constant BSODs MSi hd 6970

First of all sending shouts to all on this forum.
Been searching through various forums and seeking the solution.
A month ago I´ve upgraded my old 4890 to MSi HD 6970 and since then my problems have started.
I´ve found that several other MSi HD 6970 and 6*** users have this problem, albeit no solution has worked for me yet.
Gonna keep it short.
What´s the problem:
- constant BSODs / vertical stripes and crashes while playing 3d games (Bad Company 2, AC: Brotherhood) - sometimes after 10 mins of gameplay, sometimes after an hour
- no BSODs in Win 7 itself
- no BSODs during movies / videos
- no BSODs while dual monitor setup and both in use as extended (dvi Asus 24´´ and hdmi 42´´ LCD TV Samsung)
What I´ve tried:
- various drivers (original drivers supplied with the card, 11.4 to 11.8 CCC) - no change, still crashing
- sweeped the old drivers in safe mode - no change
- uninstalled the Afterburner app; from what I´ve learned it´s in conflict w/ punkbuster which is sort of mandatory for Bad Company 2
- not using ANY kind of GPU utility (except CCC)
- temps max 90 celsius in heavy load
- fan running on 35% in heavy load
My specs:
CPU: INTEL Core 2 Duo E8500 - 3,16GHz
RAM: 6GB DDR3 1333MHz PC10666 CL6-6-6-18 OCZ Reaper HPC Edition
Motherboard:INTEL DP45SG Skyberg
Sound: firewire Edirol FA-66; on-board audio disabled
VGA:MSI Radeon 6970 2PM2D2GD5
HDD: WESTERN DIGITAL Caviar Black 500GB, SATA II, WESTERN DIGITAL Caviar Green 1000GB, SATA II
PSU:TAGAN TG600-U88 600W ATX 2.2
case: Antec P182
OS:Windows 7 home premium x64
Is it PSU, MB or any other component in conflict with the GPU?
So lads, is it time for RMA?
All your help and suggestions will be much appreciated

Registered only to say: had same issues and solved it myself. I sent back the card to the vendor but they refused to do anything because according to their test softwares, the card was fine, the issue did not come up. Yet when I started playing 3D games, my card and PC froze after a few minutes.
I spent hours searching for the solution and tested all that was suggested without resolution. In the end I took it apart, cleaned the original thermal paste from and around the GPU (it was clearly a mess, spilled around the GPU and not evenly applied, plus it felt somehow very dry), then I applied a better quality paste that I previously purchased for my new CPU. I put the card back into my PC and issue gone. I used to get above 95C (especially the second GPU) just before the PC crashed, now the maximum is around 69-70 Celsius and no crash for a month (playing Guild wars2, assassins creed etc)
It is very easy to do all this, even if you are a noob like myself. I 'm not a technical person, so I looked it up all on youtube: how to take the heatsink apart, how to clean the orignal paste and how to apply new paste.
There is another issue I was also facing, with the famous atikmdag crash during games (freeze for a few seconds, then it comes back with the mesage that it has been recovered successfully) - the only workaround I found was to lower the GPU clock from 940 to 900MHz. Error disappeared completely and games are still runnig great on max graphics. It is fine for now, but I'm sure I wont buy another ATI graphic card

GTX 560 ti constant BSOD`s .. Troubling me ...

Hi guys ...
First things first, here are my system specs :
core i5 760 @2.8GHz
Asus P7P55D-E
Corsair 2X2GB RAM
MSI NGTX560ti Twin Frozr II OC Edition
CM Hyper 212+
Corsair GS600
Windows 7 64bit
I was using my XFX HD4350 for over a year now .. was running perfect .. When I upgraded my GPU about a week ago to MSI NGTX560ti Twin Frozr II OC Edition .. I am getting constant BSoD`s while playing games ... IT`s getting on my nerves ...
I tried clearing CMOS , checked all power cables, Updated to latest Drivers from nVidia (ie: 285.62), Even did a fresh install of windows .. but to no avail ...
The error on the blue screen I get is BAD POOL CALLER .. I don`t know what it means ... I`ve searched countless forums and did all the above which were recommended ...
I request forum members and senior members to help me out of this problem ...
Thank you,
vizkid2005

you can try this:
1) first, update the BIOS of your motherboard, if you have been do it this, proced with the next tip
2) upgrade bios of the VGA
3) watch the TEMPS, and if your PSU is enough for the card
4) change slot of the motherboard and test
when i buyed this card, after install the card, i updated my BIOS of the motherboard, and later the BIOS of the card.

GT70 - Constant BSoDs

Hello
I am constantly getting BSoD with my GT70. I am running Windows 8, I cleaned out the Killer Network drivers and reinstalled, I updated my nVidia drivers, and it is still unstable
I ran memory validater and there doesn't seem to be any issues with the RAM
I get BSoDs for a variety of reasons. I paid quite a handsome chunk of cash for this thingy and I'm more than a little miffed with the constant BSoD. The latest issue was a KMODE Exception but with USBPORT.sys??
I can post the logs if needed, there's a veritable horde of them.
Thanks

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
Machine Name:
Kernel base = 0xfffff801`c8c7b000 PsLoadedModuleList = 0xfffff801`c8f44a80
Debug session time: Sat Apr 12 11:28:50.542 2014 (UTC - 4:00)
System Uptime: 0 days 12:44:11.552
* Bugcheck Analysis *
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000f88, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff801c8ceb220, address which referenced memory
Debugging Details:
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff801c8fd0168
GetUlongFromAddress: unable to read from fffff801c8fd01f8
0000000000000f88 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiInsertTimerTable+90
fffff801`c8ceb220 488906 mov qword ptr [rsi],rax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: audiodg.exe
TRAP_FRAME: fffff8801add3790 -- (.trap 0xfffff8801add3790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80277cc320 rbx=0000000000000000 rcx=fffff801c8f5f520
rdx=fffffa8028e5a1a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801c8ceb220 rsp=fffff8801add3920 rbp=0000006ac1ac41bc
r8=0000006ac1ac09c6 r9=000000000000006b r10=fffff801c8c7b000
r11=fffff8801add3978 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiInsertTimerTable+0x90:
fffff801`c8ceb220 488906 mov qword ptr [rsi],rax ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff801c8cf4369 to fffff801c8cf5040
STACK_TEXT:
fffff880`1add3648 fffff801`c8cf4369 : 00000000`0000000a 00000000`00000f88 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`1add3650 fffff801`c8cf2be0 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`1add3790 : nt!KiBugCheckDispatch+0x69
fffff880`1add3790 fffff801`c8ceb220 : fffff880`1add3ab8 fffff801`c90c08f5 00000000`00140000 00000000`00000002 : nt!KiPageFault+0x260
fffff880`1add3920 fffff801`c8ce1403 : fffff880`02ee8180 ffffffff`fffb6c20 00000000`00000000 ffffffff`fffb6c20 : nt!KiInsertTimerTable+0x90
fffff880`1add3980 fffff801`c8ce197e : fffffa80`2534c740 00000000`00000001 fffff880`1add3ab8 00000000`00000000 : nt!ExpSetTimer+0x203
fffff880`1add3a60 fffff801`c8cf4053 : fffffa80`27bfc080 00000000`0000001e 00000000`00000000 fffffa80`269c4d60 : nt!NtSetTimerEx+0x10d
fffff880`1add3b00 000007fe`878c447b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000004b`f4f4f8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`878c447b
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiInsertTimerTable+90
fffff801`c8ceb220 488906 mov qword ptr [rsi],rax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiInsertTimerTable+90
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 50ecec77
FAILURE_BUCKET_ID: X64_AV_nt!KiInsertTimerTable+90
BUCKET_ID: X64_AV_nt!KiInsertTimerTable+90
Followup: MachineOwner
This was after resetting to factory defaults using Windows 8 advanced startup

Constant BSOD (Blue Screen of Death) on Windows 7 w/ Bootcamp 4

Please see below for what comes up constantly while doing work on the Windows 7 side of my iMac while running Bootcamp 4.
So here is my setup:
Brand New 27" iMac (just got it new in August 2011)
Intel core i5 2.7 Ghz
8GB RAM
AMD Radeon HD 6770M
I am running Lion latest version on Mac OS X side.
I installed Windows 7 Home Premium SP1 with Bootcamp 4.
I loaded the drivers like I am so supposed to with my Mac Disk.
When in Windows 7 Home Premium SP1, everything works fine for the most part, except sometimes it just freezes up and the BSOD pops up (see below for exact message)
It's completely random. Sometimes I can play a hardcore 3D war game or an MMO for 6 hours with no problem, sometimes I am just watching a video on youtube for a minute and it just stops.
I called Apple, they don't really care. They said to start from scratch and do a full clear and reinstall, so I did. I cleared my Bootcamp partition, then I made a new one and completeley reinstalled Windows 7 Home Premium. I have done this 4 times. I have also tried to make new disks for the updated drivers for my installation on Windows side. The problem persists.
Everything is completely updated and all the newest patches and versions are installed on both the Windows and Mac side. I am at a complete loss as to what to do with this.
I cannot update my video card from within Windows - Apple must provide the updated drivers themselves. In fact, I can update NO drivers of the iMac hardware from the Windows side.
PLEASE HELP ME!!!

If you haven't already I recommend reposting in the Boot Camp forum. That's where the Boot Camp guys tend to hang out.

New G560 crashes every few minutes windows 7 BSOD 0x00000124

We just bought the new G560 using windows 7.
The system crashed after the first 10 minutes with a BSOD;
it crashes constantly/every few minutes.
The code is 0x00000124
I see comments from others that this is a hardware conflict.
This is a laptop started crashing right away during our first moments of opening an IE browser.
There were any changes and no added software.
We have since made sure it has all the current Microsoft updates but the problem continues.
I don't find any other users of this new laptop with any postings but it looks like it has a serious problem right out of the box. No clues to be found here or in the Microsoft site.
Can anyone help- let me know if there is any more info I can add to the thread

@ tenmnd
if you have any mini dump file, please, upload
( copy the recent two or three files from c:\windows\minidump to desktop then upload somewhere on the web, like rapidshare.com )

Constant BSOD errors

I get BSOD errors fairly often. This may have started to happen after enabling
Asus Optimal power plan in BIOS, I can't tell that by looking at dump files.
Shared link to dump files: http://1drv.ms/1DCaKcG
Please tell me what's wrong and help me to fix this problem.

These are called BCC124 and are related to hardware. Read how to diagnose and hopefully to fix them in this
wiki
Since yours references "genuine Intel" I would start with a cpu stress test
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\zigza\Desktop\041415-21312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff802`22c1a000 PsLoadedModuleList = 0xfffff802`22ef3250
Debug session time: Tue Apr 14 14:27:53.505 2015 (UTC - 4:00)
System Uptime: 0 days 3:51:33.144
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffffe001cc1f1028, bf800000, 124}
Probably caused by : GenuineIntel
Followup: MachineOwner
2: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe001cc1f1028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: SpecOpsTheLine
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:
ffffd000`5256edf8 fffff802`233e5213 : 00000000`00000124 00000000`00000000 ffffe001`cc1f1028 00000000`bf800000 : nt!KeBugCheckEx
ffffd000`5256ee00 fffff802`22de05a9 : 00000000`00000001 ffffe001`c16af310 ffffe001`c16af310 ffffe001`cc1f1028 : hal!HalBugCheckSystem+0xcf
ffffd000`5256ee40 fffff802`233e56a0 : 00000000`00000728 00000000`00000002 ffffd000`5256f230 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`5256eea0 fffff802`233e5a0d : ffffe001`00000010 ffffe001`c16af310 ffffd000`5256f048 ffffe001`c16af310 : hal!HalpMcaReportError+0x50
ffffd000`5256eff0 fffff802`233e58f8 : ffffe001`c16aeca0 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`5256f040 fffff802`233e5b42 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`5256f080 fffff802`233e5ccf : ffffe001`c16aeca0 ffffd000`5256f2b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`5256f0b0 fffff802`22d754bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`5256f0e0 fffff802`22d75271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`5256f220 fffff800`eb9d133f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd000`24731870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x3bf
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache
FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

Help with constant BSOD

I keep getting BSOD. At first I had windows vista installed, I tried updating everything, bios, memory drivers, graphics drivers, again still BSOD. I downgrading to windows XP(because of this and other reasons). I still get BSOD.
The messages associated with it are:
1)no message given
2)memory_management
3)irql_not_less_or_equal
I have the Lenovo T61p.
Any assistance would be greatly appreciated.

Hello David,
The Sequence setting needs to match the video and audio of the incoming files. When this occurs correctly rendering is minimized.
Sequence settings are selected by choosing the correct _Easy Setup_ before the material is edited to the Timeline.
Note: The Material has to match the Sequence settings not the other way round. FCE works with fixed formats.
If you provide details of the footage you are working with and how they arrived into FCE, we may be able to help.
Al

Apple Radeon HD5770 Crossfire on Windows 7 BSOD

So many users who bought two Apple Radeon HD 5770's video cards can't use Crossfire under Windows.
Crossfire works perfectly on very old Catalyst 10.11 drivers. All newer drivers doesn't work causing BSOD error just after clicking Enable Crossfire.
More details: http://forums.amd.com/game/messageview.cfm?catid=262&threadid=155342&forumid=11
Please fix it.

You think we the end users - there is NO ONE from Apple here.
That is Windows issue. Buy / build a PC.

Windows 7 BSOD randomly occuring after installing iTunes 10.6 with iPhone 4 in dock

After installing iTunes 10.6 and IOS 5.1 on my iPhone 4, Windows 7 computer was randomly blue screening with the iPhone 4 in the attached dock. After removing the phone from the dock, system works fine.

Re-installed iTunes as you suggested and it worked. However, started experiencing random BSOD's. Disk check found a number of file errors on the boot drive - which it fixed. It then took a number of re-boots before computer became stable.
Then, upgraded iTunes on a HP workstation (no iPhone attached). On reboot windows had to attempt a boot repair 3 times before it would reboot. Couldn't even do a disk check without first reverting to the last restore point. It also corrupted Norton. The end result was 2.5 hours of wasted time.
Being an expert pc user, I can safely say that I believe Apple has some serious issues with 10.6.

Constant BSOD, Can't seem to fix

My board crashed so I replaced it and my memory with an MSI 970A-G46. My RAM is running in dual channel with 8GB on each side. I reinstalled Win 64 bit and it started crashing almost immediately. It would run for a few hours but then crash.
It only crashes while browsing the internet. I use Firefox and thought maybe it was my browser. I tried Chrome though with the same effect.   My Video Card is a GEForce 460. Finally I decided to try a new hard drive and reinstall Windows
again. This time it worked a few days and started to crash again. Same issue, only when browsing. I have tried updating every driver I have to no effect. Windows update tried to install a new service pack yesterday but that took forever and
got rolled back because of an error. Basically the only hardware I have left is the Power Supply, processor and video card. I keep my processor fan and heatsink clean, I have tried a different video card with the same issue so I really don't think
it is my hardware.
My last crash brought this up in Event Vewer:Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          2/20/2014 10:24:53 AM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HOME-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000102, 0x0000000000000002, 0x0000000000000001, 0xfffffa800e2722e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 022014-26988-01.
Event Xml:
<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="2014-02-20T16:24:53.000000000Z" />
    <EventRecordID>17716</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>HOME-PC</Computer>
    <Security />
</System>
<EventData>
    <Data Name="param1">0x000000d1 (0x0000000000000102, 0x0000000000000002, 0x0000000000000001, 0xfffffa800e2722e0)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">022014-26988-01</Data>
</EventData>
</Event>
As well as this message from the previous BSOD
Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          2/20/2014 10:49:45 AM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HOME-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 022014-27565-01.
Event Xml:
<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="2014-02-20T16:49:45.000000000Z" />
    <EventRecordID>17829</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>HOME-PC</Computer>
    <Security />
</System>
<EventData>
    <Data Name="param1">0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">022014-27565-01</Data>
</EventData>
</Event>

Hi,
I have checked with the dmp files uploaded.
Most of them showed that there are some hardware issues with BugCHeck ID 1E and 3B. (25412,14414,24242,21964,22885,28095, 18688, 20576, 18064.)
Only two of them(19125,19671) indicate that your AMD processor failure error with BugCheck ID 124.
See: Dump file:
Dump file 19125:
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800dae6028, b66b4000, 135}
Probably caused by : AuthenticAMD
Followup: MachineOwner
2: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800dae6028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b66b4000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_AuthenticAMD
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: FlashPlayerPlu
CURRENT_IRQL: f
STACK_TEXT:
fffff880`02f6ca88 fffff800`0301e903 : 00000000`00000124 00000000`00000000 fffffa80`0dae6028 00000000`b66b4000 : nt!KeBugCheckEx [d:\win7_gdr\minkernel\ntos\ke\amd64\procstat.asm @ 177]
fffff880`02f6ca90 fffff800`031da543 : 00000000`00000001 fffffa80`0de98ea0 00000000`00000000 fffffa80`0de98ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6cad0 fffff800`0301e5c8 : 00000000`00000728 fffffa80`0de98ea0 fffff880`02f6ce30 00000000`098f8b00 : nt!WheaReportHwError+0x263 [d:\win7_gdr\minkernel\ntos\whea\whea.c @ 773]
fffff880`02f6cb30 fffff800`0301df1a : fffffa80`0de98ea0 fffff880`02f6ce30 fffffa80`0de98ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6cc80 fffff800`03011e8f : 00000000`00000097 00000000`00000001 fffff880`02f6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6ccc0 fffff800`030c312c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02f6ccf0 fffff800`030c2f93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c [d:\win7_gdr\minkernel\ntos\ke\amd64\trap.asm @ 1322]
fffff880`02f6ce30 00000000`6c40e2e1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 [d:\win7_gdr\minkernel\ntos\ke\amd64\trap.asm @ 1282]
00000000`042df810 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6c40e2e1
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
Followup: MachineOwner
Dump file 19671:
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800de0e028, b669c000, 135}
Probably caused by : AuthenticAMD
Followup: MachineOwner
2: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800de0e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b669c000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_AuthenticAMD
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: f
STACK_TEXT:
fffff880`02d6ca88 fffff800`03601903 : 00000000`00000124 00000000`00000000 fffffa80`0de0e028 00000000`b669c000 : nt!KeBugCheckEx [d:\win7_gdr\minkernel\ntos\ke\amd64\procstat.asm @ 177]
fffff880`02d6ca90 fffff800`0319a543 : 00000000`00000001 fffffa80`0c710010 00000000`00000000 fffffa80`0c710060 : hal!HalBugCheckSystem+0x1e3
fffff880`02d6cad0 fffff800`036015c8 : 00000000`00000728 fffffa80`0c710010 fffff880`02d6ce30 00000000`00000000 : nt!WheaReportHwError+0x263 [d:\win7_gdr\minkernel\ntos\whea\whea.c @ 773]
fffff880`02d6cb30 fffff800`03600f1a : fffffa80`0c710010 fffff880`02d6ce30 fffffa80`0c710010 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02d6cc80 fffff800`035f4e8f : fffff900`c2ad6490 00000000`00000001 fffff880`02d6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02d6ccc0 fffff800`0308312c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02d6ccf0 fffff800`03082f93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c [d:\win7_gdr\minkernel\ntos\ke\amd64\trap.asm @ 1322]
fffff880`02d6ce30 fffff960`001ab04a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 [d:\win7_gdr\minkernel\ntos\ke\amd64\trap.asm @ 1282]
fffff880`089f9910 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff960`001ab04a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD__UNKNOWN
BUCKET_ID: X64_0x124_AuthenticAMD__UNKNOWN
Followup: MachineOwner
The other dump files showed the reason for BSOD is probably caused by some system files like dxgkrnl.sys, ntfs.sys and win32K.sys, which I think is related with(or caused by) the hardware failure.
For BugCheck information, please see:
Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR
Hope this might help
Best regards
Michael Shao
TechNet Community Support

New Computer, Windows 7 BSOD

Hey there,
Thanks so much for taking the time to help me!
To give you the short story, I recently built my first computer (with the help of an experienced friend). It was a lot of fun and the computer ran great the first day!
However, on the second day when I went to boot up, I got a BOOTMGR not found error. I eventually worked my way around this by reinstalling Windows 7 on my SSD. My problem now is that I am plagued
with BSOD now.
I can not install any new programs without the BSOD coming up.
I also cannot even update Windows as that causes a cruel cycles of BSODs.
The only thing I can do is get on the internet and browse the web.
I've included here the Dump File as well as a picture of the BSOD.
BSOD picture: i.imgur.com/M5bHsGl.jpg
Dump File: mediafire.com/?3e72czvkakx8zja
I really hope you guys can help me! Thanks!!!

Ahijaouy
This was related to Hardware and hints at Genuine Intel. It is called a BCC124
Stop 0x124 is a hardware error
If you are overclocking try resetting
your processor to standard settings and see if that helps.
If you continue to get BSODs here are some more things you may want to consider.
This
is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).
Stop 0x124 - what it means and what to try
Synopsis:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond
its design specifications - by overclocking - can malfunction in unpredictable ways.
2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece
of hardware.
It is good practice to run the latest drivers anyway.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
Their website should provide detailed instructions as to the brand and model-specific procedure.
5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought
otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
free from defects - only that none were encountered during the test passes.
7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the
OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine
is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential
which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
Should
you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's
hardware.
More
advanced reading can be found here from a MS MVP IT PRO
http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e58e90
Debug session time: Wed Apr 9 20:40:34.697 2014 (UTC - 4:00)
System Uptime: 0 days 0:02:07.884
Loading Kernel Symbols
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
Loading unloaded module list
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8010ce9028, bf800000, 124}
Page 3c8c0a not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : GenuineIntel
Followup: MachineOwner
16.1: kd:x86> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8010ce9028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
Page 3c8c0a not present in the dump file. Type ".hh dbgerr004" for details
BUGCHECK_STR: 0x124_GenuineIntel
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x0
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_cache
FAILURE_ID_HASH: {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

Windows 7 BSOD Problem

Hi
Since yesterday, im having some BSOD's, with this content:
SYSTEM_SERVICE_EXCEPTION (3b)An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000196373, Address of the instruction which caused the bugcheck
Arg3: fffff8800553a030, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
win32k!HmgLockEx+a3
fffff960`00196373 0fb7430c movzx eax,word ptr [rbx+0Ch]
CONTEXT: fffff8800553a030 -- (.cxr 0xfffff8800553a030)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa80096a3060
rdx=fffff900c0200000 rsi=0000000002e00000 rdi=fffff900c0200000
rip=fffff96000196373 rsp=fffff8800553aa00 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff8800553aa68 r12=000000000736ff00 r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!HmgLockEx+0xa3:
fffff960`00196373 0fb7430c movzx eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff960003525c0 to fffff96000196373
STACK_TEXT:
fffff880`0553aa00 fffff960`003525c0 : fffff900`c3ee5c00 00000000`00000001 00000000`5912213a fffff900`c2864a40 : win32k!HmgLockEx+0xa3
fffff880`0553aa70 fffff960`00351abe : fffff900`c3ee5c00 00000000`00000000 0000213a`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`0553aaa0 fffff960`003529c3 : 00000000`00000000 00000000`5912213a fffff900`c3ee5c00 00000000`0736ff4c : win32k!SFMLOGICALSURFACE:eInitialize+0x4e
fffff880`0553aae0 fffff960`002af13b : 00000000`00000000 fffff900`c00bf010 fffff900`c3ee5c00 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`0553ab20 fffff960`002d0670 : 00000000`00000001 00000000`00000001 fffff880`0553ac60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`0553ab60 fffff800`03273a93 : 00000000`052818e0 fffff880`0553ac60 00000000`052818b0 00000000`0736ff4c : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`0553abe0 000007fe`fdaf4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0372f478 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdaf4efa
FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`00196373 0fb7430c movzx eax,word ptr [rbx+0Ch]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!HmgLockEx+a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 50e64aeb
STACK_COMMAND: .cxr 0xfffff8800553a030 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3
BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3
Some solution to this problem?

Santy
This was related to dtsoftbus01.sys which is part of your virtual drive software (either Alcohol120 or Daemon tools, etc) I would remove it and replace with the following.
ALSO AND IMPORTANT. You need to update to SP-1 ASAP as there are many bugfixes that you need.
Service pack 1 Update.
http://windows.microsoft.com/installwindows7sp1
Learn how to install Windows 7 Service Pack 1 (SP1)
http://windows.microsoft.com/en-US/windows7/learn-how-to-install-windows-7-service-pack-1-sp1
Additional Resources:
http://windows.microsoft.com/en-US/windows7/uninstall-sp1
http://windows.microsoft.com/troubleshootwindows7sp1
Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.
They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.
Use this SPTD uninstaller DuplexSecure
http://www.duplexsecure.com/downloads
when you're done you can use this Freeware:
MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place
http://www.magiciso.com/download.htm
Don't forget to turn off verifier by typing verifier /reset from an elevated command prompt
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )
Debugging Details:
BUGCHECK_STR: 0xc9_23e
DRIVER_VERIFIER_IO_VIOLATION_TYPE: 23e
FAULTING_IP:
dtsoftbus01+1324
fffff880`01bae324 4053 push rbx
FOLLOWUP_IP:
dtsoftbus01+1324
fffff880`01bae324 4053 push rbx
IRP_ADDRESS: fffff9800b454e10
DEVICE_OBJECT: fffffa8009181260
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff800036fe3dc to fffff80003275840
STACK_TEXT:
fffff880`033b5768 fffff800`036fe3dc : 00000000`000000c9 00000000`0000023e fffff880`01bae324 fffff980`0b454e10 : nt!KeBugCheckEx
fffff880`033b5770 fffff800`0370847a : fffff800`036fc9f0 fffff880`01bae324 fffff980`0b454e10 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`033b57b0 fffff800`0370934e : 00000000`0000023e 00000000`00000000 fffff980`0b454e10 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`033b5800 fffff800`0371471f : fffffa80`09390250 fffffa80`08ffe6a0 fffffa80`08ffe758 fffff880`01bb2228 : nt!VfErrorReport6+0x6e
fffff880`033b58d0 fffff800`03714b63 : fffffa80`08ffe6a0 00000000`00000002 fffffa80`09181260 fffff880`01bae3f4 : nt!IovpCallDriver2+0x13f
fffff880`033b5930 fffff800`0371ac2e : fffff980`0b454e10 fffff980`0b454e10 00000000`00000002 fffffa80`09181260 : nt!VfAfterCallDriver+0x353
fffff880`033b5980 fffff800`03719c42 : fffff980`0b454ee0 00000000`00000002 fffffa80`0938d550 fffffa80`08ffe6a0 : nt!IovCallDriver+0x57e
fffff880`033b59e0 fffff800`0371ac16 : fffff980`0b454e10 00000000`00000002 fffffa80`0938d400 fffff800`037163f5 : nt!ViFilterDispatchGeneric+0x62
fffff880`033b5a10 fffff880`010e05dd : fffff980`0b454f28 fffffa80`0939b180 fffff980`0b454e10 fffffa80`092a9850 : nt!IovCallDriver+0x566
fffff880`033b5a70 fffff980`0b454f28 : fffffa80`0939b180 fffff980`0b454e10 fffffa80`092a9850 fffffa80`00000020 : PxHlpa64+0x35dd
fffff880`033b5a78 fffffa80`0939b180 : fffff980`0b454e10 fffffa80`092a9850 fffffa80`00000020 fffffa80`00000001 : 0xfffff980`0b454f28
fffff880`033b5a80 fffff980`0b454e10 : fffffa80`092a9850 fffffa80`00000020 fffffa80`00000001 fffffa80`00000000 : 0xfffffa80`0939b180
fffff880`033b5a88 fffffa80`092a9850 : fffffa80`00000020 fffffa80`00000001 fffffa80`00000000 00000000`00000000 : 0xfffff980`0b454e10
fffff880`033b5a90 fffffa80`00000020 : fffffa80`00000001 fffffa80`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`092a9850
fffff880`033b5a98 fffffa80`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffff880`033b5ce0 : 0xfffffa80`00000020
fffff880`033b5aa0 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffff880`033b5ce0 00000000`00000000 : 0xfffffa80`00000001
fffff880`033b5aa8 00000000`00000000 : 00000000`00000000 fffff880`033b5ce0 00000000`00000000 fffffa80`08c43650 : 0xfffffa80`00000000
STACK_COMMAND: .bugcheck ; kb
SYMBOL_NAME: dtsoftbus01+1324
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dtsoftbus01
IMAGE_NAME: dtsoftbus01.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f10358a
FAILURE_BUCKET_ID: X64_0xc9_23e_VRF_dtsoftbus01+1324
BUCKET_ID: X64_0xc9_23e_VRF_dtsoftbus01+1324
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xc9_23e_vrf_dtsoftbus01+1324
FAILURE_ID_HASH: {a4b0905c-b00f-9d8a-8c18-eafbbc358648}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

To anyone getting windows freezing,BSOD etc

This is not a solution to everyones problems. However it has fixed mine and many other probelms with freezing/lockups in windows. It is called SP2. Dont install it and if you have either roll back or do re-install of XP with SP1.
Obviously this wont help you if its your PSU or mem thats the problem but it is worth a try. I no longer get any lockups ever.

Quote
Originally posted by Paul Foster
I'm usually one of the first people to badmouth Microsoft so I am far from being a sheep who is happy to give even more money for software that typically has even more bugs. I ran W2K on my previous PC and never saw the need to upgrade to XP. However it does seem to be very stable and I have yet to run into any serious problems where I can point my finger at XP much less SP2.
If you experience a lot of BSODs and other problems I still think you probably have a bad driver but you might have some sort of hardware problem. Can you run Prime95 for an extended period without it failing?
Yeah Dacull nice one mate I found the patch before I got rid of SP2.
Paul not sure if you aimed the Q at me but yeah Prime95 had been running in the backround for 24 hours+ one of the times the comp suddenly froze. No SP2 and hey presto no freezes. So yup I always make sure every config is 100% prime95 stable at both tortures and the blend test.

Pavilion G6: Windows 10 BSOD Error

Once I upgraded my laptop to Windows 10 (64-bit) whenever I would put my laptop to sleep or close the lid and come back to it, it would come back on but immediately be frozen and it would not respond. After a couple of seconds a blue screen of death with a frowny face would pop up. It usually gives me the error code of: UNEXPECTED_STORE_EXCEPTION Then when I would come and start my laptop from being off sometime it will give me a BSOD right at the beginning and it would have error code, CRITICAL_PROCESS_DIED Is there anyway to fix this? I would very much enjoy being able to have windows 10 on my laptop. Given the amount of BSOD I have had I went back to Windows 7 until a solution can be found. Sidenote: I also had a similar problem with windows 8, it did the same exact thing as Windows 10 did. It just gave me a different error code: KERNAL_DATA_INPAGE_ERROR. I went back to Windows 7 on that situation as well. Any help to fix this would be great! Thanks in advance.

Install windows 10 again this time choose Not to save any data or system settings. Back up important data first.

Re: Windows 8 constant BSOD

Similar Messages

Maybe you are looking for