📎 AI Summary:
The forum thread discusses a user experiencing frequent crashes and BSODs on a newly purchased laptop. After posting their error logs and seeking help, another user suggests that the issue may be caused by a driver or hardware problem, and recommends uninstalling problematic drivers and contacting the vendor due to warranty options. The original poster reports that after following these steps, the crashes have stopped for over two days, leading to gratitude and relief that their laptop is now stable. The overall sentiment is positive, with the user finding a satisfactory resolution.
M

mlkjhg

New Member
Member details
Joined
Oct 31, 2013
Messages
3
Thread Author #1
Hello,

My laptop has been crashing repeatibly since I used it on monday, I've done every scan I could find on the internet, the only change I've noticed is that it now crashes every hour instead of every thirty minutes.
I've done an analysis as mentioned on this site and here are the results.
Can anybody take a looke at this, it would realy help me to know what the cause is.

https://www.dropbox.com/s/kzqb278cxhas7v2/103013-21546-01.dmp
https://www.dropbox.com/s/dcg2vd433hf9cgz/103013-29296-01.dmp
https://www.dropbox.com/s/xswkss0dendja9u/103013-31218-01.dmp
https://www.dropbox.com/s/ovz73zeda6a4puo/103113-28750-01.dmp
https://www.dropbox.com/s/5vzzpnd4dzvo20q/103113-35062-01.dmp
https://www.dropbox.com/s/zh0u77umuy2qnsf/103113-37125-01.dmp
https://www.dropbox.com/s/gsw76z1pffzbv94/MEMORY.DMP

I realy hope somebody can help me with this sice my laptop is only two weeks old and it took all my savings.
 

Solution
Trouble
BugCheck 109, {a3a01f58936d25ab, b3b72bdee5ec5c26, ffffe00002a92a00, 1c}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Click to expand...
Code: 
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set...
Sort by date Sort by votes
Trouble

Trouble

Noob Whisperer
Member details
Joined
Nov 30, 2009
Messages
13,723
#2
BugCheck 109, {a3a01f58936d25ab, b3b72bdee5ec5c26, ffffe00002a92a00, 1c}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Click to expand...
Code: 
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f58936d25ab, Reserved
Arg2: b3b72bdee5ec5c26, Reserved
Arg3: ffffe00002a92a00, Failure type dependent information
Arg4: 000000000000001c, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification
The first thing you should probably do is remove daemon tools (sptd.sys 10/11/2009). Link Removed and grab the correct version for you architecture. Run the program and click the UNINSTALL button.
Then turn off Driver Verifier and see if Blue Screens persist. If so....
Since your computer "is only two weeks old" I would suggest contacting the vendor and make arrangements to take advantage of the system's warranty, either with a replacement or a refund.
 

Upvote 1 Downvote
Solution
M

mlkjhg

New Member
Member details
Joined
Oct 31, 2013
Messages
3
Thread Author #3
I've tried what you said and i am happy to report that my laptop hasn't crashed for over two hours, I will report it when it crashes or after 48 hours if it still hasn't crashed by then
 

Upvote 0 Downvote
M

mlkjhg

New Member
Member details
Joined
Oct 31, 2013
Messages
3
Thread Author #4
The BSOD hasn't returned.
Thanks a lot, now I can finaly use my laptop again without saving every 5 seconds
 

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