BSOD...Please Help! Thanks.

M

mignoncharly

Active member
Joined
Dec 25, 2013
Posts
27
Location
France
Hi,
i can't write english as well but i'll try to explain my problem. At first thank you for this forum and the possibility to receive solutions we need.
i have done all steps and landed here to attach and send the file.


Microsoft Windows 8 (6.2) 64-bit (Build 9200)
Original installed OS was Win 8 (USA)
OEM version
System's age: i think 2years
I have re-installed the OS Win 8 German version--- since 6 Months
CPU: AMD A6-4400M
Video Card: AMD Radeon HD 7520G
System Manufacturer: Samsung
Model: NP365E5C-SO5US

thank for your help.
best regards

mignoncharly
 

Attachments

  • CPU.jpg
    CPU.jpg
    19.3 KB · Views: 1
Hi,

The crashes were caused by different bug checks, but the underlying problem of all of them seems to be a memory corruption. For example, the following lines in one of the minidumps clearly indicates that memory got corrupted (0000000000000003 cannot be a valid memory address):

Code: 
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: [B]0000000000000003[/B], memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: [B]0000000000000003[/B], address which referenced memory

In most cases (but not always), this is caused by:

  • Some buggy driver
  • Faulty RAM
First, I would like you to enable Driver Verifier, as described in this guide. Once enabled, please wait for the system to crash at least few times, so we could see if we can see some specific driver is indicated as a cause in all of these dumps. In case it isn't, we will need you to run a memory test, to see if there's no issues with the RAM modules.
 
Hi TomasD,
thank for your response. i have tried for 3 hrs to enable Driver Verifier but i got some difficulties (i'll try again)... but i also used a software to enumerate all crashes (with details) , the problem is i don't know how to post the report here!
 
mignoncharly said:
Hi TomasD,
thank for your response. i have tried for 3 hrs to enable Driver Verifier but i got some difficulties (i'll try again)... but i also used a software to enumerate all crashes (with details) , the problem is i don't know how to post the report here!
Click to expand...

Do you mean Sysnative jcgriff2 BSOD File Collection app software? If so, the report you attached on your first post is OK and everything is OK with that. Anyhow, I need you to enable driver verifier, wait for new crashes and attach new report.

What kind of issues are you having with Driver Verifier that you cannot enable it?
 
mignoncharly said:
ok, concerning the selection to do (as i already ran Driver Verifier) i dont have the same choices/propositions.
Click to expand...

OK, let's try again:

  1. Run Driver Verifier
  2. Select Create Standard Settings
  3. Select Select driver names from a list
  4. Click on Provider column to sort drivers by provider
  5. Mark all drivers where Provider is NOT Microsoft Corporation
  6. Click Finish
  7. Reboot the computer
 
Cool...done, but while rebooting i got bsod twice: driver_verifier_IONMANAGER_VIOLATION
And now windows proposes me an automatic reparation (windows can't load)
I have 2 choices: restore or abort. Thks
 
Well, the best option would be to get booted to Safe Mode and disabling driver verifier (selecting Delete existing settings option). Anyhow, if there's no such option, feel free to do a restore to the point you created before enabling Driver Verifier. What I'm afraid of is it can remove minidump files too, so we will be back to square one.
 
Sorry but when you say "to get booted in safe mode" you mean i should work at the biginning in this mode?? (Sorry for this kind of question ;) ) i think i'm confused.
 
mignoncharly said:
Sorry but when you say "to get booted in safe mode" you mean i should work at the biginning in this mode?? (Sorry for this kind of question ;) ) i think i'm confused.
Click to expand...

Yes, Safe Mode should work (Driver Verifier shouldn't be active in Safe Mode).
 
Thanks.

I see that the bugcheck in 122613-66050-01.dmp occurred due to Driver Verifier (this is what we wanted), 30 seconds after the system was started (as you said, Windows crashed during boot):

Code: 
Verify Flags Level 0x000209bb

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [X] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [X] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks
    [X] (0x00020000) DDI compliance checking

Code: 
System Uptime: 0 days 0:00:[B]32[/B].272

This is the details debugger provides for the crash:

Code: 
BUGCHECK_STR:  0xc9_23e
DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e
FAULTING_IP: 
dtsoftbus01+1360
fffff880`0198e360 4053            push    rbx
FOLLOWUP_IP: 
dtsoftbus01+1360
fffff880`0198e360 4053            push    rbx
IRP_ADDRESS: fffff98005af4ee0
DEVICE_OBJECT: fffffa80062bca30
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
LOCK_ADDRESS:  fffff803d4aeb700 -- (!locks fffff803d4aeb700)
STACK_COMMAND:  .bugcheck ; kb
SYMBOL_NAME:  dtsoftbus01+1360
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dtsoftbus01
IMAGE_NAME:  [B]dtsoftbus01.sys[/B]
DEBUG_FLR_IMAGE_TIMESTAMP:  51c2adcb
FAILURE_BUCKET_ID:  0xc9_23e_VRF_dtsoftbus01+1360
BUCKET_ID:  0xc9_23e_VRF_dtsoftbus01+1360
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0xc9_23e_vrf_dtsoftbus01+1360
FAILURE_ID_HASH:  {aac2c460-fec6-e4d4-73d0-fb24caa4df98}

It identifies dtsoftbus01.sys driver (it belongs to Daemon Tools application) as the possible cause of the crash.

Unfortunately, as per this page, this is a know issue, which doesn't really mean it's causing all other BSODs. Anyhow, due Daemon Tools being well known for causing crashes as well as this particular issue with Driver Verifier, interrupting with our troubleshooting, I would suggest you to do the following:

  1. Remove Daemon Tools
  2. Reboot computer
  3. Enable Driver Verifier the same way you did it before
  4. Wait for system to crash few times (it shouldn't be crashing at the boot time now)
  5. Disable driver verifier
  6. Attach new files from C:\Windows\Minidump

In addition, I was just curious, what were you using Daemon Tools for? Windows 8 already has built in ISO mounting support, which means you can mount an image just by double-clicking on it. In case the reason is you need to mount other image formats, not ISO only, I would suggest you using Virtual Clone Drive.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top